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 feature module describes how to configure quality of service (QoS) hierarchical queueing policy maps on sessions and ATM VCs in ATM Digital Subscriber Line Access Multiplexer (A-DSLAM) applications on a Cisco ASR 1000 Series Aggregation Services Router.
For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for QoS Hierarchical Queueing for ATM DSLAMs" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
•Prerequisites for QoS Hierarchical Queueing for ATM DSLAMs
•Restrictions for QoS Hierarchical Queueing for ATM DSLAMs
•Information About QoS Hierarchical Queueing for ATM DSLAMs
•How to Configure QoS Hierarchical Queueing for ATM DSLAMs
•Configuration Examples for QoS Hierarchical Queueing for ATM DSLAMs
•Feature Information for QoS Hierarchical Queueing for ATM DSLAMs
You must configure traffic classes using the class-map command.
The QoS Hierarchical Queueing for ATM DSLAMs feature is not supported in combination with load balancing when a session service policy is routed to a Layer 2 Tunnel Protocol (L2TP) tunnel. This feature is supported only with shaped ATM VCs, which means ATM VCs that are defined as constant bit rate (CBR), Variable bit rate (VBR) or shaped unspecified bit rate (UBR), (that is, UBR with a peak cell rate).
Traffic downstream from a Broadband Router Access Server (BRAS) requires different levels of QoS provisioning (for example, traffic shaping) depending on the network architecture between the BRAS and the subscriber. Figure 1 illustrates an ATM DSL access network. The sample network includes multiple entities where QoS provisioning is required for different reasons.
Figure 1 ATM DSL Access Network
Different traffic shaping requirements result in QoS provisioning at multiple levels at the same time. The QoS-Hierarchical Queueing for ATM DSLAMs feature provides the ability to form one integrated queueing hierarchy that provides QoS provisioning at multiple levels with support for features such as bandwidth distribution at any of these levels.
The integrated queueing hierarchy is formed on the physical interface. When a service policy is instantiated on a session, the Subscriber Service Switch (SSS) infrastructure invokes the Modular QoS CLI (MQC) and a common queueing control plane sets up and enables the queueing features.
Session-to-ATM associations are resolved to determine the ATM VC on which the session QoS queues are built. QoS policies consisting of a shaper may also be applied simultaneously at the VC level.
When configuring the QoS Hierarchical Queueing for ATM DSLAMs feature, note the following guidelines:
•When an ATM VC is used to aggregate a number of sessions with queueing policies, a queueing policy at an ATM VC level must be a one-level policy map that is configured as class-default with only the shape feature enabled.
•Both ATM VCs and sessions can be oversubscribed and controlled by shapers.
1. enable
2. configure terminal
3. policy-map policy-map-name
4. class class-map-name
5. bandwidth {bandwidth-kbps | percent percentage | remaining percent percentage}
6. exit
7. exit
8. policy-map policy-map-name
9. class class-default
10. shape average {cir | percent percentage}
11. bandwidth remaining ratio ratio
12. service-policy policy-map-name
13. exit
14. exit
15. interface virtual-template number
16. service-policy output policy-map-name
17. end
The following is an example of how to configure and apply a QoS hierarchical queueing policy map to PPP/IP sessions by using a virtual template:
Router> enable
Router# configure terminal
Router(config)# policy-map session-a-child
Router(config-pmap)# class voip
Router(config-pmap-c)# police 1000000
Router(config-pmap-c)# priority level 1
Router(config-pmap-c)# exit
Router(config-pmap)# class video
Router(config-pmap-c)# police 100000
Router(config-pmap-c)# priority level 2
Router(config-pmap-c)# exit
Router(config-pmap)# class precedence_0
Router(config-pmap-c)# bandwidth remaining ratio 10
Router(config-pmap-c)# exit
Router(config-pmap)# class precedence_1
Router(config-pmap-c)# bandwidth remaining ratio 20
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# policy-map session_a_parent
Router(config-pmap-c)# exit
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 10000000
Router(config-pmap-c)# bandwidth remaining ratio 10
Router(config-pmap-c)# service-policy session-a-child
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface virtual-template 20
Router(config-if)# service-policy output session_a_parent
Router(config-if)# end
1. enable
2. configure terminal
3. policy-map policy-map-name
4. class class-default
5. shape average {cir | percent percentage}
6. exit
7. exit
8. interface type slot/subslot/port.subinterface
9. pvc [name] vpi/vci [ces | ilmi | qsaal | smds | l2transport]
10. vbr-nrt peak-cell-rate average-cell-rate
11. service-policy output policy-map-name
12. end
The following is an example of how to configure and apply a QoS hierarchical queueing policy map to an ATM VC (and provide aggregate shaping for a large number of subscribers):
Router> enable
Router# configure terminal
Router(config)# policy-map subint-1
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 10000000
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface ATM 3/1/1.1
Router(config-if-atm-vc)# pvc 2/100
Router (config-if-atm-vc)# vbr-nrt 800000 800000
Router(config-subif)# service-policy output subint-1
Router(config-subif)# end
1. enable
2. show policy-map
3. show policy-map interface type number
4. show policy-map session
5. exit
The following example shows how to configure and apply QoS hierarchical queueing policy maps on sessions. A child queueing policy is applied to each parent subscriber line level policy.
Router> enable
Router# configure terminal
Router(config)# policy-map service-a-out
Router(config-pmap)# class voip
Router(config-pmap-c)# priority
Router(config-pmap-c)# set cos 1
Router(config-pmap-c)# exit
Router(config-pmap)# class video
Router(config-pmap-c)# set cos 2
Router(config-pmap-c)# exit
Router(config-pmap)# class gaming
Router(config-pmap-c)# bandwidth remaining percent 80
Router(config-pmap-c)# set cos 3
Router(config-pmap-c)# exit
Router(config-pmap)# class class-default
Router(config-pmap-c)# bandwidth remaining percent 20
Router(config-pmap-c)# set cos 4
Router(config-pmap-c)# exit
Router(config-pmap)# exit
!
Router(config)# policy-map rate-1-service-a-out
Router(config-pmap)# class class-default
Router(config-pmap-c)# bandwidth remaining ratio 10
Router(config-pmap-c)# shape average 100000
Router(config-pmap-c)# service-policy service-a-out
Router(config-pmap-c)# exit
Router(config-pmap)# exit
!
Router(config)# policy-map rate-1-service-a-in
Router(config-pmap)# class voip
Router(config-pmap-c)# police percent 25
Router(config-pmap-c)# exit
Router(config-pmap)# class gaming
Router(config-pmap-c)# police percent 50
Router(config-pmap-c)# exit
Router(config-pmap)# class class-default
Router(config-pmap-c)# police percent 20
Router(config-pmap-c)# exit
Router(config-pmap)# exit
!
Router(config)# interface virtual-template 20
Router(config-if)# service-policy output rate-1-service-a-out
Router(config-if)# service-policy input rate-1-service-a-in
Router(config-if)# end
The following example shows how to configure and apply QoS hierarchical queueing policy maps on sessions with multiple PPP/IP sessions per subscriber line. In this example, queueing is configured as in previous example. The VC is configured as follows:
Router(config)# policy-map isp_A_out
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 500000
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface ATM 1/0/0.1
Router(config-subif)# pvc 10/100
Router(config-if-atm-vc)# vbr-nrt 800000 800000
Router(config-if-atm-vc)# service-policy output isp-A-out
Router(config-if-atm-vc)# exit
Router(config-subif)# exit
|
|
---|---|
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
|
Traffic shaping |
|
MQC |
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
|
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific Software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.