Feedback
Table Of Contents
Configuring QoS on the Optical Services Modules
Additional QoS Features and Resources
Restrictions and Usage Guidelines
Configuring Class-Based Traffic Shaping
Restrictions and Usage Guidelines
Configuring Class-Based Weighted Fair Queuing
Restrictions and Usage Guidelines
Configuring Low Latency Queuing
Restrictions and Usage Guidelines
Configuring Weighted Random Early Detection
Restrictions and Usage Guidelines
Configuring Hierarchical Traffic Shaping
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Restrictions and Usage Guidelines
Distribution of Remaining Bandwidth
Unsupported Frame Relay-Specific QoS Features
Restrictions and Usage Guidelines
Configuring QoS on the Optical Services Modules
This chapter describes how to configure Quality of Service (QoS) on the Optical Services Modules (OSMs).
This chapter consists of these sections:
•
Understanding QoS on the OSMs
•
Understanding QoS on the OSMs
QoS for the OSMs is distributed between the OSMs and the Policy Feature Card. This chapter discusses the Layer 3 QoS implementations on the OSM WAN ports.
For the OSM WAN ports, the OSMs support the following Layer 3 QoS implementations:
•
•
•
•
•
You configure OSM WAN port QoS using a subset of the Modular QoS CLI (MQC). For information on MQC, refer to the Modular Quality of Service Command-Line Interface Overview at:
Note
For OSM WAN port Layer 3 QoS configuration information and examples, see the "Configuring QoS on the OSMs" section and the Configuring MPLS QoS.
Additional QoS Features and Resources
•
•
•
Note
•
–
–
•
–
–
•
–
–
Configuring QoS on the OSMs
These sections describe configuring QoS on the OSMs:
•
•
•
•
•
•
For information on shaping features supported with Destination Sensitive Services (DSS), see "Configuring Destination Sensitive Services on the Optical Services Modules."
Enabling QoS Globally
Before you can configure QoS on the OSMs, you must enable the QoS functionality globally. To enable QoS globally, perform this task:
This example shows how to enable QoS globally:
Router(config)# mls qosRouter(config)# endRouter#This example shows how to verify the configuration:
Router# show mls qosQoS is enabled globallyMicroflow QoS is enabled globallyQoS global counters:Total packets: 544393IP shortcut packets: 1410Packets dropped by policing: 0IP packets with TOS changed by policing: 467IP packets with COS changed by policing: 59998Non-IP packets with COS changed by policing: 0Router#Configuring Classification
This section contains information for configuring classification for the OSM QoS features.
Classification is the selection of traffic for QoS. OSMs classify IP traffic based on the packet IP precedence or IP DSCP value. OSMs classify MPLS traffic based on the MPLS EXP value in the topmost label in the MPLS label stack. Use the class-map command in global configuration mode to specify the name of the class map and define the class-matching criteria.
Restrictions and Usage Guidelines
The classification restrictions and usage guidelines are as follows:
•
•
•
Configuration Tasks
To configure classification, perform this task in global configuration mode on the Mutilayer Switch Feature Card (MSFC):
Configuring Class-Based Traffic Shaping
This section contains information for configuring class-based traffic shaping.
QoS on the OSMs supports both inbound and outbound class-based traffic shaping. Class-based traffic shaping on the OSMs limits the traffic to the configured rate. To configure class-based traffic shaping, use the shape average command.
Restrictions and Usage Guidelines
The class-based traffic shaping restrictions and usage guidelines are as follows:
•
Note
•
–
–
–
•
Configuration Tasks
To configure class-based traffic shaping, use the Modular QoS CLI. Define the class of traffic with the class-map command as shown previously, create a policy map as shown previously that contains the shape average command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with class-based traffic shaping and to assign the policy to an interface, perform the following tasks in global configuration mode.
Note
1 Only supported parameters are shown.
Configuration Example
This example shows how to configure a low shape-rate queue and a high shape-rate queue:
Step 1
Router(config)# class-map match-all gold-dataRouter(config-cmap)# match ip dscp 40Router(config-cmap)# exitRouter(config)# class-map match-all bronze-dataRouter(config-cmap)# match ip dscp 8Router(config-cmap)# exitStep 2
Router(config)# policy-map policy1Router(config-pmap)# class gold-dataRouter(config-pmap-c)# shape average 2000000Router(config-pmap-c)# exitRouter(config-pmap)# class bronze-dataRouter(config-pmap-c)# shape average 5000000Router(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 3000000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)#Step 3
Router(config)# interface pos7/1Router(config-if)# service-policy output policy1Router(config-if)# exitStep 4
Note
Router# show policy interface pos7/1POS7/1Service-policy output: policy1Class-map: gold-data (match-all)795533 packets, 271276753 bytes30 second offered rate 17269000 bps, drop rate 2939000 bpsMatch: ip dscp cs5queue size 0, queue limit 128packets output 660256, packet drops 135277tail/random drops 135277, no buffer drops 0, other drops 0shape (average) cir 20000000 bc 80000 be 80000target shape rate 20000000(shape parameter is rounded to 19,513,000 bps due to granularity)
Class-map: bronze-data (match-all)795533 packets, 271276753 bytes30 second offered rate 17269000 bps, drop rate 13687000 bpsMatch: ip dscp cs1queue size 0, queue limit 128packets output 165164, packet drops 630369tail/random drops 630369, no buffer drops 0, other drops 0shape (average) cir 5000000 bc 20000 be 20000target shape rate 5000000(shape parameter is rounded to 4,878,000 bps due to granularity)
Class-map: class-default (match-any)3182121 packets, 1085103261 bytes30 second offered rate 69075000 bps, drop rate 47581000 bpsMatch: anyqueue size 0, queue limit 128packets output 990320, packet drops 2191801tail/random drops 2191801, no buffer drops 0, other drops 0shape (average) cir 30000000 bc 120000 be 120000target shape rate 30000000(shape parameter is rounded to 29,270,000 bps due to granularity)
Note
Configuring Class-Based Weighted Fair Queuing
This section contains information for configuring Class-Based Weighted Fair Queueing (CBWFQ). CBWFQ provides guaranteed bandwidth rate to a non-priority class. Under congestion conditions, the class receives the guaranteed bandwidth. To configure CBWFQ, use the bandwidth command.
Note
Restrictions and Usage Guidelines
The CBWFQ restrictions and usage guidelines are as follows:
•
•
•
•
•
•
Configuration Tasks
These sections describe the configuration tasks for CBWFQ:
•
•
Configuring a Service Policy in the Policy Map
To configure CBWFQ, use the Modular QoS CLI. Define the class of traffic with the class-map command, create a policy map that contains the bandwidth command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with CBWFQ and assign the policy to an interface, perform the following tasks in global configuration mode:
Step 1
Specifies the name of the policy map to configure.
Step 2
Specifies the name of a predefined class included in the service policy.
Step 3
Router(config-pmap-c)# bandwidth bandwidth-kbps | percent % of available bandwidth1 2
Specifies the percentage of available bandwidth in kilobits per second to be assigned to packets that meet the match criteria of the associated traffic class.
Step 4
Router(config)# interface interface-name
Specifies the interface to which the policy map will be applied.
Step 5
Router(config-if)# service-policy [output policy-name]
Attaches the specified policy map to the interface.
1 Only the parameters shown are supported.
2 The bandwidth command has a minimum rate that is one percent of the physical interface speed or the hierarchical shaped rate. See Table 9-1.
Displaying the CBWFQ Configuration and Statistics
Use the commands below to display the configuration of a service policy and its associated traffic classes:
This example shows the information displayed when you enter the show policy-map interface command:
Router1-PE# show policy-map interfacePOS6/2service-policy output:squeue stats for all priority classes:queue size 0, queue limit 32655packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0class-map:dscp0 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:ip dscp 0queue size 0, queue limit 610packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0shape:cir 2440000, Bc 9760, Be 9760(shape parameter is rounded to 2,439,000 bps due to granularity)
output bytes 0, shape rate 0 bpsclass-map:dscp1 (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:ip dscp 10 packets, 0 bytes30 second rate 0 bpsqueue size 0, queue limit 100000packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0bandwidth:kbps 400000, weight 64(bandwidth parameter is rounded to 397,592 kbps due to granularity)
class-map:dscp2 (match-all)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:ip dscp 2Priority:21% (130620 kbps), burst bytes 3265500, b/w exceed drops:0(Priority parameter is rounded to 129,278 kbps due to granularity)
class-map:class-default (match-any)0 packets, 0 bytes30 second offered rate 0 bps, drop rate 0 bpsmatch:any0 packets, 0 bytes30 second rate 0 bpsqueue size 0, queue limit 11422packets output 0, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0Configuration Example
This example shows how to configure traffic classes, create a service policy, and attach it to an interface:
Step 1
Router(config)# class-map class1 Router(config-cmap)# match ip dscp 30Router(config-cmap)# exitRouter(config)# class-map class2 Router(config-cmap)# match ip dscp 10Router(config-cmap)# exitStep 2
Router(config)# policy-map policy1Router(config-pmap)# class class1Router(config-pmap-c)# bandwidth 30000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# class class2Router(config-pmap-c)# bandwidth 20000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)#Step 3
Router(config)# interface pos 2/0 Router(config-if)# service-policy output policy1Router(config-if)# exitIn the following example, CBWFQ is configured on an OC-3 link. Class foo and class bar are guaranteed minimum bandwidth of 20 percent and 30 percent of link rate, respectively. The remaining bandwidth is equally distributed between class-default and class baz, each gets 25 percent of link rate. However, because class baz is shaped to receive a maximum of 15 Mbps (or 10 percent of the link rate), the bandwidth allocated to class baz is capped by this specified shape value, and class baz is guaranteed a minimum bandwidth of 15 Mbps.
class-map foomatch ip dscp 10class-map barmatch ip dscp 20class-map bazmatch ip dscp 30policy-map foobarclass foobandwidth percent 20%class barbandwidth percent 30%class bazshape average 15000000int pos2/0service-policy output foobarConfiguring Low Latency Queuing
Low latency queuing (LLQ) lets you specify low-latency behavior for a traffic class. LLQ allows delay-sensitive data to be given preferential treatment. You can give one or more classes priority status. You configure LLQ with the priority command.
The priority command configures guaranteed bandwidth to a priority class under worst-case congestion scenarios.
Restrictions and Usage Guidelines
The LLQ restrictions and usage guidelines are as follows:
•
•
•
•
•
•
•
•
•
Note
Configuration Tasks
To configure LLQ, use the Modular QoS CLI. Define the class of traffic with the class-map command, create a policy map that contains the priority command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with LLQ and to assign the policy to an interface, perform the following tasks in global configuration mode:
1 Only the parameters shown are supported.
Configuration Example
This example shows how to configure a priority queue (with a guaranteed allowed bandwidth of 50 Mbps) reserved for traffic with an IP DSCP value of 40:
Step 1
Router(config)# class-map gold-dataRouter(config-cmap)# match-any ip dscp 40Router(config-cmap)# exitRouter(config)# class-map match barRouter(config-cmap)# match-any ip dscp 8Router(config-cmap)# exitRouter(config)#Step 2
Router(config)# policy-map policy1Router(config-pmap)# class gold-dataRouter(config-pmap-c)# priority 50000Router(config-pmap)# class barRouter(config-pmap-c)# bandwidth 20000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface pos 4/1Router(config-if)# service-policy output policy1Router(config-if)# exit
Configuring Weighted Random Early Detection
Weighted Random Early Detection (WRED) is a congestion-avoidance mechanism that takes advantage of the congestion-control mechanism of TCP. By selectively dropping packets based on IP precedence prior to periods of high congestion, WRED tells the packet source to decrease its transmission rate. Edge routers assign IP precedence to packets as they enter the network. WRED is useful on any output interface where you expect to have congestion. However, WRED is usually used in the core routers of a network rather than at the edge. WRED uses these precedences to determine how it treats different types of traffic.
When a packet arrives, the average queue size is calculated and one of the following events occurs:
•
•
•
Restrictions and Usage Guidelines
The WRED restrictions and usage guidelines are as follows:
•
•
•
•
For more details on the queue calculations and how WRED works, refer to the section "About WRED" in the chapter "Congestion Avoidance Overview" in the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_c/index.htm
Configuration Tasks
To configure WRED, use the Modular QoS CLI. Define the class of traffic with the class-map command, create a policy map that contains the random-detect command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with WRED and to assign the policy to an interface, perform the following tasks in global configuration mode:
Configuration Example
This example shows how to configure WRED.
Router# config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map wred_testRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# random-detectRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface pos 7/1Router(config-if)# service-policy output wred_testRouter(config-if)# endRouter# show policy-map interface pos 7/1POS7/1Service-policy output: wred_testClass-map: class-default (match-any)16634097 packets, 8217243918 bytes30 second offered rate 482198000 bps, drop rate 0 bpsMatch: anyqueue size 0, queue limit 128packets output 16634097, packet drops 0tail/random drops 0, no buffer drops 0, other drops 0Random-detect:Exp-weight-constant: 3 (1/8)Mean queue depth: 0Class Random Tail Minimum Maximum Mark Outputdrop drop threshold threshold probability packets0 104806 0 32 64 1/10 30268121 104569 0 36 64 1/10 30270502 104732 0 40 64 1/10 30268843 104169 0 44 64 1/10 30274494 103047 0 48 64 1/10 30285695 103156 0 52 64 1/10 30284606 0 0 56 64 1/10 07 0 0 60 64 1/10 0
Configuring Hierarchical Traffic Shaping
Hierarchical traffic shaping allows multiple classes of traffic to be shaped at a single rate. A hierarchical traffic shaping policy consists of a child policy that identifies one or more classes of traffic, and a parent policy that shapes the output of the traffic classes into a single shape rate. You can apply a nested policy to an interface or subinterface.
Restrictions and Usage Guidelines
The hierarchical traffic shaping restrictions and usage guidelines are as follows:
•
•
Note
•
•
•
•
Note
Configuration Task
To configure hierarchical traffic shaping, use the Modular QoS CLI to define the parent and child polices. For the child policy, define the classes of traffic with the class-map command and create a policy with the policy-map command. For the parent policy, create a policy with the policy-map command, apply the child policy to the default class with the service-policy command, and apply the parent policy to the appropriate interface with the service-policy command.
To configure the classes of traffic, see the "Configuring Classification" section. To configure the child and parent policies for hierarchical traffic shaping, perform the following tasks in global configuration mode:
Step 1
Router(config)# policy-map child-policy-name
Specifies the name of the child policy map to configure.
Step 2
Router(config-pmap)# class class-name
Specifies the name of a predefined class included in the service policy.
Step 3
Router(config-pmap-c)# priority bandwidth-kbps | percent % of available bandwidth1
Gives priority to a class of traffic belonging to the policy map.
Step 4
Specifies the name of a predefined class included in the service policy.
Step 5
Router(config-pmap-c)# bandwidth bandwidth-kbps | percent % of available bandwidth2
Specifies the percentage of available bandwidth in kilobits per second to be assigned to packets that meet the match criteria of the associated traffic class.
Step 6
Router(config)# policy-map parent-policy-name
Specifies the name of the parent policy map to configure.
Step 7
Router(config-pmap)# class class-name
Specifies the name of a predefined class included in the service policy.
Step 8
Router(config-pmap-c)# shape average cir
Shapes traffic to the indicated bit rate for the specified class.
Step 9
Router(config-pmap-c)# service-policy child-policy-name
Links the parent and child policy and class.
Step 10
Router(config)# interface interface-name
Specifies the interface to which the policy map will be applied.
Step 11
Router(config-if)# service-policy [output parent-policy-name]
Attaches the specified nested parent and child policies to the interface.
1 Only the parameters shown are supported.
2 Only the parameters shown are supported.
Configuration Example
This example shows a nested traffic policy configuration where traffic matching the class called voice will be guaranteed 3200 Kbps, or 10% of parent_policy's shape average:
Router(config)# class-map match-all voiceRouter(config-cmap)# match ip dscp 5Router(config-cmap)# exitRouter(config)# policy-map child_policyRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority percent 10Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# policy-map parent_policyRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 32000000Router(config-pmap-c)# service-policy child_policyRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface Serial6/1:1.1 point-to-pointRouter(config-subif)# service-policy parent_policyConfiguring Queue Limit
For the class-based traffic shaping and CBWFQ features, you can specify or modify the maximum number of packets the queue can hold for a class policy configured in a policy map using the queue-limit command from policy-map class configuration mode.
Restrictions and Usage Guidelines
The queue limit restrictions and usage guidelines are as follows:
•
Note
•
•
Configuring Tasks
To configure the queue-limit, use the Modular QoS CLI. Define the class of traffic with the class-map command, create a policy map that contains the queue-limit command, and apply the policy to the appropriate interface with the service-policy command.
To configure the class of traffic, see the "Configuring Classification" section. To configure a policy with queue-limit and to assign the policy to an interface, perform the following tasks in global configuration mode:
Note
Configuration Example
In the following example, a policy map called policy11 is configured to contain policy for a class called cls203, and the queue limit is set to 42 packets.
Router(config)# policy-map policy11Router(config-pmap)# class cls203
Router(config-pmap-c)# queue-limit 42Configuring QoS: Match VLAN
The QoS: Match VLAN feature provides trunk VLAN match and classification in Modular QoS Command-Line Interface (MQC) class maps for the OSM-2+4GE-WAN+ interface.
Note
Classification based on the match vlan command is supported by the following QoS features:
•
•
•
•
•
Restrictions and Usage Guidelines
•
!policy not-supported-policyclass class-defaultshape average 100000000service-policy child-m-vlanPolicy Map child-m-vlanclass vlan150bandwidth 20 (%)!•
•
Configuration Tasks
To configure QoS: Match VLAN support, perform the following tasks, beginning in global configuration mode:
Configuration Examples
The following example shows a sample hierarchical match VLAN policy:
Router# configure terminal
Router(config)# policy-map vlan-pol-example
Router(config-pmap)# class vlan150
Router(config-pmap-c)# shape average 200000000 800000 800000
Router(config-pmap-c)# service-policy child
Router(config-pmap-c)# exit
Router(config-pmap)# class vlan170
Router(config-pmap-c)# shape average 200000000 800000 800000
Router(config-pmap-c)# service-policy child
!
Router(config)# policy-map child
Router(config-pmap)# Class prec2
Router(config-pmap-c)# bandwidth 20 (%)
Router(config-pmap)# Class prec3
Router(config-pmap-c)# bandwidth 30 (%)
Router(config-pmap)# Class prec1
Router(config-pmap-c)# bandwidth 10 (%)
The following example creates a class map for multiple VLANs, creates a policy map for shaping, and attaches an egress interface:
Router# configure terminalRouter(config)# class-map vlan_multiRouter(config-cmap)# match vlan 100-102 200 300Router(config-cmap# exitRouter(config)# policy-map pol_multi_vlanRouter(config-pmap)# class vlan_multiRouter(config-pmap-c)# shape average 100000000Router(config-pmap-c)# exitRouter(config)# interface ge7/1.100Router(config-subif)# encapsulation dot1q 100Router(config-subif)# no shutRouter(config-int)# interface ge7/1.101Router(config-subif)# encapsulation dot1q 101Router(config-subif)# no shutRouter(config-int)# interface ge7/1.102Router(config-subif)# encapsulation dot1q 102Router(config-subif)# no shutRouter(config-int)# interface ge7/1.200Router(config-subif)# encapsulation dot1q 200Router(config-subif)# no shutRouter(config-int)# interface ge7/1.300Router(config-subif)# encapsulation dot1q 300Router(config-subif)# no shutRouter(config-subif)# exitRouter(config)# interface ge7/1Router(config-int)# service-policy output pol_multi_vlanRouter(config-int)# no shutDistribution of Remaining Bandwidth
You can use MQC to specify how the "remaining" bandwidth is distributed among the output queues on a Cisco 7600 router interface or subinterface. "Remaining" bandwidth is the available bandwidth left on an interface or subinterface after all guaranteed traffic is accounted for. The amount of remaining bandwidth available for use is determined by the excess information rate (EIR) configured for the queue.
In MQC, the bandwidth remaining percent command allows you to configure the remaining bandwidth for output queues. See the "bandwidth remaining percent" section for more information.
The following example shows how to use the bandwidth remaining percent command to distribute percentages of remaining bandwidth to various traffic classes in a policy map.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# policy-map myPolicyRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# bandwidth remaining percent 20Router(config-pmap-c)# class prec1Router(config-pmap-c)# bandwidth remaining percent 30Router(config-pmap-c)# class prec2Router(config-pmap-c)# bandwidth remaining percent 10Router(config-pmap-c)# bandwidth percent 50Router(config-pmap-c)# ^ZRouter#20:44:36: %SYS-5-CONFIG_I: Configured from console by consoleRouter# show policy-map myPolicyPolicy Map myPolicyClass prec1bandwidth remaining percent 30Class prec2bandwidth percent 50bandwidth remaining percent 10Class class-defaultbandwidth remaining percent 20Command Reference
To specify how the "remaining" bandwidth is distributed among the output queues on a Cisco 7600 series router interface or subinterface, use the MQC bandwidth remaining percent command in policy-map class configuration mode. To remove the percentage of remaining bandwidth specified for a traffic class, use the no form of this command.
bandwidth remaining percent percentage
no bandwidth remaining percent percentage
Syntax Description
Defaults
This command has no default behavior or values.
Command Modes
Modular QoS policy-map class configuration
Command History
Usage Guidelines
Use the MQC bandwidth remaining percent command to specify how the "remaining" bandwidth is distributed among the output queues on a Cisco 7600 series router interface or subinterface. "Remaining" bandwidth is the available bandwidth left on an interface or subinterface after all guaranteed traffic is accounted for.
The bandwidth remaining percent command allows you to configure the remaining bandwidth for output queues. The percentage parameter specified with the bandwidth remaining percent command is translated into an internal excess information rate (EIR) value between 0 and 255. The aggregate of all user-configured EIR bandwidth percentages cannot exceed 100 percent.
If the aggregate of all remaining bandwidth is less than 100 percent, the remainder is evenly split among user queues (including the default queue) that do not have a remaining bandwidth percentage configured. The minimum EIR value of each output queue is 1.
The EIR parameter for the network control queue is fixed at 128 and is not configurable.
If you have not configured a committed information rate (CIR) value for the default queue and it is the only user queue, the default queue receives half of the remaining bandwidth percentage of the network control queue.
Unsupported Frame Relay-Specific QoS Features
The following Frame-Relay specific QoS features are not supported:
•
•
•
•
•
Cisco IPv6 QoS on the OSMs
Cisco IPv6 QoS on the OSMs supports all QoS features supported with IPv4 QoS. For general information on Cisco IPv6 QoS, see Implementing QoS for IPv6 for Cisco IOS Software at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_qosv6.htm
Restrictions and Usage Guidelines
The Cisco IPv6 QoS restrictions and usage guidelines are as follows:
•
•
•
•
•
