The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following major topics:
Enterprise Virtual Networks consists of traffic types that include voice, video, Critical applications traffic, and end user web traffic. All these traffic require different priorities and treatments based upon their nature and how critical to the business they are. While traffic is sent and received between PE and CE, QoS implementation on ASR9000 PE uses DSCP field in the IP header to ensure that traffic is properly treated as per its priority defined by DSCP. Two-level H-QoS is configured on the PE for both ingress and egress policies. In nV access topologies, the ingress QoS function, configured on the host for Virtual satellite access port, is offloaded to satellite so that only committed traffic enters the nV network and Fabric link oversubscription can be avoided.
The mapping shown in Table 5-1 is used for different traffic classes to DSCP.
|
|
|
---|---|---|
PE configuration for QoS includes configuring class-maps for respective traffic classes and mapping them to the appropriate DSCP. Two-level ingress QOS does policing of traffic in individual classes of child policy. Parent policy is configured with keyword "child-conform-aware" to prevent the parent policer from dropping any ingress traffic that conforms to the maximum rate specified in the child policer. While configuring egress policy map, real-time traffic class CMAP-RT-dscp is configured with highest priority 1 and is policed to ensure low latency expedited forwarding. Rest classes are assigned with respective required bandwidth. WRED is used as congestion avoidance mechanism for Exp 1 and 2 traffic in the Enterprise critical class CMAP-EC-EXP. Shaping is configured on the Parent egress policy to ensure overall traffic does not exceed the committed bit rate (CBR). The ingress and egress policy-maps are applied to the PE interface connecting to CE in respective directions.
Step 1 Configure class-map for business-critical traffic.
Step 3 Configure class-map for video traffic.
Step 5 Configure class-map for real-time traffic.
Step 6 Match DSCP expedited forwarding.
Step 7 Configure Child Egress policy-map.
Step 8 Configure RT class-map under policy-map.
Step 9 Configure priority level 1 for RT class.
Step 10 Police traffic in RT class.
Step 11 Configure business-critical class under policy.
Step 12 Assign Bandwidth to the class.
Step 13 Configure Video class under policy.
Step 14 Assign Bandwidth to the class.
Step 15 Configure class-default for rest of the traffic.
Step 16 Configure parent egress policy-map.
Step 17 Configure class-default for the policy-map.
Step 18 Configure child policy under class-default.
Step 19 Configure shaping to ensure egress traffic does not exceed CBR.
Step 20 Configure bandwidth for the class.
Step 21 Configure ingress child policy-map.
Step 22 Configures real-time class-map under policy-map.
Step 23 Configure priority level 1 for real-time class.
Step 24 Police traffic in real-time class.
Step 25 Configure video class-map under policy-map.
Step 26 Configure priority level 2 for video class.
Step 27 Police traffic in video class.
Step 28 Configure business-critical class-map under policy-map.
Step 29 Police traffic in business-critical class.
Step 30 Configures class-default class-map under policy-map.
Step 31 Police traffic in default class.
Step 32 Configure parent egress policy-map.
Step 33 Configure class-default for the policy-map.
Step 34 Child policy under class-default.
Step 35 Configure policing to ensure ingress traffic does not exceed CBR.
Step 36 Configure child-conform-aware under class.
In case of PWHE access, QoS is implemented on PE based on MPLS EXP bits as the received traffic is labeled.
Step 1 Configure business-critical class.
Step 2 Match MPLS EXP of topmost label as 1,2.
Step 3 Configure real-time class.
Step 4 Match MPLS EXP of topmost label as 5.
Step 5 Configures video class.
Step 6 Match MPLS EXP of topmost label as 3.
Step 7 Configure ingress child policy-map.
Step 8 Configure real-time class-map under policy-map.
Step 9 Configure priority level 1 for real-time class.
Step 10 Police traffic in real-time class.
Step 11 Configure video class-map under policy-map.
Step 12 Configure priority level 2 for video class.
Step 13 Police traffic in video class.
Step 14 Configure business-critical class-map under policy-map.
Step 15 Configure priority level 1 for business-critical class.
Step 16 Police traffic in business-critical class.
Step 17 Configure class-default class-map under policy-map.
Step 18 Police traffic in default class.
Step 19 Configure parent egress policy-map.
Step 20 Configure class-default for the policy-map.
Step 21 Configure child policy under class-default.
Step 22 Configure policing to ensure ingress traffic does not exceed CBR.
Step 23 Configure child-conform-aware under class.
Step 24 Configure child egress policy-map.
Step 25 Configure real-time class-map under policy-map.
Step 26 Configure priority level 1 for real-time class.
Step 27 Police traffic in real-time class.
Step 28 Configure real-time class-map under policy-map.
Step 29 Configure priority level 2 for video class.
Step 30 Police traffic in video class.
Step 31 Configure WRED to congestion avoidance.
Step 32 Configure business-critical class-map under policy-map.
Step 33 Configure bandwidth for business-critical class.
Step 34 Configure WRED to congestion avoidance for discard-class 2.
Step 35 Configure WRED to congestion avoidance for discard-class 1.
Step 36 Configure parent egress policy-map.
Step 37 Configure class-default for the policy-map.
Step 38 Configure child policy under class-default.
Step 39 Configure shaping to ensure egress traffic does not exceed CBR.
Step 40 Service policies applied under PW-Ether interface.