-
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4
-
Quality of Service Overview
- Part 1: Classification
- Part 2: Congestion Management
- Part 3: Congestion Avoidance
-
Part 4: Policing and Shaping
-
Policing and Shaping Overview
-
Configuring Traffic Policing
-
Configuring Traffic Policing
-
Traffic Policing
-
Two-Rate Policer
-
Policer Enhancement---Multiple Actions
-
Percentage-Based Policing and Shaping
-
Modular QoS CLI (MQC) Three-Level Hierarchical Policer
-
ATM Policing by Service Category for SVC/SoftPVC
-
Modular QoS CLI (MQC) Unconditional Packet Discard
-
Control Plane Policing
-
- Regulating Packet Flow
-
- Part 5: Signalling
- Part 6: Link Efficiency Mechanisms
- Part 7: Quality of Service Solutions
- Part 8: Modular Quality of Service Command-Line Interface
- Part 9: Security Device Manager
- Part 10: AutoQoS
-
Table Of Contents
Prerequisites for the AutoQoS for the Enterprise Feature
Restrictions for the AutoQoS for the Enterprise Feature
Information About the AutoQoS for the Enterprise Feature
Benefits of the AutoQoS for the Enterprise Feature
Auto-Discovery (Data Collection) Phase
AutoQoS Template Generation and Installation Phase
How to Configure the AutoQoS for the Enterprise Feature
Enabling the Auto-Discovery Phase
Enabling the AutoQoS Template Generation and Installation Phase
Verifying the AutoQoS for the Enterprise Configuration
Configuration Examples for the AutoQoS for the Enterprise Feature
Enabling the Auto-Discovery Phase: Example
Enabling the AutoQoS Template Generation Phase: Example
Verifying the AutoQoS for the Enterprise Configuration: Example
Feature Information for AutoQoS for the Enterprise
AutoQoS for the Enterprise
First Published: January 03, 2004Last Updated: June 24, 2009The AutoQoS for the Enterprise feature automates the deployment of quality of service (QoS) policies in a general business environment, particularly for midsize companies and branch offices of larger companies. Existing QoS policies may be present during the first configuration phase of this feature, that is, during the Auto-Discovery (data collection) phase. However, any existing QoS policies must be removed before the AutoQoS-generated polices are applied during the second configuration phase of this feature.
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 AutoQoS for the Enterprise" 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 the AutoQoS for the Enterprise Feature
•
•
•
•
•
Prerequisites for the AutoQoS for the Enterprise Feature
•
•
•
Restrictions for the AutoQoS for the Enterprise Feature
General Restrictions
•
–
–
–
The AutoQoS for the Enterprise feature is supported on low-speed and high-speed ATM PVCs in point-to-point subinterfaces.
Note
–
Serial Interface Restrictions
•
–
–
Frame Relay DLCI Restrictions
•
•
•
When MLPoFR is configured, this IP address is removed and put on the MLP bundle. The AutoQoS for the Enterprise feature must also be configured on the ATM side of the network.
•
ATM PVC Restrictions
•
•
When MLPoATM is configured, this IP address is removed and put on the MLP bundle. The AutoQoS for the Enterprise feature must also be configured on the ATM side of the network.
Cisco IOS Release 12.2(18)ZYA2 Restrictions
•
•
•
–
–
Information About the AutoQoS for the Enterprise Feature
To configure the AutoQoS for the Enterprise feature, you should understand the following concepts:
•
Benefits of the AutoQoS for the Enterprise Feature
The key benefits of the AutoQoS for the Enterprise feature include the following:
•
–
–
–
–
–
•
•
•
Design Considerations
General QoS Requirements
•
•
–
The LLQ (specifically, PQ) is applied to the voice packets to meet the latency requirements.
–
With cRTP, the 40-byte IP header of the voice packet is reduced from 2 to 4 bytes, thereby reducing voice bandwidth requirements. cRTP must be applied at both ends of a network link.
–
LFI is used to reduce the jitter of voice packets by preventing voice packets from getting delayed behind large data packets in a queue. LFI must be applied at both ends of a network link.
Bandwidth Implications
The bandwidth of the serial interface determines the speed of the link. The speed of the link, in turn, determines the configurations generated by the AutoQoS for the Enterprise feature.
Note
The AutoQoS for the Enterprise feature uses the bandwidth that is allocated at the time the feature is configured. The AutoQoS for the Enterprise feature does not respond to changes made to bandwidth after the feature is configured.
For example, if the auto qos command is used to configure the AutoQoS for the Enterprise feature on an interface with 1000 Kbps, the AutoQoS for the Enterprise feature generates configurations for high-speed interfaces. However, if the bandwidth is later changed to 500 Kbps, the AutoQoS for the Enterprise feature will not use the lower bandwidth. The AutoQoS for the Enterprise feature retains the higher bandwidth and continues to use the generated configurations for high-speed interfaces.
To force the AutoQoS for the Enterprise feature to generate configurations for the low-speed interfaces, perform the following tasks:
1.
2.
3.
4.
Fragmentation for Frame Relay Networks
For Frame Relay networks, fragmentation is configured using a delay of 10 milliseconds (ms) and a minimum fragment size of 60 bytes. This configuration ensures that the VoIP packets are not fragmented. However, when the G.711 coder-decoder (codec) is used on low-speed links, the fragment size configured by the AutoQoS for the Enterprise feature could be smaller than the size of the G.711 Voice over IP (VoIP) packet.
To solve this potential problem, choose one of the following:
•
•
For example, if the AutoQoS for the Enterprise feature is configured on a Frame Relay DLCI with 128 Kbps, the fragment size configured by the AutoQoS for the Enterprise feature will be 160 bytes. The size of the G.711 VoIP packet will be 160 bytes, minus the bytes in the packet headers for the layers. The workaround is to either change the fragment size from 160 bytes to 220 bytes or change the size of the G.711 VoIP packet from 160 bytes to 80 bytes.
Configuration Phases
The AutoQoS for the Enterprise feature consists of two configuration phases, completed in the following order:
•
The Auto-Discovery phase uses network-based application recognition (NBAR)-based protocol discovery to detect the applications on the network and performs statistical analysis on the network traffic.
•
This phase generates templates from the data collected during the Auto-Discovery phase and installs the templates on the interface. Then these templates are used as the basis for creating the class maps and policy maps for your network. After the class maps and policy maps are created, they are then installed on the interface.
In Cisco IOS Release 12.2(18)ZYA2, when AutoQos is configured, a global macro is also applied to the interface to perform lan-queueing actions. This macro contains commands to configure bandwidth, queue limit, and thresholds based on the traffic type, its priority and its rate. This data is collected during the Auto-Discovery phase.
Figure 1 below illustrates the top-level processes for configuring the AutoQoS for Enterprise feature. The dotted lines indicate optional processes.
Figure 1 Top-Level Processes for Configuring the AutoQoS for the Enterprise Feature
First, start the Auto-Discovery (data collection) phase by using the auto discovery qos command. Note the following points about the Auto-Discovery phase:
•
•
Second, start the AutoQoS template generation phase by using the auto qos command. This phase generates templates from the data collected during the Auto-Discovery phase. It then uses those templates as the basis for creating and installing the class maps and policy maps for your network.
Note
Detailed information about the Auto-Discovery phase and the AutoQoS template generation phase is provided below.
Auto-Discovery (Data Collection) Phase
The Auto-Discovery (data collection) phase uses NBAR to detect network applications as they arrive at an interface, collect data from the offered traffic, and perform statistical analysis.
The data collected should be a representative sampling of the volume and type of voice, video, and data on your network. Therefore, the amount of time devoted to data collection varies from network to network. Run the Auto-Discovery phase for as long as necessary. The length of time needed van vary, depending on the volume and nature of traffic on your network.
AutoQoS Template Generation and Installation Phase
This phase generates templates from the data collected during the Auto-Discovery phase and installs the templates on the interface. Then these templates are used as the basis for creating the class maps and policy maps for your network. After the class maps and policy maps are created, they are then installed on the interface.
During this phase, the AutoQoS for the Enterprise also assigns the appropriate bandwidth amounts and sets the appropriate scheduling parameters for the network traffic.
In Cisco IOS Release 12.2(18)ZYA2, a macro that contains mls qos commands to configure bandwidth, queue limit, and thresholds gets applied. To view these commands, use show run interface command. The commands will not be displayed as part of the show auto qos command.
AutoQos can be applied on an interface with input service policy applied, but no output service policy can be applied on the interface while applying AutoQos on it.
Class-Map Templates
The AutoQoS for the Enterprise feature creates a number of class-map templates, used for the following purposes:
•
•
In Cisco IOS Release 12.2(18)ZYA2, the PISA MQC is limited to 8 filters per class-map. To accommodate this, additional AutoQos classes have been added to honour the 8 filter per class limitation. Transactional, Bulk, Scavanger and Management have been split.
AutoQoS Classes
The AutoQoS for the Enterprise feature defines 10 AutoQoS classes, designed to accommodate various enterprise applications. Table 1 lists the AutoQoS class name, the type of traffic defined for the class, and the differentiated services code point (DSCP) value for the type of traffic, if applicable.
These classes are used with the modular quality of service (QoS) command-line interface (MQC) to configure class maps, once the classification (match) criteria are determined. The match criteria can be configured using the appropriate match protocol commands.
These classes are also chosen to meet the scheduling requirement in compliance with the DiffServ recommendations. Each class will be associated with an egress (output) queue. The applications mapped to a class will be put into the same queue and receive the same (weighted) queueing scheduling.
Note
AutoQoS Classification Using NBAR
NBAR is the classification mechanism for the AutoQoS for the Enterprise feature. NBAR is a Cisco product that classifies network traffic using information about the application such as protocol type, URL, and dynamically assigned ports.
All the NBAR-supported applications are mapped to the AutoQoS classes described in the "AutoQoS Classes" section.
The AutoQoS for the Enterprise feature provides static default mapping rules used to build the AutoQoS class-map templates. Table 2 lists each AutoQoS class, the application to which it is mapped, and the Cisco IOS match protocol command used in a policy map to establish the mapping.
1. In Cisco IOS Release 12.2(18)ZYA2 on the Cisco Catalyst 6500 series switch that is equipped with a Supervisor 32/PISA telepresence-media and telepresence-control packets are classified under AutoQos Class Interactive Video.
Table 3 lists the best-effort AutoQoS class (Best Effort), the application category for this class, and the NBAR protocols associated with this class.
Note
Table 4 lists the AutoQoS network routing protocol class (IP Routing), the application category for this class, and the NBAR protocols associated with this class.
Table 5 lists each AutoQoS management class (Network Management), the application to which it is mapped, and the Cisco IOS match protocol command used in a policy map to establish the mapping.
These AutoQoS classes and mapping scheme are used as the basic building blocks for packet classification. If these classes and this mapping scheme are not correct for your particular network, you can change them using the standard Cisco IOS commands and the MQC.
Trusted Boundary
A trusted boundary is the location in the network where the QoS marking is established. AutoQoS can be enabled with the trust keyword of the auto discovery qos command when the data collection phase in enabled.
Note
The AutoQoS classification for trusted marking will use DSCP match statements specified in Table 6.
When a marking is trusted, the following DSCP values are used in the match statements in the policy maps.
Policy-Map Templates
The policy-map templates created by the AutoQoS for the Enterprise feature are used to define the following three components:
•
•
•
These components are designed according to "best practice" recommendations and include QoS features for specific link types, such as low- and high-speed Frame Relay DLCIs.
How to Configure the AutoQoS for the Enterprise Feature
This section contains the following tasks. Each task is identified as either required or optional.
•
•
•
Enabling the Auto-Discovery Phase
The Auto-Discovery phase uses NBAR to detect network applications and protocols as they leave an interface, collect data from the offered traffic, and perform statistical analysis. The information collected will be used to build the AutoQoS templates. These templates are then used to create the appropriate class maps and policy maps described in the "AutoQoS Template Generation and Installation Phase" section.
To enable the Auto-Discovery phase, use the auto discovery qos command.
Prerequisites
Before using the auto discovery qos command at an interface or an ATM PVC, ensure that the following prerequisites have been met:
•
•
•
•
Restrictions
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface type number
Example:Router(config)# interface serial4/0
Configures an interface (or subinterface) type and enters interface configuration mode.
•
Step 4
bandwidth kilobits
Example:Router(config-if)# bandwidth 1540
(Optional) Sets a bandwidth value for an interface.
•
Note
Step 5
vbr-nrt output-pcr output-scr output-mbs [input-pcr] [input-scr] [input-mbs]
Example:Router(config-if)# vbr-nrt 10000 5000 32 20000 10000 64
(Optional) Configures the variable bit rate-nonreal time (VBR-NRT) QoS and specifies the output peak cell rate (PCR), output sustainable cell rate (SCR), and output maximum burst cell size (MBS) for an ATM PVC, PVC range, switched virtual circuit (SVC), virtual circuit (VC) class, or VC bundle member.
•
Note
Step 6
vbr-rt peak-rate average-rate burst
Example:Router(config-if)# vbr-rt 640 56 80
(Optional) Configures the real-time VBR for Voice over ATM connections.
•
Note
Step 7
Router(config-if-atm-vc)# cbr 56
(Optional) Configures the CBR for the ATM circuit emulation service (CES) for an ATM PVC.
This command can be used in different modes, including ATM-VC configuration mode (for ATM PVCs and SVCs), ATM PVC range configuration mode (for an ATM PVC range), or ATM PVC-in-range configuration mode (for an individual PVC within a PVC range).
•
Note
Step 8
pvc [name] vpi/vci [ces | ilmi | qsaal | smds]Example:Router(config-if)# pvc 1/32
(Optional) Creates or assigns a name to an ATM PVC and specifies the encapsulation type on an ATM PVC.
•
Note
Step 9
ip address ip-address mask [secondary]
Example:Router(config-if)# ip address 10.10.100.1 255.255.255.0
(Optional) Sets a primary or secondary IP address for an interface.
Note
Step 10
Router(config-if)# frame-relay interface-dlci 100
(Optional) Assigns a DLCI to a specified Frame Relay subinterface on the router or access server, or assigns a specific PVC to a DLCI, or applies a virtual template configuration for a PPP session.
•
Note
Step 11
auto discovery qos [trust]
Example:Router(config-if)# auto discovery qos
•
Note
Step 12
end
Example:Router(config-if)# end
(Optional) Returns to privileged EXEC mode.
What to Do Next
Use the auto qos command to generate and install the AutoQoS templates. These templates are generated on the basis of the data collected in the Auto-Discovery phase, and will be used to create and install the corresponding class maps and policy maps.
Enabling the AutoQoS Template Generation and Installation Phase
This phase generates templates on the basis of the data collected during the Auto-Discovery phase and then installs the templates on the interface. These templates are then used to create class maps and policy maps for use on your network. After they are created, the class maps and policy maps are also installed on the interface.
To enable the AutoQoS template generation and installation phase, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
Troubleshooting Tips
Below are answers to frequently asked questions (FAQs) and tips for troubleshooting situations that you may encounter when configuring or using the AutoQoS for the Enterprise feature.
Why can't I configure the AutoQoS for the Enterprise feature?
To configure the feature, CEF must be is enabled. Verify that CEF is enabled on your network.
Why isn't the AutoQoS for the Enterprise feature supported on my router?
The AutoQoS for the Enterprise feature is supported only on the IP Plus image for low-end platforms. Verify that you have the IP Plus image installed on your router.
Why are some of my QoS configurations still present after I disable the AutoQoS for the Enterprise feature?
You have to manually disable any QoS configurations that were modified by the AutoQoS for the Enterprise feature.
Why did my low-speed network link go down when I enabled the AutoQoS for the Enterprise feature?
Ensure that the AutoQoS for the Enterprise feature is enabled on both sides of the network link.
Why can't I establish an end-to-end connection on the Frame Relay link?
Check the bandwidth on both sides of the Frame Relay link. The bandwidth on both sides of the link must be the same; otherwise a fragmentation size mismatch occurs, and a connection cannot be established.
Note
What to Do Next
If the policy maps and class maps created (on the basis of the templates generated by the AutoQoS for the Enterprise feature) do not meet the needs of your network, the policy maps and class maps can be modified using the appropriate Cisco IOS commands.
Note
Verifying the AutoQoS for the Enterprise Configuration
The AutoQoS template generation phase of the AutoQoS for the Enterprise feature automatically generates templates that are, in turn, used to create policy maps and class maps. These policy maps and class maps configure the QoS features on your network.
To verify the configuration (that is, the policy maps and class maps), perform the following steps.
SUMMARY STEPS
1.
2.
and/or
3.
and/or
4.
5.
DETAILED STEPS
Configuration Examples for the AutoQoS for the Enterprise Feature
This section provides the following configuration examples:
•
•
•
Enabling the Auto-Discovery Phase: Example
In the following example, the Auto-Discovery phase of the AutoQoS for the Enterprise feature has been enabled on serial interface 4/0 by using the auto discovery qos command. In this example, the bandwidth has been specified, although this is optional. With this configuration, data about the network traffic will be collected using NBAR-based protocol discovery and the traffic on the network will be analyzed.
Router> enableRouter# configure terminalRouter(config)# interface seril4/0Router(config-if)# bandwidth 1540Router(config-if)# auto discovery qosRouter(config-if)# endEnabling the AutoQoS Template Generation Phase: Example
In the following example, the template generation phase of the AutoQoS for the Enterprise feature has been enabled on serial interface 4/0 by using the auto qos command. In the template generation phase, class maps and policy maps are created (and installed) on the basis of the information collected during the Auto-Discovery phase conducted earlier.
Router> enableRouter# configure terminalRouter(config)# interface serial4/0Router(config-if)# auto qosRouter(config-if)# endVerifying the AutoQoS for the Enterprise Configuration: Example
The AutoQoS template generation phase of the AutoQoS for the Enterprise feature automatically generates templates that are, in turn, used to create policy maps and class maps. These policy maps and class maps configure the QoS features on your network.
The output of the show auto discovery qos command, the show auto qos command, and the show policy-map interface command can be used to verify the contents of the policy maps and class maps created by this AutoQoS for the Enterprise feature. The following section contains sample output for each of these commands.
The following is sample output from the show auto discovery qos command. This example displays the data collected during the Auto-Discovery (data discovery) phase.
Router# show auto discovery qosSerial2/1.1AutoQoS Discovery enabled for applicationsDiscovery up time: 55 minutes, 52 secondsAutoQoS Class information:Class VoIP:Recommended Minimum Bandwidth: 517 Kbps/50% (PeakRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------rtp audio 2/<1 517/50 703104Class Interactive Video:Recommended Minimum Bandwidth: 24 Kbps/2% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------rtp video 24/2 5337/52 704574Class Control:Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------h323 0/0 74/7 30212rtcp 0/0 7/<1 1540Class Streaming Video:Recommended Minimum Bandwidth: 3 Kbps/<1% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------cuseeme 3/<1 6148/60 99038Class Transactional:Recommended Minimum Bandwidth: 1 Kbps/<1% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------sqlnet 1/<1 1706/16 40187Class Bulk:Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------ftp 0/0 313/30 74480Class Scavenger:Recommended Minimum Bandwidth: 1 Kbps (AverageRate)/0% (fixed).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------napster 1/<1 1429/13 33941Class Management:Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------dhcp 0/0 84/8 114480ldap 0/0 169/16 55364Class Routing:Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------icmp 0/0 2/<1 300Class Best Effort:Current Bandwidth Estimation: 350 Kbps/34% (AverageRate).Detected applications and data:Application/ AverageRate PeakRate TotalProtocol (kbps/%) (kbps/%) (bytes)----------- ----------- -------- ------------unknowns 336/32 99457/97 949276http 14/1 15607/15 41945The following is sample output from the show auto qos command. This example displays the templates created on the basis of the data collected during the data collection phase.
Router# show auto qos!policy-map AutoQoS-Policy-Se2/1.1class AutoQoS-Voice-Se2/1.1priority percent 50set dscp efclass AutoQoS-Inter-Video-Se2/1.1bandwidth remaining percent 10set dscp af41class AutoQoS-Stream-Video-Se2/1.1bandwidth remaining percent 1set dscp cs4class AutoQoS-Transactional-Se2/1.1bandwidth remaining percent 1set dscp af21class AutoQoS-Scavenger-Se2/1.1bandwidth remaining percent 1set dscp cs1class class-defaultfair-queue!policy-map AutoQoS-Policy-Se2/1.1-Parentclass class-defaultshape average 1024000service-policy AutoQoS-Policy-Se2/1.1!class-map match-any AutoQoS-Stream-Video-Se2/1.1match protocol cuseeme!class-map match-any AutoQoS-Transactional-Se2/1.1match protocol sqlnet!class-map match-any AutoQoS-Voice-Se2/1.1match protocol rtp audio!class-map match-any AutoQoS-Scavenger-Se2/1.1match protocol napster!class-map match-any AutoQoS-Inter-Video-Se2/1.1match protocol rtp video!rmon event 33333 log trap AutoQoS description "AutoQoS SNMP traps for Voice Drops" owner AutoQoSSerial2/1.1: DLCI 58 -!interface Serial2/1.1 point-to-pointframe-relay interface-dlci 58class AutoQoS-FR-Serial2/1-58!map-class frame-relay AutoQoS-FR-Serial2/1-58frame-relay cir 1024000frame-relay bc 10240frame-relay be 0frame-relay mincir 1024000service-policy output AutoQoS-Policy-Se2/1.1-ParentThe following sample output from the show policy-map interface command displays the packet statistics of the classes (for all service policies) configured by the AutoQoS for the Enterprise feature on the serial 2/1/1 subinterface.
Router# show policy-map interfaceSerial2/1.1: DLCI 58 -Service-policy output: AutoQoS-Policy-Se2/1.1-ParentClass-map: class-default (match-any)725797 packets, 224584146 bytes5 minute offered rate 3468000 bps, drop rate 2605000 bpsMatch: anyTraffic ShapingTarget/Average Byte Sustain Excess Interval IncrementRate Limit bits/int bits/int (ms) (bytes)1024000/1024000 6400 25600 25600 25 3200Adapt Queue Packets Bytes Packets Bytes ShapingActive Depth Delayed Delayed Active- 1000 268047 48786251 268032 48777309 yesService-policy : AutoQoS-Policy-Se2/1.1Class-map: AutoQoS-Voice-Se2/1.1 (match-any)80596 packets, 5158144 bytes5 minute offered rate 105000 bps, drop rate 14000 bpsMatch: protocol rtp audio80596 packets, 5158144 bytes5 minute rate 105000 bpsQueueingStrict PriorityOutput Queue: Conversation 72Bandwidth 70 (%)Bandwidth 716 (kbps) Burst 17900 (Bytes)(pkts matched/bytes matched) 82010/5248640(total drops/bytes drops) 12501/800064QoS Setdscp efPackets marked 82010Class-map: AutoQoS-Inter-Video-Se2/1.1 (match-any)50669 packets, 42473594 bytes5 minute offered rate 692000 bps, drop rate 513000 bpsMatch: protocol rtp video50669 packets, 42473594 bytes5 minute rate 692000 bpsQueueingOutput Queue: Conversation 73Bandwidth remaining 10 (%) Max Threshold 64 (packets)(pkts matched/bytes matched) 51558/43218807(depth/total drops/no-buffer drops) 9/37454/7588QoS Setdscp af41Packets marked 52193Class-map: AutoQoS-Stream-Video-Se2/1.1 (match-any)79843 packets, 30678725 bytes5 minute offered rate 511000 bps, drop rate 428000 bpsMatch: protocol cuseeme79843 packets, 30678725 bytes5 minute rate 511000 bpsQueueingOutput Queue: Conversation 74Bandwidth remaining 1 (%) Max Threshold 64 (packets)(pkts matched/bytes matched) 82381/31658370(depth/total drops/no-buffer drops) 0/63889/7245QoS Setdscp cs4Packets marked 82395Class-map: AutoQoS-Transactional-Se2/1.1 (match-any)77805 packets, 8511468 bytes5 minute offered rate 157000 bps, drop rate 102000 bpsMatch: protocol sqlnet77805 packets, 8511468 bytes5 minute rate 157000 bpsQueueingOutput Queue: Conversation 75Bandwidth remaining 1 (%) Max Threshold 64 (packets)(pkts matched/bytes matched) 80635/8820988(depth/total drops/no-buffer drops) 64/50967/3296QoS Setdscp af21Packets marked 80655Class-map: AutoQoS-Scavenger-Se2/1.1 (match-any)30723 packets, 7127736 bytes5 minute offered rate 136000 bps, drop rate 84000 bpsMatch: protocol napster30723 packets, 7127736 bytes5 minute rate 136000 bpsQueueingOutput Queue: Conversation 76Bandwidth remaining 1 (%) Max Threshold 64 (packets)(pkts matched/bytes matched) 31785/7373950(depth/total drops/no-buffer drops) 0/16381/6160QoS Setdscp cs1Packets marked 31955Class-map: class-default (match-any)406161 packets, 130634479 bytes5 minute offered rate 2033000 bps, drop rate 1703000 bpsMatch: anyQueueingFlow Based Fair QueueingMaximum Number of Hashed Queues 64(total queued/total drops/no-buffer drops) 806/291482/13603Additional References
The following sections provide references related to the AutoQoS for the Enterprise feature.
Related Documents
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples
NBAR
AutoQoS for voice over IP (VoIP)
"AutoQoS —VoIP" module
LFI and cRTP
"Header Compression" module
Packet classification
LLQ
Service policies (policy maps)
Frame Relay and ATM commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples
Frame Relay configuration
"Configuring Frame Relay" module
MLPPP
"Configuring Media-Independent PPP and Multilink PPP" module
CEF
SNMP
"Configuring SNMP Support" module
CiscoWorks QoS Policy Manager (QPM)
Product information available online at Cisco.com
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing standards has not been modified by this feature.
—
Technical Assistance
Feature Information for AutoQoS for the Enterprise
Table 7 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 and Catalyst OS 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
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card 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. (0907R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2004-2009 Cisco Systems, Inc. All rights reserved.
