Port Features
Page 62 7750 SR Interface Configuration Guide
QoS in MC-MLPPP
If the user enables the multiclass option under an MLPPP bundle, the MDA egress data path
provides a queue for each of the 4 classes of MLPPP. The user configures the required number of
MLPPP classes to use on a bundle. The forwarding class of the packet, as determined by the
ingress QoS classification, is used to determine the MLPPP class for the packet and hence which
of the four egress MDA queues to store the packet. The mapping of forwarding class to MLPPP
class is a function of the user configurable number of MLPPP classes. The default mapping for a
4-class, 3-class, and 2-class MLPPP bundle is shown in Table 9.
Table 10 shows a different mapping enabled when the user applies one of three pre-defined egress
QoS profiles in the 4-class bundle configuration only.
Table 9: Default Packet Forwarding Class to MLPPP Class Mapping
FC ID FC Name Scheduling Priority
(Default)
MLPPP Class
4-class bundle
MLPPP Class
3-class bundle
MLPPP Class
2-class bundle
7 NC Expedited 0 0 0
6 H1 Expedited 0 0 0
5 EF Expedited 1 1 1
4 H2 Expedited 1 1 1
3 L1 Non-Expedited 2 2 1
2 AF Non-Expedited 2 2 1
1 L2 Non-Expedited 3 2 1
0 BE Non-Expedited 3 2 1
Table 10: Packet Forwarding Class to MLPPP Class Mapping
FC ID FC Name Scheduling Priority
(Default)
MLPPP Class
(MLPPP Egress QoS profile 1, 2, and 3)
7 NC Expedited 0
6 H1 Expedited 0
5 EF Expedited 1
4 H2 Expedited 2
3 L1 Non-Expedited 2
2 AF Non-Expedited 2
1 L2 Non-Expedited 2
0 BE Non-Expedited 3
To Next Page
Loading...
