background image
6-10
Cisco AVVID Network Infrastructure Enterprise Quality of Service Design
956467
Chapter 6 QoS with MPLS in an AVVID-Enabled Network
Implementing MPLS VPN QoS
interface Serial0/0
bandwidth 4000
ip address 10.13.1.2 255.255.255.0
no cdp enable
service-policy output CE-EDGE
!
router eigrp 65
network 10.0.0.0
redistribute bgp 60
passive-interface serial 0/0
!
router bgp 60
no synchronization
bgp log-neighbor-changes
network 192.168.1.0
network 10.0.0.0
neighbor 192.169.1.1 remote-as 60
neighbor 192.169.1.1 update-source Loopback0
PE Routers
The PE router is required to provide QoS for both native IP packets (on the PE-to-CE link) as well as
labeled MPLS packets (on the PE-to-P links). For the PE-CE link, IP Precedence and LLQ is used. The
PE router also provides traffic shaping, but not packet reclassification (which is performed prior to
entrance into the carrier MPLS network). IOS 12.2T (or later) is required to provide for multiple classes
of service on each VRF interface and to be able to use a non-MPLS ATM network.
For the PE-to-P links, the MPLS mode must be considered.
·
As mentioned earlier, in frame-mode MPLS the label includes a 3-bit EXP field, which includes the
IP Precedence setting of the incoming packet mapped to that label field. So for frame mode, all of
the modular QoS CLI functions are available to police and queue traffic based on the EXP bits.
·
For cell-based MPLS, the label for the outbound cells does not include any inherent QoS
classification field. It is simply the assigned VPI/VCI label, which include the 3 bits that indicate
one of four labeled virtual circuits.
If the plan is to use a single labeled virtual circuit per destination for the PE-to-P links, there must be a
mapping from the class-of-service (gold, silver, bronze) to a per-virtual circuit queuing mechanism on
the egress interface. If there are no P routers and the MPLS backbone is simply a mesh of PVCs, then
there must either be a per-virtual circuit queuing mechanism or the ability to map different classes of
service to virtual circuits with different shaping characteristics (PCR, etc.) or service guarantees (CBR,
VBR-nrt, VBR-rt, etc.).
In a cell-based MPLS network, normal operation uses a single virtual circuit per destination and allows
CBWFQ to be applied to that virtual circuit. Routers can alternatively use up to 4 virtual circuits for each
destination, using a classification based on the low-order 2 bits of the EXP filed at the ingress to the cell
MPLS network. This limit of 4 virtual circuits requires additional planning of the classes supported
within the EXP bits as there are now only 4 classes (reduced from the 8 available via the 3 EXP bits).
Table 6-1
shows the default mapping of EXP values to labeled virtual circuits in cell-mode MPLS. This
mapping can be altered through the modular QoS CLI.