Table Of Contents
QoS-Hierarchical Queueing for Ethernet DSLAMs
Prerequisites for QoS-Hierarchical Queueing for Ethernet DSLAMs
Restrictions for QoS-Hierarchical Queueing for Ethernet DSLAMs
Information About QoS-Hierarchical Queueing for Ethernet DSLAMs
Different Levels of QoS Provisioning
Configuration Guidelines for Hierarchical Queueing on Ethernet DSLAMs
Configuring QoS-Hierarchical Queueing for Ethernet DSLAMs
Configuring and Applying QoS-Hierarchical Queueing Policy Maps to Sessions
Configuring and Applying QoS-Hierarchical Queueing Policy Maps to Subinterfaces
Displaying Policy-Map Information for Hierarchical Queueing
Configuration Examples for QoS-Hierarchical Queueing for Ethernet DSLAMs
Configuring QoS-Hierarchical Queueing Policy Maps on VLANs or QinQ Subinterfaces: Example
Configuring QoS-Hierarchical Queueing Policy Maps on VLANs with Arbitrary QinQ: Example
Configuring QoS-Hierarchical Queueing Policy Maps on Sessions: Example
Configuring QoS-Hierarchical Queueing Policy Maps on Sessions with Aggregate Shaping: Example
Feature Information for QoS-Hierarchical Queueing for Ethernet DSLAMs
QoS-Hierarchical Queueing for Ethernet DSLAMs
First Published: November, 2006Last Updated: October 3, 2008This feature module describes how to configure quality of service (QoS) hierarchical queueing policy maps on sessions and subinterfaces in Ethernet Digital Subscriber Line Access Multiplexer (E-DSLAM) applications on a Cisco 10000 series router. The QoS-Hierarchical Queueing for Ethernet-DSLAMs feature supports IEEE 802.1 QinQ VLAN tag termination to configure inner VLAN identifiers on E-DSLAMs.
Finding Feature Information
Your software release may not support all the features documented in this module. 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 Ethernet DSLAMs" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for QoS-Hierarchical Queueing for Ethernet DSLAMs
•
Restrictions for QoS-Hierarchical Queueing for Ethernet DSLAMs
•
Information About QoS-Hierarchical Queueing for Ethernet DSLAMs
•
Configuring QoS-Hierarchical Queueing for Ethernet DSLAMs
•
Configuration Examples for QoS-Hierarchical Queueing for Ethernet DSLAMs
•
Feature Information for QoS-Hierarchical Queueing for Ethernet DSLAMs
Prerequisites for QoS-Hierarchical Queueing for Ethernet DSLAMs
•
You must configure traffic classes using the class-map command.
•
This feature requires a Performance Routing Engine 3 (PRE3).
Restrictions for QoS-Hierarchical Queueing for Ethernet DSLAMs
•
Cisco IOS Release 12.2(31)SB2 do not include Modular QoS Command-Line Interface (CLI) (MQC) support for the following session-based queueing policies:
–
IP sessions
–
Inner VLAN sessions
•
This feature is not supported in combination with load balancing when a session service policy is routed to a Layer 2 Tunnel Protocol (L2TP) tunnel. Do not configure load balancing on an L2TP tunnel if per-session queueing is enabled.
Information About QoS-Hierarchical Queueing for Ethernet DSLAMs
To configure QoS-Hierarchical Queueing for Ethernet DSLAMs, you should understand the following concepts:
•
Different Levels of QoS Provisioning
•
Configuration Guidelines for Hierarchical Queueing on Ethernet DSLAMs
Different Levels of QoS Provisioning
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 Ethernet DSL access network. The sample network includes multiple entities where QoS provisioning is required for different reasons.
Figure 1 Ethernet DSL Access Network
![]()
The following entities may require different traffic shaping:
•
A VLAN shaped to a certain aggregate traffic rate to limit the traffic to a group of subscribers (different 802.1Q interfaces in Figure 1).
•
Individual sessions shaped with certain QoS services for different classes of traffic (individual PCs in Figure 1).
Integrated Queueing Hierarchy
Different traffic shaping requirements result in QoS provisioning at multiple levels at the same time. The QoS-Hierarchical Queueing for Ethernet 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 MQC and a common queueing control plane sets up and enables the queueing features.
Session-to-interface associations are resolved to determine the physical interface on which to form the integrated queueing hierarchy for all levels of QoS provisioning. As subinterface session-based policies are added, the respective queues are created and integrated into the queueing hierarchy.
When a subinterface is provisioned followed by session-based policy provisioning, the integrated queueing hierarchy is formed on top of the physical interface as a result of queueing policies provisioned at two different levels. When a session is provisioned before subinterface-based policy provisioning, the queueing hierarchy has a placeholder logical level between the physical queue and the session queue. The placeholder queue becomes the default queue at that level, and all other sessions are parented to that queue.
A PRE3 supports three hierarchical levels of scheduling: physical port, session, and class queues. When sessions are established within a subinterface that is configured with a shaping policy, the subinterface level is lowered to the physical layer.
Configuration Guidelines for Hierarchical Queueing on Ethernet DSLAMs
When configuring QoS-Hierarchical Queueing for Ethernet DSLAMs feature, note the following guidelines:
•
An individual subscriber is always identified by a PPP or IP session. A group of subscribers is identified by a particular VLAN by means of the outer tag ISP, E-DSLAM, or user-facing provider edge (U-PE).
•
When a subinterface is used to aggregate a number of sessions with queueing policies, a queueing policy at a subinterface level must be a one-level policy map that is configured as class-default with only the shape feature enabled.
•
Do not oversubscribe sessions to ensure distributed bandwidth for sessions with configured shape rates.
Configuring QoS-Hierarchical Queueing for Ethernet DSLAMs
This section contains the procedures for configuring the QoS-Hierarchical Queueing for Ethernet DSLAMs feature. While all three procedures are listed as optional, you must choose one of the first two.
•
Configuring and Applying QoS-Hierarchical Queueing Policy Maps to Sessions (optional)
•
Configuring and Applying QoS-Hierarchical Queueing Policy Maps to Subinterfaces (optional)
•
Displaying Policy-Map Information for Hierarchical Queueing (optional)
Configuring and Applying QoS-Hierarchical Queueing Policy Maps to Sessions
To configure and apply a QoS hierarchical queueing policy map to PPP/IP sessions through a virtual template, perform the following steps.
![]()
Note
To configure and apply a QoS hierarchical queueing policy map to subinterfaces, skip this procedure and complete the steps in the "Configuring and Applying QoS-Hierarchical Queueing Policy Maps to Subinterfaces" section.
SUMMARY STEPS
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.
precedence precedence min-threshold max-threshold mark-probability-denominator
7.
set cos cos-value
8.
exit
9.
exit
10.
policy-map policy-map-name
11.
class class-default
12.
shape average cir
13.
bandwidth remaining ratio ratio
14.
service-policy policy-map-name
15.
exit
16.
exit
17.
interface virtual-template number
18.
service-policy output policy-map-name
19.
end
DETAILED STEPS
Examples
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> enableRouter# configure terminalRouter(config)# policy-map session_a_childRouter(config-pmap)# class voipRouter(config-pmap-c)# police 1000000Router(config-pmap-c)# priority level 1Router(config-pmap-c)# exitRouter(config-pmap)# class videoRouter(config-pmap-c)# police 100000Router(config-pmap-c)# priority level 2Router(config-pmap-c)# exitRouter(config-pmap)# class precedence_0Router(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# exitRouter(config-pmap)# class precedence_1Router(config-pmap-c)# bandwidth remaining ratio 20Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# policy-map session_a_parentRouter(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# service-policy session_a_childRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface virtual-template 20Router(config-if)# service-policy output session_a_parentRouter(config-if)# endConfiguring and Applying QoS-Hierarchical Queueing Policy Maps to Subinterfaces
To configure and apply a QoS hierarchical queueing policy map to a subinterface (and provide aggregate shaping for a large number of subscribers), perform the following steps.
![]()
Note
When a subinterface is used to aggregate a number of sessions with queueing policies, a queueing policy at a subinterface level must be a one-level policy map configured as class-default with only the shape feature enabled.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
policy-map policy-map-name
4.
class class-default
5.
shape average cir
6.
exit
7.
exit
8.
interface type slot/subslot/port.subinterface
9.
encapsulation dot1q outer-vlan-id [second-dot1q inner-vlan-id]
10.
service-policy output policy-map-name
11.
end
DETAILED STEPS
Examples
The following is an example of how to configure and apply a QoS hierarchical queueing policy map to a subinterface (and provide aggregate shaping for a large number of subscribers):
Router> enableRouter# configure terminalRouter(config)# policy-map subint_1Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface GigabitEthernet3/1/1.1Router(config-subif)# encapsulation dot1q 100Router(config-subif)# service-policy output subint_1Router(config-subif)# endDisplaying Policy-Map Information for Hierarchical Queueing
To display policy-map information, perform the following steps.
SUMMARY STEPS
1.
enable
2.
show policy-map
3.
show policy-map interface interface-name
4.
show policy-map session
5.
exit
DETAILED STEPS
Configuration Examples for QoS-Hierarchical Queueing for Ethernet DSLAMs
This section provides the following configuration examples:
•
Configuring QoS-Hierarchical Queueing Policy Maps on VLANs or QinQ Subinterfaces: Example
•
Configuring QoS-Hierarchical Queueing Policy Maps on VLANs with Arbitrary QinQ: Example
•
Configuring QoS-Hierarchical Queueing Policy Maps on Sessions: Example
•
Configuring QoS-Hierarchical Queueing Policy Maps on Sessions with Aggregate Shaping: Example
Configuring QoS-Hierarchical Queueing Policy Maps on VLANs or QinQ Subinterfaces: Example
The following example shows how to configure and apply QoS hierarchical queueing policy maps on VLANs or QinQ subinterfaces. A child queueing policy is applied to each parent subscriber line level policy. In this example, the policy maps are applied to create subscriber groups on subinterfaces.
Router> enableRouter# configure terminalRouter(config)# policy-map service_a_outRouter(config-pmap)# class voipRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police percent 20 bc 300 ms pir 40Router(config-pmap-c)# set cos 1Router(config-pmap-c)# exitRouter(config-pmap)# class videoRouter(config-pmap-c)# police percent 20 bc 300 ms pir 40Router(config-pmap-c)# set cos 2Router(config-pmap-c)# exitRouter(config-pmap)# class gamingRouter(config-pmap-c)# bandwidth remaining percent 80Router(config-pmap-c)# set cos 3Router(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# set cos 4Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map service_z_outRouter(config-pmap)# exit!Router(config)# policy-map rate_1_service_a_inRouter(config-pmap)# class voipRouter(config-pmap-c)# police percent 25 4 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class gamingRouter(config-pmap-c)# police percent 50 2 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police percent 20 bc 300 ms pir 40Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_x_service_z_inRouter(config-pmap)# exit!Router(config)# policy-map rate_1_service_a_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy service_a_outRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_x_serviice_z_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy service_z_outRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface GigabitEthernet1/0/0.1Router(config-subif)# encapsulation dot1q 5 second dot1q 20Router(config-subif)# service-policy output rate_1_service_a_outRouter(config-subif)# service-policy input rate_1_service_a_inRouter(config-subif)# exitRouter(config)# interface GigabitEthernet1/0/0.2Router(config-subif)# encapsulation dot1q 5 second dot1q 25Router(config-subif)# service-policy output rate_x_service_z_outRouter(config-subif)# service-policy input rate_x_service_z_inRouter(config-subif)# endConfiguring QoS-Hierarchical Queueing Policy Maps on VLANs with Arbitrary QinQ: Example
The following example shows how to configure and apply QoS hierarchical queueing policy maps on VLANs with subscriber lines grouped by arbitrary QinQ. A child queueing policy is applied to each parent subscriber line level policy. This example includes the configuration of multiple class maps.
Router> enableRouter# configure terminalRouter(config)# class-map match-all user_1Router(config-cmap)# match vlan 10Router(config-cmap)# exitRouter(config)# class-map match-all user_2Router(config-cmap)# match vlan 11Router(config-cmap)# exitRouter(config)# class-map match-all user_3Router(config-cmap)# match vlan 10Router(config-cmap)# exitRouter(config)# class-map match-any user_4Router(config-cmap)# match vlan 11Router(config-cmap)# exitRouter(config)# class-map match-all user_nRouter(config-cmap)# exitRouter(config)# class-map match-any isp_ARouter(config-cmap)# match class user_1Router(config-cmap)# match class user_2Router(config-cmap)# exitRouter(config)# class-map match-any isp_ZRouter(config-cmap)# match class user_3Router(config-cmap)# match class user_4Router(config-cmap)# exit!Router(config)# policy-map service_a_outRouter(config-pmap)# class voipRouter(config-pmap-c)# priorityRouter(config-pmap-c)# police cir percent 20 bc 300 ms pir 40Router(config-pmap-c)# set cos 1Router(config-pmap-c)# exitRouter(config-pmap)# class videoRouter(config-pmap-c)# police cir percent 20 bc 300 ms pir 40Router(config-pmap-c)# set cos 2Router(config-pmap-c)# exitRouter(config-pmap)# class gamingRouter(config-pmap-c)# bandwidth remaining percent 80Router(config-pmap-c)# set cos 3Router(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# set cos 4Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map service_z_outRouter(config)# policy-map service_a_inRouter(config-pmap)# class voipRouter(config-pmap-c)# police percent 25 4 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class gamingRouter(config-pmap-c)# police percent 50 2 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir percent 20 bc 300 ms pir 40Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map service_z_inRouter(config-pmap)# exit!Router(config)# policy-map isp_A_outRouter(config-pmap)# class user_1Router(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy service_a_outRouter(config-pmap-c)# exitRouter(config-pmap)# class user_nRouter(config-pmap-c)# bandwidth remaining ratio 20Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy service_z_outRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map isp_Z_outRouter(config-pmap)# exit!Router(config)# policy-map isp_A_inRouter(config-pmap)# class user_1Router(config-pmap-c)# service policy service_a_inRouter(config-pmap-c)# class user_nRouter(config-pmap-c)# service policy service_z_inRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map isp_Z_inRouter(config-pmap)# exit!Router(config)# policy-map interface_policy_outRouter(config-pmap)# class isp_ARouter(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy isp_A_outRouter(config-pmap-c)# exitRouter(config-pmap)# class isp_ZRouter(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy isp_Z_outRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map interface_policy_inRouter(config-pmap)# class isp_ARouter(config-pmap-c)# service policy isp_A_inRouter(config-pmap-c)# exitRouter(config-pmap)# class isp_ZRouter(config-pmap-c)# service policy isp_Z_inRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# interface GigabitEthernet1/0/0.1Router(config-subif)# encapsulation dot1q 5 second dot1q anyRouter(config-subif)# service-policy output interface_policy_outRouter(config-subif)# service-policy input interface_policy_inRouter(config-subif)# endConfiguring QoS-Hierarchical Queueing Policy Maps on Sessions: Example
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> enableRouter# configure terminalRouter(config)# policy-map service_a_outRouter(config-pmap)# class voipRouter(config-pmap-c)# priorityRouter(config-pmap-c)# set cos 1Router(config-pmap-c)# exitRouter(config-pmap)# class videoRouter(config-pmap-c)# set cos 2Router(config-pmap-c)# exitRouter(config-pmap)# class gamingRouter(config-pmap-c)# bandwidth remaining percent 80Router(config-pmap-c)# set cos 3Router(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# set cos 4Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map service_z_outRouter(config-pmap)# exit!Router(config)# policy-map rate_1_service_a_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service-policy service_a_outRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_x_service_z_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service-policy service_z_outRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_1_service_a_inRouter(config-pmap)# class voipRouter(config-pmap-c)# police percent 25 4 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class gamingRouter(config-pmap-c)# police percent 50 2 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police cir percent 20 bc 300 ms pir 40Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_x_service_z_inRouter(config-pmap)# exit!Router(config)# policy-map isp_A_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# exitRouter(config)# policy-map isp_Z_outRouter(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 100000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface GigabitEthernet1/0/0.1Router(config-subif)# encapsulation dot1q 1Router(config-subif)# service-policy output isp_A_outRouter(config-subif)# exitRouter(config)# interface GigabitEthernet2/0/0.2Router(config-subif)# encapsulation dot1q 2Router(config-subif)# service-policy output isp_Z_outRouter(config-subif)# endConfiguring QoS-Hierarchical Queueing Policy Maps on Sessions with Aggregate Shaping: Example
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, the same policies are applied to all sessions using the same virtual interface.
Router> enableRouter# configure terminalRouter(config)# policy-map service_a_outRouter(config-pmap)# class voipRouter(config-pmap-c) priorityRouter(config-pmap-c)# police percent 25 4 ms 1 msRouter(config-pmap-c)# set cos 1Router(config-pmap-c)# exitRouter(config-pmap)# class videoRouter(config-pmap-c)# police percent 30 5 ms 1 msRouter(config-pmap-c)# set cos 2Router(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# set cos 3Router(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map service_z_outRouter(config-pmap)# exit!Router(config)# policy-map rate_1_service_a_inRouter(config-pmap)# class voipRouter(config-pmap-c)# police percent 25 4 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class videoRouter(config-pmap-c)# police percent 30 2 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# police percent 40 2 ms 1 msRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_x_service_z_inRouter(config-pmap)# exit!Router(config)# policy-map rate_1_service_a_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy service_a_outRouter(config-pmap-c)# exitRouter(config-pmap)# exit!Router(config)# policy-map rate_x_service_z_outRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining ratio 10Router(config-pmap-c)# shape average 100000Router(config-pmap-c)# service policy service_z_outRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface GigabitEthernet1/0/0Router(config-if)# encapsulation dot1q 1Router(config-if)# service-policy output isp_A_outRouter(config-if)# exitRouter(config)# interface GigabitEthernet2/0/0Router(config-if)# encapsulation dot1q 2Router(config-if)# service-policy output isp_Z_outRouter(config-if)# endAdditional References
The following sections provide references related to the QoS-Hierarchical Queueing for Ethernet DSLAMs feature.
Related Documents
Related Topic Document TitleQoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples
Traffic shaping
MQC
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This feature uses no new or modified commands.
Feature Information for QoS-Hierarchical Queueing for Ethernet DSLAMs
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS, Catalyst OS, and 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 software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006-2008 Cisco Systems, Inc. All rights reserved.