Mpls Qos: About This Chapter
Mpls Qos: About This Chapter
Mpls Qos: About This Chapter
9 MPLS QoS
traffic rate exceeds the specification, requirements for services that are sensitive to QoS are
not satisfied. Therefore, MPLS TE alone cannot provide the QoS guarantee.
Scheme 1: E-LSP
The EXP-Inferred-PSC LSP (E-LSP) scheme uses the 3-bit EXP value in an MPLS header to
determine the PHB of the packets. Figure 9-1 shows an MPLS header.
The EXP value can be copied from the DSCP or IP precedence in an IP packet or be set by
MPLS network carriers.
The label determines the forwarding path, and the EXP determines the PHB.
The E-LSP is applicable to networks that support not more than eight PHBs. The precedence
field in an IP header also has three bits, same as the EXP field length. Therefore, one
precedence value in an IP header exactly corresponds to one precedence value in an MPLS
header. However, the DSCP field in an IP header has six bits, different from the EXP length.
Therefore, more DSCP values correspond to only one EXP value. As the IEEE standard
defines, the three left-most bits in the DSCP field (the CSCP value) correspond to the EXP
value, regardless of what the three right-most bits are.
During traffic classification, the EXP value in an MPLS packet is mapped to the scheduling
precedence and drop precedence. Except traffic classification, QoS operations on an MPLS
network, such as traffic shaping, traffic policing, and congestion avoidance, are implemented
in the same manner as those on an IP network.
E-LSP
BE queue
EF queue
When the MPLS packet is leaving the LSR, the scheduling precedence and drop precedence
are mapped back to the EXP value for further EXP-based operations on the network.
NOTE
For more details about the default mapping between the EXP value, service class, and color on NE40Es,
see 6.3.2 QoS Priority Mapping.
Scheme 2: L-LSP
The Label-Only-Inferred-PSC LSP (L-LSP) scheme uses labels to transmit PHB information.
The EXP field has only three bits, and therefore cannot be used alone to identify more than
eight PHBs. Instead, only the 20-bit label in an MPLS header can be used to identify more
than eight PHBs. The L-LSP is applicable to networks that support more than eight PHBs.
During packet forwarding, the label determines the forwarding path and scheduling behaviors
of the packets; the EXP carries the drop precedence. Therefore, the label and EXP both
determine the PHB. PHB information needs to be transmitted during LSP establishment. The
L-LSPs can transmit single-PHB flow, and also multi-PHB flow that has packets of the same
scheduling behavior but different drop precedences.
The EXP determines the PHB (including the The label and EXP determine the PHB.
drop precedence).
Each LSP supports up to eight behavior Each LSP supports only one BA.
aggregates (BAs).
Trust EXP or IP
Trust IP DSCP?
DSCP?
MPLS Exp=2
IP DSCP=40 IP DSCP=40
IP packet IP over MPLS
packet
Carriers need to determine whether to trust the CoS information in an IP or MPLS packet that
is entering an MPLS network or is leaving an MPLS network for an IP network. Relevant
standards defines three modes for processing the CoS: Uniform, Pipe, and Short Pipe.
Uniform Mode
When carriers determine to trust the CoS value (IP precedence or DSCP) in a packet from an
IP network, the Uniform mode can be used. The MPLS ingress LSR copies the CoS value in
the packet to the EXP field in the MPLS outer header to ensure the same QoS on the MPLS
network. When the packet is leaving the MPLS network, the egress LSR copies the EXP
value back to the IP precedence or DSCP in the IP packet.
MPLS Network
IP Network
IP Network
Ingress Penultimate Egress
node node node
MPLS->MPLS pop
MPLS->MPLS swap Outer label
Outer label MPLS Exp=5 MPLS->IP pop
MPLS->MPLS push Outer label
MPLS Exp=5 MPLS Exp=5 Inner label
Inner label MPLS Exp=5
Inner label Inner label
IP->MPLS push MPLS Exp=5 MPLS Exp=5 MPLS Exp=5
IP DSCP=40 IP DSCP=40 IP DSCP=40 IP DSCP=40
As its name implies, Uniform mode ensures the same priority of packets on the IP and MPLS
networks. Priority mapping is performed for packets when they are entering or leaving an
MPLS network. Uniform mode has disadvantages. If the EXP value in a packet changes on an
MPLS network, the PHB for the packet that is leaving the MPLS network changes
accordingly. In this case, the original CoS of the packet does not take effect.
MPLS Network
IP Network
IP Network
Ingress Penultimate Egress
node node node
MPLS->MPLS pop
MPLS->MPLS swap Outer label
Outer label MPLS Exp=6 MPLS->IP pop
MPLS->MPLS push Outer label
MPLS Exp=5 MPLS Exp=6 Inner label
Inner label MPLS Exp=6
Inner label Inner label
IP->MPLS push MPLS Exp=5 MPLS Exp=5 MPLS Exp=6
IP DSCP=40 IP DSCP=40 IP DSCP=40 IP DSCP=48
Pipe Mode
When carriers determine not to trust the CoS value in a packet from an IP network, the Pipe
mode can be used. The MPLS ingress delivers a new EXP value to the MPLS outer header,
and the QoS guarantee is provided based on the newly-set EXP value from the MPLS ingress
to the egress. The CoS value is used only after the packet leaves the MPLS network.
MPLS Network
IP Network
IP Network
Ingress Penultimate
Egress
node node
node
MPLS->MPLS pop
Outer label
MPLS->MPLS swap MPLS->MPLS swap MPLS Exp=1
MPLS->MPLS push Outer label Outer label Outer label
MPLS Exp=1
MPLS->IP pop
MPLS Exp=1 MPLS Exp=1
Inner label
IP->MPLS push Inner label Inner label Inner label MPLS Exp=1
MPLS Exp=1 MPLS Exp=1 MPLS Exp=1
IP DSCP=46 IP DSCP=46 IP DSCP=46 IP DSCP=46
In Pipe mode, the MPLS ingress does not copy the IP precedence or DSCP to the EXP field
for a packet that enters an MPLS network. Similarly, the egress does not copy the EXP value
to the IP precedence or DSCP for a packet that leaves an MPLS network. If the EXP value in
a packet changes on an MPLS network, the change takes effect only on the MPLS network.
When a packet leaves an MPLS network, the original CoS continues to take effect.
NOTE
In Pipe mode, the egress implements QoS scheduling for packets based on the CoS value defined by
carriers. The CoS value defined by carriers is relayed to the egress using the outer MPLS header.
MPLS Network
IP Network
IP Network
Ingress Penultimate Egress
node node node
MPLS->MPLS pop
MPLS->MPLS swap Outer label
MPLS->MPLS push Outer label MPLS Exp=1 MPLS->IP pop
Outer label
New EXP value MPLS Exp=1 MPLS Exp=1 Inner label
IP->MPLS push Inner label MPLS Exp=2
Inner label Inner label
New EXP value MPLS Exp=2 MPLS Exp=2 MPLS Exp=2
IP DSCP=40 IP DSCP=40 IP DSCP=40 IP DSCP=40
In Pipe or Short Pipe mode, carriers can define a desired CoS value for QoS implementation
on the carriers' own network, without changing the original CoS value of packets.
The difference between Pipe mode and Short Pipe mode lies in the QoS marking for the
outgoing traffic from a PE to a CE. In Pipe mode, outgoing traffic is scheduled based on a
CoS value defined by carriers, whereas outgoing traffic uses the original CoS value in Short
Pipe mode, as shown in Figure 9-8.
IP MPLS
IP
network network
network
CE PE PE CE
Flow direction
The tunnel to which a PW is to be iterated may vary after the PW bandwidth is configured. If
the PW bandwidth does not meet specific requirements or the SQ resources are insufficient,
the PW may fail to be iterate to the tunnel and becomes Down.
Implementing HQoS (L2VPN) at the Public Network Side Based on VPN + Peer
PE
In the MPLS VPN, bandwidth agreement may need to be reached between PE devices of an
operator, so that traffic between two PEs is restricted or guaranteed according to the
bandwidth agreement. To achieve this end, HQoS at the public network side that is based on
VPN + Peer PE can be adopted.
As shown in Figure 9-9, bandwidth and class of service are specified for traffic between PEs
at the MPLS VPN side. For example, in VLL1, the specified bandwidth for traffic between
PE1 and PE2 is 30 Mbit/s, and higher priority services are given bandwidth ahead of lower
priority services.
NOTE
If, however, you need to implement bandwidth restriction rather than bandwidth guarantee at the
network side, you can simply specify the CIR to be 0, and the PIR to the desired bandwidth.
Figure 9-9 Implementing HQoS at the public network side based on VLL + peer PE
flow1
flow2
Scheduler
flow3
classfier
flow4 port
flow5
flow6
Base t
flow7
flow8
por
CE2
d on
Base t
VLL 1
por
VLL 1
d on
PE2
CE1
PE1 VLL 2
VLL 2
CE4
P2
CE5
PE3
P3
VLL 2
PW1 Traffic:30M CE3
PW2 Traffic:20M
Flow queue 8
(Service flow 8) User queue 2 User group
(VLL2 + PE2) queue 2
Based on Based on
Based on PW
user queue outbound
Flow queue 1 interface
(Service flow 1) User queue 1 User group
queue 1 Port queue 1
(VLL1 + PE1)
If traffic is load-balanced among TE tunnels on peer PEs, all traffic that is load-balanced
undergoes priority scheduling and bandwidth restriction according to the traffic
scheduling procedure as shown in Figure 9-11.
NOTE
In this scenario, it is recommended that the TE tunnel that is configured with bandwidth resources be
adopted to achieve PE-to-PE bandwidth guarantee for traffic.
9.3.2 Application
End-to-End MPLS HQoS Solution
Figure 9-12shows the procedures of implementing end-to-end MPLS HQoS.
PE2 VLL 1
CE1 PW1 P2
PE1
VLL 2
CE3 PE3
PW2 P3 CE4
VLL 2
Configuring interface-
based QoS attributes
of incoming/outgoing
packets
On the CE-side interfaces of PEs, interface-based QoS policies are configured to implement
QoS enforcement on packets that are received from CEs or sent to CEs.
On the ingress PE that is, PE1, QoS policies are configured based on VLL/VLL instance +
peer PE for packets that are sent to the public network side. Besides, to deliver end-to-end
QoS guarantee for traffic, the TE tunnel that is allocated bandwidth can be adopted to carry
VLL traffic. In addition, on PEs, QPPB can be configured to propagate QoS policies, and the
MPLS DiffServ model can be configured so that in MPLS VPN services, both the private
network and the public network that are configured with the DiffServ QoS model can
communicate.
On the P node, QoS policies are enforced based on interface/TE tunnel without distinguishing
between VLL services and non-VLL services.