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.
The 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.
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
The AutoQoS for the Enterprise feature is supported on low-speed and high-speed ATM PVCs in point-to-point subinterfaces.
Note |
An ATM PVC is classified as low speed if its bandwidth is less than or equal to 768 Kbps; an ATM PVC is classified as high speed if its bandwidth is greater than 768 Kpbs. |
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.
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.
The key benefits of the AutoQoS for the Enterprise feature include the following:
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.
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 |
Changing the bandwidth during configuring the AutoQoS for the Enterprise feature is not recommended. |
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 qoscommand 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:
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.
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.
The figure below 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 |
After the auto qos command has finished creating and installing the templates, creating the class maps and policy maps, and installing the class maps and policy maps on the interface, you can view the class maps and policy maps by using the show auto qos command. |
Detailed information about the Auto-Discovery phase and the AutoQoS template generation phase is provided below.
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.
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 qoscommand.
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.
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.
The AutoQoS for the Enterprise feature defines 10 AutoQoS classes, designed to accommodate various enterprise applications. The table below 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.
Table 1 | Class Definitions for the AutoQoS for the Enterprise Feature |
AutoQoS Class Name |
Traffic Type |
DSCP Value |
---|---|---|
IP Routing |
Network control traffic, such as routing protocols |
CS6 |
Interactive Voice |
Inactive voice-bearer traffic |
EF |
Interactive Video |
Interactive video data traffic |
AF41 |
Streaming Video |
Streaming media traffic |
CS4 |
Telephony Signaling |
Telephony signaling and control traffic |
CS3 |
Transactional/Interactive |
Database applications transactional in nature |
AF21 |
Network Management |
Network management traffic |
CS2 |
Bulk Data |
Bulk data transfers; web traffic; general data service |
AF11 |
Scavenger |
Casual entertainment; rogue traffic; traffic in this category is given less-than-best-effort treatment |
CS1 |
Best Effort |
Default class; all non-critical traffic; HTTP; all miscellaneous traffic |
0 |
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 |
The actual number of queues created corresponds to the number of applications (and then classes) discovered during AutoQoS-Discovery. |
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 Class-Map Templates section.
The AutoQoS for the Enterprise feature provides static default mapping rules used to build the AutoQoS class-map templates. The table below 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.
Table 2 | AutoQoS Classes, Applications, and match protocol Command |
AutoQoS Class |
Application |
match protocol Command |
---|---|---|
Interactive Voice |
VoIP bearer |
match protocol rtp voice match protocol cisco-phone match protocol vofr |
Interactive Video 1 |
Video conference |
match protocol rtp video |
Telephony Signaling |
Voice and video signaling and control |
match protocol rtcp match protocol h323 |
Streaming Video |
Streaming video |
match protocol cuseeme match protocol netshow match protocol realaudio match protocol streamwork match protocol vdolive |
Transactional/Interactive |
Database |
match protocol sap match protocol sqlnet match protocol sqlserver match protocol sqlexec match protocol citrix match protocol notes match protocol 1dap match protocol secure-1dap |
Interactive sessions |
match protocol telnet match protocol secure-telnet match protocol rtelnet match protocol xwindows match protocol ssh match protocol finger match protocol klogin match protocol kshell match protocol nickname match protocol vnc match protocol xdmcp |
|
Other enterprise applications |
match protocol novadigm match protocol pcanywhere match protocol appleqtc match protocol cobra-iiop match protocol dicom match protocol fix match protocol ibm-db2 match protocol hl7 match protocol ora-srv |
|
Bulk Data |
File transfer |
match protocol ftp match protocol secure-ftp match protocol nntp match protocol secure-ntp match protocol irc match protocol secure-irc match protocol tftp match protocol printer |
Bulk Data (Continued) |
match protocol cifs match protocol ipx match protocol microsoftds match protocol netbios match protocol winmx match protocol simap |
|
Email and groupware |
match protocol exchange match protocol smtp match protocol pop3 match protocol secure-pop3 match protocol mapi |
|
Scavenger |
Peer-to-peer file transfer |
match protocol napster match protocol fastrack match protocol gnutella match protocol kazaa2 match protocol bittorent match protocol edonkey match protocol directconnect |
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.
The table below lists the best-effort AutoQoS class (Best Effort), the application category for this class, and the NBAR protocols associated with this class.
Table 3 | Best Effort Class, Application Categories, and Associated NBAR Protocols |
Note |
NBAR allows new applications to be defined and added to the network by using different tools such as a Packet Description Language Module (PDLM). The AutoQoS class mapping can not be predetermined for these applications. Therefore, these new applications will be viewed as unknown and put into the AutoQoS default (that is, Best Effort) class. |
The table below lists the AutoQoS network routing protocol class (IP Routing), the application category for this class, and the NBAR protocols associated with this class.
Table 4 | IP Routing Class, Application Categories, and Associated NBAR Protocols |
AutoQoS Class |
Application Category |
NBAR Protocols |
||
---|---|---|---|---|
IP Routing
|
Network routing and signaling |
All supported network routing and signaling protocols. The list of NBAR supported protocols includes bgp, eigrp, rip, rsvp. |
The table below lists each AutoQoS management class (Network Management), the application to which it is mapped, and the Cisco IOS match protocolcommand used in a policy map to establish the mapping.
Table 5 | Network Management Class, Application Categories, and match protocol Command |
AutoQoS Class |
Application Category |
match protocol Command |
---|---|---|
Network Management |
Network Management |
match protocol snmp |
match protocol syslog |
||
match protocol systat |
||
match protocol dhcp |
||
match protocol dns |
||
match protocol ldap |
||
match protocol secure-ldap |
||
match protocol socks |
||
match protocol imap |
||
match protocol secure-imap |
||
match protocol kerberos |
||
match protocol tacacs |
||
match protocol daytime |
||
match protocol time |
||
match protocol npp |
||
match protocol echo |
||
match protocol isakmp |
||
match protocol clearcase |
||
match protocol lockd |
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.
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 |
In Cisco IOS Release 12.2(18)ZYA2 trusted boundary feature is not supported. |
The AutoQoS classification for trusted marking will use DSCP match statements specified in the table below.
When a marking is trusted, the following DSCP values are used in the match statements in the policy maps.
Table 6 | DSCP Values in Match Statements for Trusted Boundaries |
AutoQoS Class |
DSCP Values in Match Statements |
---|---|
IP Routing |
match ip dscp cs6 |
Interactive Voice |
match ip dscp ef |
Interactive Video |
match ip dscp af41 |
Streaming Video |
match ip dscp cs4 |
Telephony Signaling |
match ip dscp cs3 |
Transactional/Interactive |
match ip dscp af21 |
Network Management |
match ip dscp cs2 |
Bulk Data |
match ip dscp af11 |
Scavenger |
match ip dscp cs1 |
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.
Before using the auto discovery qos command at an interface or an ATM PVC, ensure that the following prerequisites have been met:
Note |
|
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# interface serial4/0 |
Configures an interface (or subinterface) type and enters interface configuration mode.
|
||
|
Example: Router(config-if)# bandwidth 1540 Example:
|
(Optional) Sets a bandwidth value for an interface.
|
||
|
Example: Router(config-if)# vbr-nrt 10000 5000 32 20000 10000 64 Example:
|
(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.
|
||
|
Example: Router(config-if)# vbr-rt 640 56 80 |
(Optional) Configures the real-time VBR for Voice over ATM connections.
|
||
|
Example: Router(config-if-atm-vc)# cbr 56 Example:
|
(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).
|
||
|
Example: Router(config-if)# pvc 1/32 Example:
|
(Optional) Creates or assigns a name to an ATM PVC and specifies the encapsulation type on an ATM PVC.
|
||
|
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.
|
||
|
Example: Router(config-if)# frame-relay interface-dlci 100 Example:
|
(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.
|
||
|
Example: Router(config-if)# auto discovery qos |
|
||
|
Example: Router(config-if)# end |
(Optional) Returns to privileged EXEC mode.
|
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.
Command or Action | Purpose | |||
---|---|---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
||
|
Example: Router# configure terminal |
Enters global configuration mode. |
||
|
Example: Router(config)# interface serial4/0 |
Configures an interface (or subinterface) type and enters interface configuration mode.
|
||
|
Example: Router(config-if)# bandwidth 1540 Example:
|
(Optional) Sets a bandwidth value for an interface.
|
||
|
Example: Router(config-if)# vbr-nrt 10000 5000 32 20000 10000 64 Example:
|
(Optional) Configures the VBR-NRT and specifies the output PCR, output SCR, and output MBS for an ATM PVC, PVC range, SVC, VC class, or VC bundle member.
|
||
|
Example: Router(config-if)# vbr-rt 640 56 80 |
(Optional) Configures the real-time VBR for Voice over ATM connections.
|
||
|
Example: Router(config-if-atm-vc)# cbr 56 Example:
|
(Optional) Configures the CBR for the ATM 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).
|
||
|
Example: Router(config-if)# pvc 1/32 Example:
|
(Optional) Creates or assigns a name to an ATM PVC and specifies the encapsulation type on an ATM PVC.
|
||
|
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.
|
||
|
Example: Router(config-if)# frame-relay interface-dlci 100 Example:
|
(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.
|
||
|
Example: Router(config-if)# auto qos |
|
||
|
Example: Router(config-if)# end |
(Optional) Returns to privileged EXEC mode.
|
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.
To configure the feature, CEF must be is enabled. Verify that CEF is enabled on your network.
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.
You have to manually disable any QoS configurations that were modified by the AutoQoS for the Enterprise feature.
Ensure that the AutoQoS for the Enterprise feature is enabled on both sides of the network 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 |
For more help, see the Troubleshooting Tips section. |
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 |
Although you can modify the policy maps and class maps, they may not be removed properly when the AutoQoS for the Enterprise feature is disabled using the no auto qoscommand. You may have to manually remove any modified policy maps and class maps. For more information about the no auto qoscommand, see the Cisco IOS Quality of Service Solutions Command Reference. |
Command or Action | Purpose | |
---|---|---|
|
Example: Router> enable |
Enables privileged EXEC mode.
|
|
Example: Router# show auto qos interface serial4/0 |
(Optional) Displays the AutoQoS templates created for a specific interface or all interfaces. |
|
|
|
|
Example: Router# show auto discovery qos interface serial4/0 |
(Optional) Displays the results of the data collected during the Auto-Discovery phase for a specific interface or all interfaces. |
|
|
|
|
Example: Router# show policy-map interface serial4/0 Example:
|
(Optional) Displays the packet statistics of all classes that are configured for all service policies either on the specified interface or subinterface or on a specific PVC on the interface.
|
|
Example: Router# exit |
(Optional) Exits privileged EXEC mode. |
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 qoscommand. 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> enable Router# configure terminal Router(config)# interface seril4/0 Router(config-if)# bandwidth 1540 Router(config-if)# auto discovery qos Router(config-if)# end
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 qoscommand. 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> enable Router# configure terminal Router(config)# interface serial4/0 Router(config-if)# auto qos Router(config-if)# end
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 qoscommand, the show auto qos command, and the show policy-map interfacecommand 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 qos
Serial2/1.1
AutoQoS Discovery enabled for applications
Discovery up time: 55 minutes, 52 seconds
AutoQoS Class information:
Class VoIP:
Recommended Minimum Bandwidth: 517 Kbps/50% (PeakRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
rtp audio 2/<1 517/50 703104
Class Interactive Video:
Recommended Minimum Bandwidth: 24 Kbps/2% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
rtp video 24/2 5337/52 704574
Class Control:
Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
h323 0/0 74/7 30212
rtcp 0/0 7/<1 1540
Class Streaming Video:
Recommended Minimum Bandwidth: 3 Kbps/<1% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
cuseeme 3/<1 6148/60 99038
Class Transactional:
Recommended Minimum Bandwidth: 1 Kbps/<1% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
sqlnet 1/<1 1706/16 40187
Class Bulk:
Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
ftp 0/0 313/30 74480
Class Scavenger:
Recommended Minimum Bandwidth: 1 Kbps (AverageRate)/0% (fixed).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
napster 1/<1 1429/13 33941
Class Management:
Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
dhcp 0/0 84/8 114480
ldap 0/0 169/16 55364
Class Routing:
Recommended Minimum Bandwidth: 0 Kbps/0% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
icmp 0/0 2/<1 300
Class Best Effort:
Current Bandwidth Estimation: 350 Kbps/34% (AverageRate).
Detected applications and data:
Application/ AverageRate PeakRate Total
Protocol (kbps/%) (kbps/%) (bytes)
----------- ----------- -------- ------------
unknowns 336/32 99457/97 949276
http 14/1 15607/15 41945
The 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.1
class AutoQoS-Voice-Se2/1.1
priority percent 50
set dscp ef
class AutoQoS-Inter-Video-Se2/1.1
bandwidth remaining percent 10
set dscp af41
class AutoQoS-Stream-Video-Se2/1.1
bandwidth remaining percent 1
set dscp cs4
class AutoQoS-Transactional-Se2/1.1
bandwidth remaining percent 1
set dscp af21
class AutoQoS-Scavenger-Se2/1.1
bandwidth remaining percent 1
set dscp cs1
class class-default
fair-queue
!
policy-map AutoQoS-Policy-Se2/1.1-Parent
class class-default
shape average 1024000
service-policy AutoQoS-Policy-Se2/1.1
!
class-map match-any AutoQoS-Stream-Video-Se2/1.1
match protocol cuseeme
!
class-map match-any AutoQoS-Transactional-Se2/1.1
match protocol sqlnet
!
class-map match-any AutoQoS-Voice-Se2/1.1
match protocol rtp audio
!
class-map match-any AutoQoS-Scavenger-Se2/1.1
match protocol napster
!
class-map match-any AutoQoS-Inter-Video-Se2/1.1
match protocol rtp video
!
rmon event 33333 log trap AutoQoS description "AutoQoS SNMP traps for Voice Drops" owner AutoQoS
Serial2/1.1: DLCI 58 -
!
interface Serial2/1.1 point-to-point
frame-relay interface-dlci 58
class AutoQoS-FR-Serial2/1-58
!
map-class frame-relay AutoQoS-FR-Serial2/1-58
frame-relay cir 1024000
frame-relay bc 10240
frame-relay be 0
frame-relay mincir 1024000
service-policy output AutoQoS-Policy-Se2/1.1-Parent
The following sample output from the show policy-map interfacecommand 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 interface
Serial2/1.1: DLCI 58 -
Service-policy output: AutoQoS-Policy-Se2/1.1-Parent
Class-map: class-default (match-any)
725797 packets, 224584146 bytes
5 minute offered rate 3468000 bps, drop rate 2605000 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
1024000/1024000 6400 25600 25600 25 3200
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 1000 268047 48786251 268032 48777309 yes
Service-policy : AutoQoS-Policy-Se2/1.1
Class-map: AutoQoS-Voice-Se2/1.1 (match-any)
80596 packets, 5158144 bytes
5 minute offered rate 105000 bps, drop rate 14000 bps
Match: protocol rtp audio
80596 packets, 5158144 bytes
5 minute rate 105000 bps
Queueing
Strict Priority
Output Queue: Conversation 72
Bandwidth 70 (%)
Bandwidth 716 (kbps) Burst 17900 (Bytes)
(pkts matched/bytes matched) 82010/5248640
(total drops/bytes drops) 12501/800064
QoS Set
dscp ef
Packets marked 82010
Class-map: AutoQoS-Inter-Video-Se2/1.1 (match-any)
50669 packets, 42473594 bytes
5 minute offered rate 692000 bps, drop rate 513000 bps
Match: protocol rtp video
50669 packets, 42473594 bytes
5 minute rate 692000 bps
Queueing
Output Queue: Conversation 73
Bandwidth remaining 10 (%) Max Threshold 64 (packets)
(pkts matched/bytes matched) 51558/43218807
(depth/total drops/no-buffer drops) 9/37454/7588
QoS Set
dscp af41
Packets marked 52193
Class-map: AutoQoS-Stream-Video-Se2/1.1 (match-any)
79843 packets, 30678725 bytes
5 minute offered rate 511000 bps, drop rate 428000 bps
Match: protocol cuseeme
79843 packets, 30678725 bytes
5 minute rate 511000 bps
Queueing
Output Queue: Conversation 74
Bandwidth remaining 1 (%) Max Threshold 64 (packets)
(pkts matched/bytes matched) 82381/31658370
(depth/total drops/no-buffer drops) 0/63889/7245
QoS Set
dscp cs4
Packets marked 82395
Class-map: AutoQoS-Transactional-Se2/1.1 (match-any)
77805 packets, 8511468 bytes
5 minute offered rate 157000 bps, drop rate 102000 bps
Match: protocol sqlnet
77805 packets, 8511468 bytes
5 minute rate 157000 bps
Queueing
Output Queue: Conversation 75
Bandwidth remaining 1 (%) Max Threshold 64 (packets)
(pkts matched/bytes matched) 80635/8820988
(depth/total drops/no-buffer drops) 64/50967/3296
QoS Set
dscp af21
Packets marked 80655
Class-map: AutoQoS-Scavenger-Se2/1.1 (match-any)
30723 packets, 7127736 bytes
5 minute offered rate 136000 bps, drop rate 84000 bps
Match: protocol napster
30723 packets, 7127736 bytes
5 minute rate 136000 bps
Queueing
Output Queue: Conversation 76
Bandwidth remaining 1 (%) Max Threshold 64 (packets)
(pkts matched/bytes matched) 31785/7373950
(depth/total drops/no-buffer drops) 0/16381/6160
QoS Set
dscp cs1
Packets marked 31955
Class-map: class-default (match-any)
406161 packets, 130634479 bytes
5 minute offered rate 2033000 bps, drop rate 1703000 bps
Match: any
Queueing
Flow Based Fair Queueing
Maximum Number of Hashed Queues 64
(total queued/total drops/no-buffer drops) 806/291482/13603
Related Topic |
Document Title |
---|---|
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
Cisco IOS Quality of Service Solutions Command Reference |
NBAR |
"Classifying Network Traffic Using NBAR" module |
AutoQoS for voice over IP (VoIP) |
"AutoQoS --VoIP" module |
LFI and cRTP |
"Header Compression" module |
Packet classification |
"Classifying Network Traffic" module |
LLQ |
"Configuring Weighted Fair Queueing" module |
Service policies (policy maps) |
"Applying QoS Features Using the MQC" module |
Frame Relay and ATM commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples |
Cisco IOS Wide-Area Networking Command Reference |
Frame Relay configuration |
"Configuring Frame Relay" module |
MLPPP |
"Configuring Media-Independent PPP and Multilink PPP" module |
SNMP |
"Configuring SNMP Support" module |
CiscoWorks QoS Policy Manager (QPM) |
Product information available online at Cisco.com |
Standard |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIB |
MIBs Link |
---|---|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFC |
Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 7 | Feature Information for AutoQoS for the Enterprise |
Feature Name |
Releases |
Feature Information |
---|---|---|
AutoQos for the Enterprise |
12.2(18)ZYA2 12.3(7)T |
The 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. In Release 12.3(7)T, this feature was introduced. In Release 12.2(18)ZYA2, support was added for the Cisco Catalyst 6500. The following commands were introduced or modified: auto discovery qos, auto qos, show auto discovery qos, show auto qos. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.