Prerequisites for Auto-QoS
The prerequisites for auto-QoS are the same as the prerequisites for standard QoS.
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 prerequisites for auto-QoS are the same as the prerequisites for standard QoS.
The following are restrictions for auto-QoS:
Auto-qos is not supported on SVI interfaces.
Do not configure the auto qos voip cisco-phone option for IP phones that support video. This option causes DSCP markings of video packets to get overwritten, because these packets do not have Expedited Forwarding priority, which results in these packets getting classified in the class-default class.
Information About Configuring Auto-QoS
You can use the auto-QoS feature to simplify the deployment of QoS features. Auto-QoS determines the network design and enables QoS configurations so that the switch can prioritize different traffic flows.
The switch employs the MQC model. This means that instead of using certain global configurations, auto-QoS applied to any interface on a switch configures several global class maps and policy maps.
Auto-QoS matches traffic and assigns each matched packet to qos-groups. This allows the output policy map to put specific qos-groups into specific queues, including into the priority queue.
QoS is needed in both directions, both on inbound and outbound. When inbound, the switch port needs to trust the DSCP in the packet (done by default). When outbound, the switch port needs to give voice packets "front of line" priority. If voice is delayed too long by waiting behind other packets in the outbound queue, the end host drops the packet because it arrives outside of the receive window for that packet.
When you enter an auto-QoS command, the switch displays all the generated commands as if the commands were entered from the CLI. You can use the auto-QoS compact feature to hide the auto-QoS generated commands from the running configuration. This would make it easier to comprehend the running-configuration and also help to increase efficient usage of memory.
In general, an auto-QoS command generates a series of class maps that either match on ACLs or on DSCP and/or CoS values to differentiate traffic into application classes. An input policy is also generated, which matches the generated classes and in some cases, polices the classes to a set bandwidth. Eight egress-queue class maps are generated. The actual egress output policy assigns a queue to each one of these eight egress-queue class maps.
The auto-QoS commands only generate templates as needed. For example, the first time any new auto-QoS command is used, global configurations that define the eight queue egress service-policy are generated. From this point on, auto-QoS commands applied to other interfaces do not generate templates for egress queuing because all auto-QoS commands rely on the same eight queue models, which have already been generated from the first time a new auto-QoS command was used.
After entering the appropriate auto-QoS command, the following actions occur:
Specific class maps are created.
Specific policy maps (input and output) are created.
Policy maps are attached to the specified interface.
Trust level for the interface is configured.
When auto-QoS is enabled, the auto qos interface configuration commands and the generated global configuration are added to the running configuration.
The switch applies the auto-QoS-generated commands as if the commands were entered from the CLI. An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions may occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the switch without saving the current configuration to memory. If the generated commands are not applied, the previous running configuration is restored.
If auto-QoS compact is enabled:
Only the auto-QoS commands entered from the CLI are displayed in running-config.
The generated global and interface configurations are hidden.
When you save the configuration, only the auto-qos commands you have entered are saved (and not the hidden configuration).
When you reload the switch, the system detects and re-executes the saved auto-QoS commands and the AutoQoS SRND4.0 compliant config-set is generated.
![]() Note |
Do not make changes to the auto-QoS-generated commands when auto-QoS compact is enabled, because user-modifications are overridden when the switch reloads. |
When auto-qos global compact is enabled:
show derived-config command can be used to view hidden Auto-QoS global Compact derived commands.
Auto-QoS global Compact commands will not be stored to memory. They will be regenerated every time the switch is reloaded.
When compaction is enabled, auto-qos generated commands should not be modified.
If the interface is configured with auto-QoS and if Auto-QoS global Compact needs to be disabled, auto-QoS should be disabled at interface level first.
How to configure Auto-QoS
For optimum QoS performance, configure auto-QoS on all the devices in your network.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
configure terminal Example:
|
Enters global configuration mode. |
||
Step 2 |
interface interface-id Example:
|
Specifies the port that is connected to a VoIP port, video device, or the uplink port that is connected to another trusted switch or router in the network interior, and enters the interface configuration mode. |
||
Step 3 |
Depending on your auto-QoS configuration, use one of the following commands:
Example:
|
The following commands enable auto-QoS for VoIP:
The following commands enable auto-QoS for the specified video device (system, camera, or media player):
The following command enables auto-QoS for classification:
The following commands enable auto-QoS for trusted interfaces:
|
||
Step 4 |
end Example:
|
Returns to privileged EXEC mode. |
||
Step 5 |
show auto qos interface interface-id Example:
|
(Optional) Displays the auto-QoS command on the interface on which auto-QoS was enabled. Use the show running-config command to display the auto-QoS configuration and user modifications. |
Prior to upgrading, you need to remove all auto-QoS configurations currently on the switch. This sample procedure describes that process.
After following this sample procedure, you must then reboot the switch with the new or upgraded software image and reconfigure auto-QoS.
Step 1 |
show auto qos Example:
In privileged EXEC mode, record all current auto QoS configurations by entering this command. |
Step 2 |
no auto qos Example:
In interface configuration mode, run the appropriate no auto qos command on each interface that has an auto QoS configuration. |
Step 3 |
Example:
Return to privileged EXEC mode, and record any remaining auto QoS maps class maps, policy maps, access lists, table maps, or other configurations by entering this command. |
Step 4 |
no policy-map policy-map_name Example:
In global configuration mode, remove the QoS class maps, policy maps, access-lists, table maps, and any other auto QoS configurations by entering these commands:
|
Step 5 |
Example:
Return to privileged EXEC mode, run this command again to ensure that no auto-QoS configuration or remaining parts of the auto-QoS configuration exists |
Step 6 |
show auto qos Example:
Run this command to ensure that no auto-QoS configuration or remaining parts of the configuration exists. |
Step 7 |
write memory Example:
Write the changes to the auto QoS configuration to NV memory by entering the write memory command. |
Reboot the switch with the new or upgraded software image.
After rebooting with the new or upgraded software image, re-configure auto-QoS for the appropriate switch interfaces as determined by running the show auto qos command described in step 1.
![]() Note |
There is only one table-map for exceed and another table-map for violate markdown per switch or stack. If the switch already has a table-map under the exceed action, then the auto-qos policy cannot be applied. |
To enable auto-QoS compact, enter this command:
Command or Action | Purpose | |
---|---|---|
Step 1 |
configure terminal Example:
|
Enters global configuration mode. |
Step 2 |
auto qos global compact Example:
|
Enables auto-Qos compact and generates (hidden) the global configurations for auto-QoS. You can then enter the auto-QoS command you want to configure in the interface configuration mode and the interface commands that the system generates are also hidden. To display the auto-QoS configuration that has been applied, use these the privileged EXEC commands:
|
To disable auto-QoS compact, remove auto-Qos instances from all interfaces by entering the no form of the corresponding auto-QoS commands and then enter the no auto qos global compact global configuration command.
Command |
Description |
---|---|
show auto qos [interface [interface-id]] |
Displays the initial auto-QoS configuration. You can compare the show auto qos and the show running-config command output to identify the user-defined QoS settings. |
show running-config |
Displays information about the QoS configuration that might be affected by auto-QoS. You can compare the show auto qos and the show running-config command output to identify the user-defined QoS settings. |
show derived-config |
Displays the hidden mls qos command which get configured along with the running configs because of auto-qos template. |
To troubleshoot auto-QoS, use the debug auto qos privileged EXEC command. For more information, see the debug auto qos command in the command reference for this release.
To disable auto-QoS on a port, use the no form of the auto qos command interface configuration command, such as no auto qos voip . Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos voip command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration).
Configuration Examples for Auto-QoS
The following is an example of the auto qos trust cos command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-Trust-Cos-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigE1/0/2
Device(config-if)# auto qos trust cos
Device(config-if)# end
Device# show policy-map interface HundredGigE1/0/2
HundredGigE1/0/2
Service-policy input: AutoQos-4.0-Trust-Cos-Input-Policy
Class-map: class-default (match-any)
0 packets
Match: any
QoS Set
cos cos table AutoQos-4.0-Trust-Cos-Table
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
0 packets
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (7500000 kbps), burst bytes 187500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
0 packets
Match: dscp cs2 (16) cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
queue-limit dscp 56 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
0 packets
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
0 packets
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
0 packets
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
0 packets
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
0 packets
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
0 packets
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos trust dscp command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-Trust-Dscp-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigE1/0/2
Device(config-if)# auto qos trust dscp
Device(config-if)# end
Device#show policy-map interface HundredGigE1/0/2
HundredGigE1/0/2
Service-policy input: AutoQos-4.0-Trust-Dscp-Input-Policy
Class-map: class-default (match-any)
0 packets
Match: any
QoS Set
dscp dscp table AutoQos-4.0-Trust-Dscp-Table
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
0 packets
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: dscp 5
Priority: 30% (30000000 kbps), burst bytes 750000000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
0 packets
Match: dscp cs2 (16) cs3 (24) cs6 (48) cs7 (56)
Match: dscp 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
queue-limit dscp 56 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
0 packets
Match: dscp af41 (34) af42 (36) af43 (38)
Match: dscp 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
0 packets
Match: dscp af21 (18) af22 (20) af23 (22)
Match: dscp 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
0 packets
Match: dscp af11 (10) af12 (12) af13 (14)
Match: dscp 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
0 packets
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
0 packets
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
0 packets
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos video cts command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-Trust-Cos-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigabitEthernet1/0/2
Device(config-if)# auto qos video cts
Device(config-if)# end
Device# show policy-map interface HundredGigabitEthernet1/0/2
HundredGigabitEthernet1/0/2
Service-policy input: AutoQos-4.0-Trust-Cos-Input-Policy
Class-map: class-default (match-any)
Match: any
QoS Set
cos cos table AutoQos-4.0-Trust-Cos-Table
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
Match: dscp cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos video ip-camera command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-Trust-Dscp-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigabitE1/0/2
Device(config-if)# auto qos video ip-camera
Device(config-if)# end
Device# show policy-map interface HundredGigabitE1/0/2
HundredGigabitE1/0/2
Service-policy input: AutoQos-4.0-Trust-Dscp-Input-Policy
Class-map: class-default (match-any)
Match: any
QoS Set
dscp dscp table AutoQos-4.0-Trust-Dscp-Table
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
Match: dscp cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos video media-player command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-Trust-Dscp-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigabitE1/0/2
Device(config-if)# auto qos video media-player
Device(config-if)# end
Device# show policy-map interface HundredGigabitE1/0/2
HundredGigabitE1/0/2
Service-policy input: AutoQos-4.0-Trust-Dscp-Input-Policy
Class-map: class-default (match-any)
Match: any
QoS Set
dscp dscp table AutoQos-4.0-Trust-Dscp-Table
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
Match: dscp cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos voip trust command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-Trust-Cos-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigabitE1/0/3
Device(config-if)# auto qos voip trust
Device(config-if)# end
Device# show policy-map interface HundredGigabitE1/0/3
HundredGigabitE1/0/3
Service-policy input: AutoQos-4.0-Trust-Cos-Input-Policy
Class-map: class-default (match-any)
Match: any
QoS Set
cos cos table AutoQos-4.0-Trust-Cos-Table
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
Match: dscp cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos voip cisco-phone command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-CiscoPhone-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
AutoQos-4.0-Voip-Data-Class (match-any)
AutoQos-4.0-Voip-Signal-Class (match-any)
AutoQos-4.0-Default-Class (match-any)
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigabitE1/0/5
Device(config-if)# auto qos voip cisco-phone
Device(config-if)# end
Device# show policy-map interface HundredGigabitE1/0/5
HundredGigabitE1/0/5
Service-policy input: AutoQos-4.0-CiscoPhone-Input-Policy
Class-map: AutoQos-4.0-Voip-Data-Class (match-any)
Match: ip dscp ef (46)
QoS Set
ip dscp ef
police:
cir 128000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Voip-Signal-Class (match-any)
Match: ip dscp cs3 (24)
QoS Set
ip dscp cs3
police:
cir 32000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Default-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-Default
QoS Set
dscp default
police:
cir 10000000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: class-default (match-any)
Match: any
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
Match: dscp cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos voip cisco-softphone command and the applied policies and class maps.
The following policy maps are created and applied when running this command:
AutoQos-4.0-CiscoSoftPhone-Input-Policy
AutoQos-4.0-Output-Policy
The following class maps are created and applied when running this command:
AutoQos-4.0-Voip-Data-Class (match-any)
AutoQos-4.0-Voip-Signal-Class (match-any)
AutoQos-4.0-Multimedia-Conf-Class (match-any)
AutoQos-4.0-Bulk-Data-Class (match-any)
AutoQos-4.0-Transaction-Class (match-any)
AutoQos-4.0-Scavanger-Class (match-any)
AutoQos-4.0-Signaling-Class (match-any)
AutoQos-4.0-Default-Class (match-any)
class-default (match-any)
AutoQos-4.0-Output-Priority-Queue (match-any)
AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
AutoQos-4.0-Output-Trans-Data-Queue (match-any)
AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
AutoQos-4.0-Output-Scavenger-Queue (match-any)
AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Device(config)# interface HundredGigE1/0/20
Device(config-if)# auto qos voip cisco-softphone
Device(config-if)# end
Device# show policy-map interface HundredGigE1/0/20
HundredGigE1/0/20
Service-policy input: AutoQos-4.0-CiscoSoftPhone-Input-Policy
Class-map: AutoQos-4.0-Voip-Data-Class (match-any)
Match: ip dscp ef (46)
QoS Set
ip dscp ef
police:
cir 128000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Voip-Signal-Class (match-any)
Match: ip dscp cs3 (24)
QoS Set
ip dscp cs3
police:
cir 32000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Multimedia-Conf-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-MultiEnhanced-Conf
QoS Set
dscp af41
police:
cir 5000000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Bulk-Data-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-Bulk-Data
QoS Set
dscp af11
police:
cir 10000000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Transaction-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-Transactional-Data
QoS Set
dscp af21
police:
cir 10000000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Scavanger-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-Scavanger
QoS Set
dscp cs1
police:
cir 10000000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Signaling-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-Signaling
QoS Set
dscp cs3
police:
cir 32000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: AutoQos-4.0-Default-Class (match-any)
Match: access-group name AutoQos-4.0-Acl-Default
QoS Set
dscp default
police:
cir 10000000 bps, bc 8000 bytes, be 8000 bytes
conformed 0 bytes; actions:
transmit
exceeded 0 bytes; actions:
set-dscp-transmit dscp table policed-dscp
violated 0 bytes; actions:
drop
conformed 0000 bps, exceed 0000 bps, violate 0000 bps
Class-map: class-default (match-any)
Match: any
Service-policy output: AutoQos-4.0-Output-Policy
queue stats for all priority classes:
Queueing
priority level 1
(total drops) 0
(bytes output) 0
Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,
Priority Level: 1
Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
Match: dscp cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing
queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 4%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
Match: dscp cs1 (8)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 1%
queue-buffers ratio 10
Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10
Class-map: class-default (match-any)
Match: any
Queueing
(total drops) 0
(bytes output) 0
bandwidth remaining 25%
queue-buffers ratio 25
The following is an example of the auto qos global compact command.
Device# configure terminal
Device(config)# auto qos global compact
Device(config)# interface HundredGigE1/0/2
Device(config-if)# auto qos voip cisco-phone
Device# show auto qos
HundredGigE1/0/2
auto qos voip cisco-phone
Device# show running-config interface HundredGigE1/0/2
interface HundredGigE1/0/2
auto qos voip cisco-phone
end
Review the QoS documentation if you require any specific QoS changes to your auto-QoS configuration.
This table provides release and related information for features explained in this module.
These features are available on all releases subsequent to the one they were introduced in, unless noted otherwise.
Release |
Feature |
Feature Information |
---|---|---|
Cisco IOS XE Fuji 16.9.2 |
Auto-QoS |
Auto-QoS feature simplifies the deployment of QoS features. This feature determines the network design and enables QoS configurations so that the switch can prioritize different traffic flows. |
Cisco IOS XE Cupertino 17.9.1 |
Auto-QoS |
This feature was implemented on C9200CX-12P-2X2G, C9200CX-8P-2X2G, and C9200CX-12T-2X2G models of the Cisco Catalyst 9200CX Series Switches, which were introduced in this release. |
Use Cisco Feature Navigator to find information about platform and software image support. To access Cisco Feature Navigator, go to Cisco Feature Navigator.