-
Catalyst 6500 Series Software Configuration Guide, 7.6
-
Preface
-
Product Overview
-
Command-Line Interfaces
-
Configuring the Switch IP Address and Default Gateway
-
Configuring Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet Switching
-
Configuring Ethernet VLAN Trunks
-
Configuring EtherChannel
-
Configuring IEEE 802.1Q Tunneling and Layer 2 Protocol Tunneling
-
Configuring Spanning Tree
-
Configuring Spanning Tree PortFast, UplinkFast, BackboneFast, and Loop Guard
-
Configuring VTP
-
Configuring VLANs
-
Configuring InterVLAN Routing
-
Configuring CEF for PFC2
-
Configuring MLS
-
Configuring NDE
-
Configuring Access Control
-
Configuring GVRP
-
Configuring Dynamic Port VLAN Membership with VMPS
-
Checking Status and Connectivity
-
Administering the Switch
-
Configuring Switch Access Using AAA
-
Configuring Redundancy
-
Modifying the Switch Boot Configuration
-
Working with the Flash File System
-
Working with System Software Images
-
Working with Configuration Files
-
Configuring System Message Logging
-
Configuring DNS
-
Configuring CDP
-
Configuring UDLD
-
Configuring NTP
-
Configuring Broadcast Suppression
-
Configuring Layer 3 Protocol Filtering
-
Configuring the IP Permit List
-
Configuring Port Security
-
Configuring 802.1x Authentication
-
Configuring Unicast Flood Blocking
-
Configuring SNMP
-
Configuring RMON
-
Configuring SPAN and RSPAN
-
Using Switch TopN Reports
-
Configuring Multicast Services
-
Configuring QoS
-
Configuring Automatic QoS
-
Configuring ASLB
-
Configuring the Switch Fabric Module
-
Configuring a VoIP Network
-
Acronyms
-
Table Of Contents
Understanding How Automatic QoS Works
Typical CoS and DSCP Values for Voice and Video Networks
Automatic QoS Configuration Guidelines and Restrictions
Clearing the QoS Configuration
Global Automatic QoS Detail Settings
Port-Specific Automatic QoS Macro
Port-Specific Automatic QoS Settings for ciscoipphone
Port-Specific Automatic QoS Settings for ciscosoftphone
Port-Specific Automatic QoS Settings for trust cos
Port-Specific Automatic QoS Settings for trust dscp
CLI Interface for Automatic QoS
Global Automatic QoS Macro—set qos autoqos
Port-Specific Automatic QoS Macro—set port qos autoqos
Detailed Automatic QoS Configuration Statements
Port-Specific Automatic QoS—voip ciscoipphone
Port-Specific Automatic QoS—voip ciscosoftphone
Port-Specific Automatic QoS—trust cos
Port-Specific Automatic QoS—trust dscp
Interface Change for All Ports Required—Warning Level
Other Relevant syslog Messages
Device No Longer Detected on the Port—Notice Level (Trusted Boundary Feature)
Device Detected on the Port—Notice Level
CDP Disabled with Trust-Dev Configured—Warning Level
Summary of Automatic QoS Features
Global Automatic QoS features (set qos autoqos)
Port-Based Automatic QoS Features
Using Automatic QoS in Your Network
Using Automatic QoS
This chapter describes how to use the automatic quality of service (QoS) configuration features on the Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Catalyst 6000 Family Switch Command Reference publication.
Note
This chapter consists of these sections:
•
•
Understanding How Automatic QoS Works
Automatic QoS consists of a macro that simplifies QoS configuration on the Catalyst 6500 series switches. The automatic QoS macro covers all the QoS configuration tasks that are required for implementing the recommended Architecture for Voice, Video, and Integrated Data (AVVID) settings for a voice port.
Automatic QoS focuses on the voice networks that are built using the Cisco IP Phone 79xx series and the Cisco SoftPhone. However, other phones can equally benefit from the automatically configured QoS settings. With automatic QoS, you use keywords, such as ciscoipphone or ciscosoftphone, or other AVVID types to allow you to specify the type of QoS parameters that you desire on a particular port. With automatic QoS, all appropriate QoS settings (Internet Engineering Task Force (IETF)-recommended values and proven AVVID settings) are applied to the port.
QoS Overview
These sections provide an overview of QoS:
•
Typical CoS and DSCP Values for Voice and Video Networks
The IETF recommends that you use several values for the different traffic types that are found in voice and video networks. Automatic QoS uses these values to configure such QoS parameters as CoS-to-queue maps, differentiated services code point (DSCP)-to-CoS maps, and so on.
The Catalyst 6500 series switches use the differentiated services (DIFFSERV) model for QoS; the model outlines three traffic types:
•
•
•
Four traffic classes exist within the AF class. The classes are denoted by AFXY where X is the class number and Y is the drop precedence number. X corresponds to a queue, and Y corresponds to a drop precedence value within the queue (either WRED or tail-drop). EF has the highest priority, BE has the lowest priority, and the priority for AF is somewhere in between.
See Table 44-1 for the recommended CoS and DSCP values for voice networks and other traffic types. The values listed are assumed when configuring the CoS-to-queue maps and other CoS/DSCP value-dependent configurations with the automatic QoS macro.
Table 44-1 Typical CoS and DSCP values in Cisco Voice and Video Networks
0
0
Default traffic (BE class)
3
26 (IETF recommended)
Voice/video call control/signaling (TCP)
AF31 class5
46 (IETF recommended)
Voice-bearer stream (RTP/UDP)
EF class4
34 (IETF recommended)
Video-bearer stream
AF41 class2
18 (From Cisco Encore architecture)
Mission critical/transactional traffic
AF21 class (from Cisco Encore architecture)1
10 (From Cisco Encore architecture)
Streaming video (not interactive)
AF11 (from Cisco Encore architecture)6
48
Routing protocols (as default)
7
Spanning Tree Protocol
1 Some values differ from the current QoS default values for Catalyst software (such as CoS-to-DSCP maps).
The priorities for these CoS/DSCP values are as follows:
•
•
•
•
•
For ports that do not implement a priority queue, WRED and tail-drop mechanisms are used to attain traffic prioritization within the queue. See the "Global Automatic QoS Detail Settings" section for specific scheduling settings.
QoS Scenario—Cisco IP Phone
In most configurations, the Cisco IP Phone 79xx is connected directly to the Catalyst switch port. Optionally, you can attach a PC to the phone and use the phone as a hop to the switch.
Typically, the traffic that comes from the phone and enters the switch is marked with a tag using the 802.1Q/p header. The header contains the VLAN information and the CoS 3-bit field. The CoS determines the priority of the packet. The switch uses the CoS field to distinguish the PC traffic from the phone traffic. The switch can also use the DSCP field for the same purpose.
In most Cisco IP Phone 79xx configurations, the traffic that comes from the phone and enters the switch is trusted. You set the port trust to trust-cos to properly prioritize the voice traffic over other types of traffic in the network.
The Cisco IP Phone 79xx has a built in switch that mixes the traffic that comes from the PC, the phone, and the switch port. The Cisco IP Phone 79xx has trust and classification capabilities that you need to configure. For more information, see the "Port-Specific Automatic QoS Settings for ciscosoftphone" section.
QoS Scenario—Cisco SoftPhone
The Cisco SoftPhone is a software product that runs on a standard PC and emulates an IP phone. The main difference between the Cisco SoftPhone and the Cisco IP Phone 79xx is that the Cisco SoftPhone marks its voice traffic through a DSCP, while the Cisco IP Phone 79xx marks its traffic through a CoS. The QoS settings on the switch accommodate this behavior by trusting the Layer 3 marking of the traffic entering the port. All other behavior is similar to the Cisco IP Phone 79xx.
Automatic QoS Macro
These sections describe the automatic QoS macro:
•
•
•
•
•
•
Automatic QoS Overview
The automatic QoS macro is divided into these two separate components:
•
•
Tip
Automatic QoS Configuration Guidelines and Restrictions
These sections provide the configuration guidelines and restrictions for automatic QoS:
•
Configuration Files
Creating commands (macros) that implement other commands can lead to conflicting commands. For example, if you configure a CoS-to-queue map with a certain setting and then enable the automatic QoS macro feature, the macro that you enabled will alter the CoS-to-queue map.
To avoid conflicting commands, the configuration file includes all the legacy commands that are included in the macro. The actual macro command does not appear in the configuration file; instead, all the existing configuration commands that result from executing the macro are included in the configuration file. For example, when you enter the set qos autoqos command and then enter the write config command, all existing QoS-related CLI commands display, excluding the actual macro command itself.
Supported Phones
When you use the automatic QoS feature with the ciscoipphone keyword, some of the QoS configuration requires phone-specific configuration (trust-ext, ext-cos) which is supported only on the following phones: Cisco IP Phone 7910, Cisco IP Phone 7940, Cisco IP Phone 7960, and Cisco IP Phone 7935. However, the ciscoipphone keyword is not exclusive to these models only; any phone can benefit from all the other QoS settings that are configured on the switch.
Cisco SoftPhone is supported through the ciscoipsoftphone keyword.
CDP Dependencies
To configure the QoS settings and the trusted boundary feature on the Cisco IP Phone, you must enable Cisco Discovery Protocol (CDP) version 2 or later on the port. If you enable the trusted boundary feature, a syslog warning message displays if CDP is not enabled or if CDP is running version 1.
You need to enable CDP only for the ciscoipphone QoS configuration; CDP does not affect the other components of the automatic QoS features. When you use the ciscoipphone keyword with the port-specific automatic QoS feature, a warning displays if the port does not have CDP enabled. See the "CDP Warning" section.
COPS Considerations
You can configure a port for local policy or Common Open Policy Service (COPS) policy. This setting specifies whether the port should get its QoS configuration information from a local configuration or through a COPS server. If you enable COPS on the port as well as globally enable COPS, the policy that is specified by the COPS server applies. If you disable COPS and/or the configured policy is local, the local configuration QoS policy applies.
Automatic QoS affects only the local policy on a port. If you execute automatic QoS on a port whose configured policy is currently set to COPS, the policy reverts to local policy. The global QoS policy reverts to local (through the global automatic QoS command), and the port-based policy reverts to local (through the port-based automatic QoS command). A warning displays if the policy of a port or global policy has been changed from COPS to local. For more information, see the "COPS Warning Message" section. Any existing COPS roles that are already associated with the port are not changed.
RSVP Considerations
All global and port-based Resource Reservation Protocol (RSVP)-related settings (including the RSVP [Designated Subnet Bandwidth Manager] DBSM election settings) are not changed by the automatic QoS macros.
Current QoS Default Settings
All current QoS settings are applied as described in the "Detailed Automatic QoS Configuration Statements" section. Some of these QoS settings reflect the current QoS defaults. After automatic QoS has been applied, all QoS settings, regardless of whether or not they were defaults, are applied on the port/switch.
EtherChannel Considerations
The global automatic QoS command supports channeling. All outbound QoS is configured for all channeling or nonchanneling interfaces. Channeling is not supported with the per-port automatic QoS commands.
Video Traffic Considerations
The CoS and DSCP values that are associated with the video traffic are prioritized for the global QoS settings. For more information, see the "Typical CoS and DSCP Values for Voice and Video Networks" section.
Clearing the QoS Configuration
Clearing the QoS configuration resets the configuration to the default QoS values. The automatic QoS features do not alter the default values.
PFC/PFC2 Support
No PFC or PFC2 is required for the ciscoipphone and trust cos keywords. A PFC or PFC2 is required for the ciscosoftphone and trust dscp keywords.
1p1q0t/1p3q1t Port Support
All 1p1q0t/1p3q1t ports must either be in port-based mode or VLAN-based mode. If a change is required (for example, if the port was configured for VLAN-based mode before you executed automatic QoS), a syslog message displays. The message indicates that a change to an interface type was needed that affected all ports in the module. For more information, see the "Interface Change for All Ports Required—Warning Level" section.
Global Automatic QoS Macro
These sections describe the global automatic QoS macro:
•
Overview
Both egress and ingress QoS must be configured for QoS to function properly. Because any traffic type can egress on any given port, egress QoS settings must have global QoS settings. The settings take into account all possible traffic types that are listed in the "Typical CoS and DSCP Values for Voice and Video Networks" section. Egress QoS settings are applied to all ports in the switch. Global QoS settings cover ingress scheduling settings, because the granularity CoS-to-queue mapping is port-type specific and not port specific. Port-specific QoS settings, such as QoS ACLs, port trust, and default CoS, are not altered.
Global Automatic QoS Detail Settings
Table 44-2 through Table 44-6 list the values of all the QoS parameters that are configured through the global automatic QoS command.
Note
Table 44-2 Switch-Wide Settings (Global QoS Settings)
CoS-to-DSCP map
0 10 18 26 34 46 48 56 (bold indicates nondefault values)
IP-precedence-to-DSCP map
0 10 18 26 34 46 48 56 (bold indicates nondefault values)
DSCP-to-CoS map
{0-7}, {8-15}, {16-23}, {24-31}, {32-39}, {40-47}, {48-55}, {56-63} (as per default)
Policed-DSCP map
As per default with 46:0 and 26:0 (see the "Global Automatic QoS Macro" section)
Policed-DSCP map excess rate
As per default (see the "Global Automatic QoS Macro" section)
Default QoS IP ACL
ip dscp 0 (as per default)
Port-Specific Automatic QoS Macro
The port-specific automatic QoS macro handles all inbound QoS configuration that is specific to a particular traffic type. Support is implemented for ciscoipphone, ciscosoftphone, and trust. See the "CLI Interface for Automatic QoS" section for the associated CLI commands.
The QoS ingress port-specific settings include port trust, default CoS, classification, and policing but does not include scheduling. Input scheduling is programmed through the global automatic QoS macro. Together with the global automatic QoS macro command, all QoS settings are configured properly for a specific QoS traffic type.
That existing QoS ACLs that are already associated with a port are removed when the ACL mappings change. The ACL names and instances are not changed.
These sections describe the port-specific automatic QoS macro:
•
•
•
•
Port-Specific Automatic QoS Settings for ciscoipphone
With the ciscoipphone keyword, the port is set up to trust-cos as well as to enable the trusted boundary feature. Combined with the global automatic QoS command, all settings are configured on the switch to properly handle the signaling and voice bearer and PC data entering and leaving the port.
In addition to the switch-side QoS settings covered by the global automatic QoS command, the phone has a few QoS features that need to be configured for proper labeling to occur. QoS configuration information is sent to the phone through CDP from the switch. The QoS values that need to be configured are the trust setting of the "PC port" on the phone (trust or untrusted) and the CoS value that is used by the phone to remark packets in case the port is untrusted (ext-cos).
AVVID recommends an untrusted and cos-ext value of 0. PC traffic that enters the switch is marked with CoS 0 by the phone, the voice bearer traffic that is generated by the phone is always labeled with CoS 5, and the signaling is labeled with CoS 3.
Table 44-7 lists the port-specific settings that are implemented after executing the automatic QoS ciscoipphone macro on a port. See the "Port-Specific Automatic QoS—voip ciscoipphone" section for detailed configuration examples.
Note
1 Only IP QoS ACLs are applied (not IPX).
2 If the ACL_IP-PHONES name is already in use, the name ACL_IP-PHONESx, where x is a value from 1 to 99, will be tried sequentially. If all these names are taken, a syslog message displays.
Port-Specific Automatic QoS Settings for ciscosoftphone
On the ports that connect to a Cisco SoftPhone, QoS settings must be configured to trust the Layer 3 markings of the traffic that enters the port. Trusting all Layer 3 markings is a security risk because PC users could send nonpriority traffic with DSCP 46 and gain unauthorized performance benefits. Policing on all inbound traffic prevents malicious users from obtaining unauthorized bandwidth from the network. Policing is accomplished by rate limiting the DSCP 46 (EF) inbound traffic to the codec rate used by the Cisco SoftPhone application (worst case G.722). Any traffic that exceeds this rate is marked down to the default traffic rate (DSCP 0 - BE). Signaling traffic (DSCP 26) is also policed and marked down to zero if excess signaling traffic is detected. All other inbound traffic types are reclassified to default traffic (DSCP 0 - BE).
Caution
Table 44-8 lists the port-specific settings that are implemented after executing the automatic QoS voip ciscosoftphone macro on a port. See the "Port-Specific Automatic QoS—voip ciscosoftphone" section for detailed configuration examples.
Table 44-8 Port-Specific Settings for Voice (ciscosoftphone Keyword)
Interface type
Port-based
Policy source—config
Local
Policy source—runtime
Local
Trust type—config
untrusted
Trust type—runtime
untrusted
Default CoS—config
0
Default CoS—runtime
0
Trust-device
none
Trust-ext
Untrusted
Cos-ext
0
QoS ACL attached to port
trust-dscp aggregate POLICE_SOFTPHONE-DSCP46-x-y any dscp-field 461 , 2
trust-dscp aggregate POLICE_SOFTPHONE-DSCP26-x-y any dscp-field 26 *
QoS ACL name
QoS policers
aggregate POLICE_SOFTPHONE-DSCP46-3-1 rate 320 burst 20 policed-dscp
aggregate POLICE_SOFTPHONE-DSCP26-3-1 rate 32 burst 8 policed-dscp
QoS policer names
POLICE_SOFTPHONE-DSCP46-x-y
POLICE_SOFTPHONE-DSCP26-x-y
1 x = module number (interface on which the port-based automatic QoS macro is applied).
2 y = port number (if a range is specified, use the first number in the range).
3 Only IP QoS ACLs are applied (not IPX).
4 If ACL_IP-SOFTPHONE-x-y name is already in use, the name ACL_IP-SOFTPHONE-x-y-z, where z is a value from 1 to 99, will be tried sequentially. If all these names are taken, an error message displays. A similar action is taken with the policer name (see the "Out of Policer Names" section).
Policing Configuration for ciscosoftphone
Two rate limiters are associated with the interface on which the ciscosoftphone port-based automatic QoS macro is executed. The two rate limiters ensure all inbound traffic on a Cisco SoftPhone port has the following characteristics:
1.
2.
3.
Action 3 is accomplished by the default QoS ACL. Any traffic exceeding actions (1) or (2) are policed-dscp back to zero (remarked back to DSCP 0 - BE).
DSCP 46 is policed at the rate of 320 kbps with a burst of 20 kb. DSCP 26 is policed at 32 kbps with a burst of 8 kb. The burst and rate values are based on worst case G.722 codec with 256 kbps (maximum packet length of 256 bytes) and minor signaling with a maximum packet length of 1000 bytes. Signaling is transmitted with DSCP 26 and the bearer channel of the SoftPhone stream with DSCP 46.
The port is set to untrusted for all port types to prevent ingress QoS scheduling. The global automatic QoS macro configures the policed-dscp-map to make sure DSCP 46 is marked down to DSCP 0 and DSCP 26 is marked down to DSCP 0. The global automatic QoS macro configures the default QoS IP ACL that is used to remark all other traffic to DSCP 0.
Limitations for ciscosoftphone
Because there is a limit on the total number of policers and QoS ACLs that are supported on the Catalyst 6500 series switches, similar limitations are associated with the ciscosoftphone automatic QoS macro. Up to 1023 aggregate policers are supported. Approximately 500 Cisco SoftPhone interfaces are supported (less interfaces are supported when other QoS ACLs and security ACLs are configured).
With a large number of Cisco SoftPhone interfaces, both bootup time and NVRAM space could be affected. Bootup time increases with a large number of Cisco SoftPhone instances. It is possible to run out of NVRAM space with a high number of Cisco SoftPhone instances. To avoid the NVRAM space issue, you might need to use the text configuration mode. For more information, see the "Out of TCAM Space" section.
Port-Specific Automatic QoS Settings for trust cos
The trust cos automatic QoS keyword is used for ports requiring a "trust all" solution. The keyword should only be used on ports connecting other switches or known servers as the port trusts all inbound traffic marking in Layer 2 (CoS). The trusted boundary feature is disabled, and no QoS policing is configured on these types of ports.
Table 44-9 outlines the details of the configuration after executing the automatic QoS trust macro on a port. See the "Port-Specific Automatic QoS—trust cos" section for detailed configuration examples.
1 Only IP QoS ACLs are applied (not IPX).
2 If the ACL_IP- TRUSTCOS name is already in use, the name ACL_IP- TRUSTCOSx , where x is a value from 1 to 99, will be tried sequentially. If all these names are taken, a syslog message is displayed.
Port-Specific Automatic QoS Settings for trust dscp
The trust dscp automatic QoS keyword is used for ports requiring a "trust all" type of solution. This keyword should be used only on ports that connect to other switches or known servers as the port will be trusting all inbound traffic marking Layer 3 (DSCP). The trusted boundary feature is disabled and no QoS policing is configured on these types of ports.
Table 44-10 outlines the details of the configuration after executing the automatic QoS trust macro on a port. See the "Port-Specific Automatic QoS Settings for trust dscp" section for detailed configuration examples.
1 Only IP QoS ACLs are applied (not IPX).
2 If the ACL_IP-TRUSTDSCP name is already in use, the name ACL_IP-TRUSTDSCPx, where x is a value from 1 to 99, will be tried sequentially. If all these names are taken, a syslog message is displayed.
CLI Interface for Automatic QoS
These sections describe the CLI interface for automatic QoS:
•
•
Global Automatic QoS Macro—set qos autoqos
When you execute the global automatic QoS macro, all the global QoS settings are applied to all ports in the switch. After completion, a prompt displays showing the CLI for the port-based automatic QoS commands that are currently supported.
Console> (enable) set qos autoqos ?Usage: set qos autoqosConsole> (enable) set qos autoqosQoS is enabled.........All ingress and egress QoS scheduling parameters configured on all ports.CoS to DSCP, DSCP to COS, IP Precedence to DSCP and policed dscp maps configured. Global QoS configured, port specific autoqos recommended:set port qos <mod/port> autoqos trust <cos|dscp>set port qos <mod/port> autoqos voip <ciscoipphone|ciscosoftphone>Console> (enable)Port-Specific Automatic QoS Macro—set port qos autoqos
The port-specific automatic QoS macro accepts a mod/port combination and must include an AVVID-type keyword. The ciscoipphone, ciscosoftphone, and trust keywords are supported.
This example shows how to use the ciscoipphone keyword:
Console> (enable) set port qos 3/1 autoqos helpUsage: set port qos <mod/port> autoqos trust <cos|dscp>set port qos <mod/port> autoqos voip <ciscoipphone|ciscosoftphone>Console> (enable) set port qos 3/1 autoqos voip ciscoipphonePort 3/1 ingress QoS configured for Cisco IP Phone.It is recommended to execute the "set qos autoqos" global command if not executed previously.Console> (enable)This example shows how to use the ciscosoftphone keyword:
Console> (enable) set port qos 3/1 autoqos voip ciscosoftphonePort 3/1 ingress QoS configured for Cisco Softphone.It is recommended to execute the "set qos autoqos" global command if not executed previously.Console> (enable)This example shows how to use the trust cos keyword:
Console> (enable) set port qos 3/1 autoqos trust cosPort 3/1 QoS configured to trust all incoming CoS marking.It is recommended to execute the "set qos autoqos" global command if not executed previously.Console> (enable)This example shows how to use the trust dscp keyword:
Console> (enable) set port qos 3/1 autoqos trust dscpPort 3/1 QoS configured to trust all incoming DSCP marking.It is recommended to execute the "set qos autoqos" global command if not executed previously.Console> (enable)Displaying QoS Settings
Use the existing QoS show commands to display the QoS settings. These commands include show port qos and show qos info runtime.
Detailed Automatic QoS Configuration Statements
These sections provide detailed automatic QoS configuration statements:
•
•
•
•
Global Automatic QoS Macro
The global automatic QoS command results in the following configuration:
set qos autoqos---------------set qos enableset qos policy-source localset qos ipprec-dscp-map 0 10 18 26 34 46 48 56set qos cos-dscp-map 0 10 18 26 34 46 48 56set qos dscp-cos-map 0-7:0 8-15:1 16-23:2 24-31:3 32-39:4 40-47:5 48-55:6 56-63:7set qos acl default-action ip dscp 0set qos map 2q2t tx queue 2 2 cos 5,6,7set qos map 2q2t tx queue 2 1 cos 1,2,3,4set qos map 2q2t tx queue 1 1 cos 0set qos drop-threshold 2q2t tx queue 1 100 100set qos drop-threshold 2q2t tx queue 2 80 100set qos drop-threshold 1q4t rx queue 1 50 60 80 100set qos txq-ratio 2q2t 80 20set qos wrr 2q2t 100 255set qos map 1p3q1t tx 1 1 cos 0set qos map 1p3q1t tx 2 1 cos 1,2set qos map 1p3q1t tx 3 1 cos 3,4set qos map 1p3q1t tx 3 0 cos 6,7set qos map 1p3q1t tx 4 cos 5set qos wrr 1p3q1t 20 100 200set qos wred 1p3q1t queue 1 70:100set qos wred 1p3q1t queue 2 70:100set qos wred 1p3q1t queue 3 70:90set qos map 1p1q0t rx 1 cos 0,1,2,3,4set qos map 1p1q0t rx 2 cos 5,6,7set qos rxq-ratio 1p1q0t 80 20set qos map 1p2q2t tx 1 2 cos 0set qos map 1p2q2t tx 2 1 cos 1,2,3,4set qos map 1p2q2t tx 2 2 cos 6,7set qos map 1p2q2t tx 3 cos 5set qos txq-ratio 1p2q2t 75 15 15set qos wrr 1p2q2t 50 255set qos wred 1p2q2t queue 1 1 40:70set qos wred 1p2q2t queue 1 2 70:100set qos wred 1p2q2t queue 2 1 40:70set qos wred 1p2q2t queue 2 2 70:100set qos map 1p1q4t rx 1 1 cos 0set qos map 1p1q4t rx 1 3 cos 1,2,3,4set qos map 1p1q4t rx 1 4 cos 6,7set qos map 1p1q4t rx 2 cos 5set qos drop-threshold 1p1q4t rx queue 1 50 60 80 100set qos map 1p2q1t tx 1 1 cos 0set qos map 1p2q1t tx 2 1 cos 1,2,3,4set qos map 1p2q1t tx 2 cos 6,7set qos map 1p2q1t tx 3 cos 5set qos txq-ratio 1p2q1t 75 15 15set qos wrr 1p2q1t 50 255set qos wred 1p2q1t queue 1 70:100set qos wred 1p2q1t queue 2 70:100set qos map 1p1q8t rx 1 1 cos 0set qos map 1p1q8t rx 1 5 cos 1,2set qos map 1p1q8t rx 1 8 cos 3,4set qos map 1p1q8t rx 2 cos 5,6,7set qos wred 1p1q8t queue 1 1 40:70set qos wred 1p1q8t queue 1 5 60:90set qos wred 1p1q8t queue 1 8 70:100set qos rxq-ratio 1p1q8t 80 20set qos policed-dscp-map 0:0set qos policed-dscp-map 1:1set qos policed-dscp-map 2:2set qos policed-dscp-map 3:3set qos policed-dscp-map 4:4set qos policed-dscp-map 5:5set qos policed-dscp-map 6:6set qos policed-dscp-map 7:7set qos policed-dscp-map 8:8set qos policed-dscp-map 9:9set qos policed-dscp-map 10:10set qos policed-dscp-map 11:11set qos policed-dscp-map 12:12set qos policed-dscp-map 13:13set qos policed-dscp-map 14:14set qos policed-dscp-map 15:15set qos policed-dscp-map 16:16set qos policed-dscp-map 17:17set qos policed-dscp-map 18:18set qos policed-dscp-map 19:19set qos policed-dscp-map 20:20set qos policed-dscp-map 21:21set qos policed-dscp-map 22:22set qos policed-dscp-map 23:23set qos policed-dscp-map 24:24set qos policed-dscp-map 25:25set qos policed-dscp-map 26:0set qos policed-dscp-map 27:27set qos policed-dscp-map 28:28set qos policed-dscp-map 29:29set qos policed-dscp-map 30:30set qos policed-dscp-map 31:31set qos policed-dscp-map 32:32set qos policed-dscp-map 33:33set qos policed-dscp-map 34:34set qos policed-dscp-map 35:35set qos policed-dscp-map 36:36set qos policed-dscp-map 37:37set qos policed-dscp-map 38:38set qos policed-dscp-map 39:39set qos policed-dscp-map 40:40set qos policed-dscp-map 41:41set qos policed-dscp-map 42:42set qos policed-dscp-map 43:43set qos policed-dscp-map 44:44set qos policed-dscp-map 45:45set qos policed-dscp-map 46:0set qos policed-dscp-map 47:47set qos policed-dscp-map 48:48set qos policed-dscp-map 49:49set qos policed-dscp-map 50:50set qos policed-dscp-map 51:51set qos policed-dscp-map 52:52set qos policed-dscp-map 53:53set qos policed-dscp-map 54:54set qos policed-dscp-map 55:55set qos policed-dscp-map 56:56set qos policed-dscp-map 57:57set qos policed-dscp-map 58:58set qos policed-dscp-map 59:59set qos policed-dscp-map 60:60set qos policed-dscp-map 61:61set qos policed-dscp-map 62:62set qos policed-dscp-map 63:63set qos policed-dscp-map excess-rate 0:0set qos policed-dscp-map excess-rate 1:1set qos policed-dscp-map excess-rate 2:2set qos policed-dscp-map excess-rate 3:3set qos policed-dscp-map excess-rate 4:4set qos policed-dscp-map excess-rate 5:5set qos policed-dscp-map excess-rate 6:6set qos policed-dscp-map excess-rate 7:7set qos policed-dscp-map excess-rate 8:8set qos policed-dscp-map excess-rate 9:9set qos policed-dscp-map excess-rate 10:10set qos policed-dscp-map excess-rate 11:11set qos policed-dscp-map excess-rate 12:12set qos policed-dscp-map excess-rate 13:13set qos policed-dscp-map excess-rate 14:14set qos policed-dscp-map excess-rate 15:15set qos policed-dscp-map excess-rate 16:16set qos policed-dscp-map excess-rate 17:17set qos policed-dscp-map excess-rate 18:18set qos policed-dscp-map excess-rate 19:19set qos policed-dscp-map excess-rate 20:20set qos policed-dscp-map excess-rate 21:21set qos policed-dscp-map excess-rate 22:22set qos policed-dscp-map excess-rate 23:23set qos policed-dscp-map excess-rate 24:24set qos policed-dscp-map excess-rate 25:25set qos policed-dscp-map excess-rate 26:26set qos policed-dscp-map excess-rate 27:27set qos policed-dscp-map excess-rate 28:28set qos policed-dscp-map excess-rate 29:29set qos policed-dscp-map excess-rate 30:30set qos policed-dscp-map excess-rate 31:31set qos policed-dscp-map excess-rate 32:32set qos policed-dscp-map excess-rate 33:33set qos policed-dscp-map excess-rate 34:34set qos policed-dscp-map excess-rate 35:35set qos policed-dscp-map excess-rate 36:36set qos policed-dscp-map excess-rate 37:37set qos policed-dscp-map excess-rate 38:38set qos policed-dscp-map excess-rate 39:39set qos policed-dscp-map excess-rate 40:40set qos policed-dscp-map excess-rate 41:41set qos policed-dscp-map excess-rate 42:42set qos policed-dscp-map excess-rate 43:43set qos policed-dscp-map excess-rate 44:44set qos policed-dscp-map excess-rate 45:45set qos policed-dscp-map excess-rate 46:46set qos policed-dscp-map excess-rate 47:47set qos policed-dscp-map excess-rate 48:48set qos policed-dscp-map excess-rate 49:49set qos policed-dscp-map excess-rate 50:50set qos policed-dscp-map excess-rate 51:51set qos policed-dscp-map excess-rate 52:52set qos policed-dscp-map excess-rate 53:53set qos policed-dscp-map excess-rate 54:54set qos policed-dscp-map excess-rate 55:55set qos policed-dscp-map excess-rate 56:56set qos policed-dscp-map excess-rate 57:57set qos policed-dscp-map excess-rate 58:58set qos policed-dscp-map excess-rate 59:59set qos policed-dscp-map excess-rate 60:60set qos policed-dscp-map excess-rate 61:61set qos policed-dscp-map excess-rate 62:62set qos policed-dscp-map excess-rate 63:63Port-Specific Automatic QoS—voip ciscoipphone
The port-specific automatic QoS command results in the following configuration:
set port qos mod/port autoqos voip ciscoipphone---------------set port qos mod/port policy-source localset port qos mod/port port-basedset port qos mod/port cos 0set port qos mod/port cos-ext 0set port qos mod/port trust-ext untrusted
