19.07.2013 Views

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

Enterprise QoS Solution Reference Network Design Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3 WAN Aggregator <strong>QoS</strong> <strong>Design</strong><br />

Version 3.3<br />

WAN Edge Link-Specific <strong>QoS</strong> <strong>Design</strong><br />

Two options exist for carrying voice traffic over slow-speed ATM PVCs: either Multilink PPP over ATM<br />

(MLPoATM), in conjunction with MLP LFI, or ATM PVC bundling. ATM PVC bundling is a legacy<br />

technique that has drawbacks such as inefficient bandwidth utilization and classification limitations (IP<br />

precedence versus DSCP). But sometimes service providers make ATM PVC bundles economically<br />

attractive to enterprise customers, so both approaches are discussed.<br />

Slow-Speed (£ 768 kbps) ATM Links: MLPoATM<br />

Recommendation: Use MLP LFI. Tune the ATM PVC Tx-ring to 3. cRTP can be used only in Cisco<br />

IOS Release 12.2(2)T or later.<br />

Serialization delays on slow-speed ATM links, as shown in Figure 3-14, necessitate a fragmentation and<br />

interleaving mechanism. The most common ATM adaptation layers (such as AAL5) do not have<br />

sequence numbers in the cell headers and, thus, require cells to arrive in the correct order. This<br />

requirement makes interleaving a problem that cannot be solved at these ATM adaptation layers and thus<br />

must be solved at a higher layer.<br />

Figure 3-14 Slow-Speed MLPoATM Links<br />

WAN Aggregator<br />

MLPoATM Link<br />

768 kbps<br />

ATM<br />

Cloud<br />

Branch Router<br />

A solution to this problem is to run MLPoATM and let MLP LFI handle any necessary fragmentation<br />

and interleaving so that such operations are completely transparent to the lower ATM layer. As far as the<br />

ATM layer is concerned, all cells arrive in the same order they were sent.<br />

MLPoATM functionality is enabled through the use of virtual-access interfaces. Virtual-access<br />

interfaces are built on demand from virtual-template interfaces and inherit their configuration properties<br />

from the virtual templates they are built from. Thus, the IP address, service-policy statement, and LFI<br />

parameters all are configured on the virtual template, as shown in Example 3-22.<br />

cRTP is supported only on ATM PVCs (through MLPoATM), as of Cisco IOS Release 12.2(2)T.<br />

Additionally, as discussed previously in this chapter, it is recommended that the value of the final output<br />

buffer, the Tx-ring, be tuned on slow-speed ATM PVCs to a value of three particles to minimize<br />

serialization delay.<br />

Example 3-22 Slow-Speed (£ 768 kbps) MLPoATM <strong>QoS</strong> <strong>Design</strong> Example<br />

!<br />

interface ATM4/0<br />

bandwidth 768<br />

no ip address<br />

no atm ilmi-keepalive<br />

!<br />

interface ATM4/0.60 point-to-point<br />

pvc BRANCH#60 0/60<br />

vbr-nrt 768 768 ! ATM PVC definition<br />

tx-ring-limit 3 ! Per-PVC Tx-ring is tuned to 3 particles<br />

protocol ppp Virtual-Template60 ! PVC is bound to the Virtual-Template<br />

!<br />

interface Virtual-Template60<br />

bandwidth 768<br />

<strong>Enterprise</strong> <strong>QoS</strong> <strong>Solution</strong> <strong>Reference</strong> <strong>Network</strong> <strong>Design</strong> <strong>Guide</strong><br />

3-33

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!