Catalyst 6500 Series Software Configuration Guide, 8.7
Configuring Automatic QoS
Download this chapter
Configuring Automatic QoSConfiguring Automatic QoS
give_us_feedback

Table Of Contents

Using Automatic QoS

Understanding How Automatic QoS Works

QoS Overview

Typical CoS and DSCP Values for Voice and Video Networks

QoS Scenario—Cisco IP Phone

QoS Scenario—Cisco SoftPhone

Using the Automatic QoS Macro on the Switch

Automatic QoS Overview

Automatic QoS Configuration Guidelines and Restrictions

Configuration Files

Supported Phones

CDP Dependencies

COPS Considerations

RSVP Considerations

Current QoS Default Settings

EtherChannel Considerations

Video Traffic Considerations

Clearing the QoS Configuration

PFC/PFC2 Support

1p1q0t/1p3q1t Port Support

Global Automatic QoS Macro

Overview

Global Automatic QoS Detail Settings

Port-Specific Automatic QoS Macro

Port-Specific Automatic QoS Settings—ciscoipphone

Port-Specific Automatic QoS Settings—ciscosoftphone

Port-Specific Automatic QoS Settings—trust cos

Port-Specific Automatic QoS Settings—trust dscp

CLI Interface for Automatic QoS

Global Automatic QoS Macro—set qos autoqos

Port-Specific Automatic QoS Macro—set port qos autoqos

Displaying the QoS Settings

Clearing the Automatic QoS Settings

Tracking the QoS Configuration

Detailed Automatic QoS Configuration Statements

Global Automatic QoS Macro

Port-Specific Automatic QoS—voip ciscoipphone

Port-Specific Automatic QoS—voip ciscosoftphone

Port-Specific Automatic QoS—trust cos

Port-Specific Automatic QoS—trust dscp

Warning and Error Conditions

Out of ACL Names

Out of TCAM Space

COPS Warning Message

CDP Warning

Out of Policer Names

QoS Disabled

syslog Additions

CDP Warning —Warning Level

Interface Change for All Ports Required—Warning Level

Other Relevant syslog Messages

Device No Longer Detected on the Port—Notice Level (Trusted Boundary)

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 that are used in this chapter, refer to the Catalyst 6500 Series Switch Command Reference publication.

Note Automatic QoS is not supported on Supervisor Engine 720 in software release 8.1(1).

Note For information on using automatic voice configuration, see the "Using SmartPorts" section on page 55-38.

This chapter consists of these sections:

•Understanding How Automatic QoS Works

•QoS Overview

•Using the Automatic QoS Macro on the Switch

•Using Automatic QoS in Your Network

Understanding How Automatic QoS Works

Automatic QoS consists of a macro that simplifies the 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

•QoS Scenario—Cisco IP Phone

•QoS Scenario—Cisco SoftPhone

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.

Catalyst 6500 series switches use the differentiated services (DIFFSERV) model for QoS. This model outlines three traffic types:

•EF (Expedited Forwarding)

•AF (Assured Forwarding)

•BE (Best Effort)

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 52-1 for the recommended CoS and DSCP values for the 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 52-1 Typical CoS and DSCP values in Cisco Voice and Video Networks

CoS Value1
DSCP
Significance

0

0

Default traffic (BE class)

3

26 (IETF recommended)

Voice/video call control/signaling (TCP)
AF31 class

5

46 (IETF recommended)

Voice-bearer stream (RTP/UDP)
EF class

4

34 (IETF recommended)

Video-bearer stream
AF41 class

2

18

Mission critical/transactional traffic
AF21 class

1

10

Streaming video (not interactive)
AF11

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:

•CoS 5 (voice data)—Highest priority (priority queue if present, otherwise high queue)

•CoS 6, 7 (routing protocols)—Second priority (high queue)

•CoS 3, 4 (call signal and video stream)—Third priority (high queue)

•CoS 1, 2 (streaming and mission critical)—Fourth priority (high queue)

•CoS 0— Low priority (low queue)

For the ports that do not implement a priority queue, the 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, you can connect the Cisco IP Phone 79xx 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 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 the trust and classification capabilities that you need to configure. For more information, see the "Port-Specific Automatic QoS Settings—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.

Using the Automatic QoS Macro on the Switch

These sections describe the automatic QoS macro:

•Automatic QoS Overview

•Automatic QoS Configuration Guidelines and Restrictions

•Global Automatic QoS Macro

•Port-Specific Automatic QoS Macro

•CLI Interface for Automatic QoS

•Detailed Automatic QoS Configuration Statements

•Warning and Error Conditions

•syslog Additions

•Other Relevant syslog Messages

•Summary of Automatic QoS Features

Automatic QoS Overview

The automatic QoS macro is divided into these two separate components:

•Global automatic QoS command (set qos auto)—Deals with all switch-wide related QoS settings that are not specific to any given interface. These settings include CoS-to-queue maps, CoS-to-DSCP maps, and WRED settings for specific port types and global mappings.

•Port-specific automatic QoS command (set port qos mod/port autoqos)—Configures all inbound QoS parameters for a particular port to reflect the desired traffic type (voice, video, and applications).

Tip To ensure that automatic QoS works properly, you should execute both components.

Automatic QoS Configuration Guidelines and Restrictions

These sections provide the configuration guidelines and restrictions for automatic QoS:

•Configuration Files

•Supported Phones

•CDP Dependencies

•COPS Considerations

•RSVP Considerations

•Current QoS Default Settings

•EtherChannel Considerations

•Video Traffic Considerations

•Clearing the QoS Configuration

•PFC/PFC2 Support

•1p1q0t/1p3q1t Port Support

Configuration Files

Creating the 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 automatic QoS 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 trusted boundary on the Cisco IP Phone, you must enable Cisco Discovery Protocol (CDP) version 2 or later on the port. If you enable trusted boundary, 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 the local policy or the 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 that has a configured policy that is currently set to COPS, the policy reverts to the local policy. The global QoS policy reverts to the local policy (through the global automatic QoS command), and the port-based policy reverts to the local policy (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

•Global Automatic QoS Detail Settings

Overview

You must configure both egress and ingress QoS for QoS to function properly. Because any traffic type can egress on any given port, the egress QoS settings must have global QoS settings. The settings take into account all the possible traffic types that are listed in the "Typical CoS and DSCP Values for Voice and Video Networks" section. The egress QoS settings are applied to all the ports in the switch. The global QoS settings cover the ingress scheduling settings, because the granularity CoS-to-queue mapping is port-type specific and not port specific. The port-specific QoS settings, such as QoS ACLs, port trust, and default CoS, are not altered.

Global Automatic QoS Detail Settings

Table 52-2 through Table 52-6 list the values of all the QoS parameters that are configured through the global automatic QoS command.

Note The 1p1q8t default WRED settings are not changed from the current QoS defaults; only the CoS-to-threshold map is changed.

Table 52-2 Switch-Wide Settings (Global QoS Settings)

QoS Parameter
Setting

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)


Table 52-3 Scheduling Specific Settings (Global QoS Settings)

Field
Value

1p1q0t rxq-ratio

80% : 20% (q1 : p1)

1p3q1t wrr

20 100 200 (q1 q2 q3)

2q2t txq-ratio

80% : 20% (q1 : q2)

2q2t wrr

100 255 (q1 q2)


Table 52-4 CoS-to-Queue Maps and Tail/WRED Settings (Global QoS Settings)

 
2q2t
Tail (2q2t)
1q2t
Tail (1q2t)
1q4t
Tail (1q4t)
1p3q1t
WRED (1p3q1t)
1p1q0t

Q1t1

0

(100%)

0, 1, 2, 3, 4

(80%)

0

(50%)

0

(70% : 100%)

0, 1, 2, 3, 4

Q1t2

 

(100%)

5, 6, 7

(100%)

 

(60%)

     

Q1t3

       

1, 2, 3, 4

(80%)

     

Q1t4

       

5, 6, 7

(100%)

     

Q2t1

1, 2, 3, 4

(80%)

       

1, 2

(70% : 100%)

5, 6, 7

Q2t2

5, 6, 7

(100%)

             

Q3t1

           

3, 4

(70% : 90%)

 

Q3

           

6, 7

WRED disabled

 

Q4t1

           

5

   

Table 52-5 Scheduling Specific Settings (Global QoS Settings)

Field
Value

1p2q2t txq-ratio

70% : 15% : 15% (q1 q2 1p)

1p2q2t wrr

50 255 (q1 q2)

1p1q8t rxq-ratio

80 20 (q1 1p)

1p2q1t txq-ratio

70% : 15% : 15% (q1 q2 1p)

1p2q1t wrr

50 255 (q1 q2)


Table 52-6 CoS-to-Queue Maps and Tail/WRED Settings (Global QoS Settings) 

 
1p2q2t
WRED
1p1q4t
Tail
1p2q1t
WRED
1p1q8t
WRED

Q1t1

0

(70% : 100%)

0

(50%)

0

(70% : 100%)

0

(40% : 70%)

Q1t2

(70% : 100%)

 

(60%)

   

1, 2

(60% : 90%) (threshold 5)

Q1t3

   

1,2,3,4

(80%)

   

3, 4

(70% : 100%)

(threshold 8)

Q1t4

   

6,7

(100%)

       

Q2t1

1, 2, 3, 4

(70% : 90%)

5

 

1, 2, 3, 4

(70% : 90%)

5, 6, 7

 

Q2t2

6, 7

(100% : 100%)

           

Q2

       

6, 7

WRED disabled

   

Q3t1

5

     

5

     

Port-Specific Automatic QoS Macro

The port-specific automatic QoS macro handles all inbound QoS configuration that is specific to a particular traffic type. The 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 do not include scheduling. The 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.

The 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—ciscoipphone

•Port-Specific Automatic QoS Settings—ciscosoftphone

•Port-Specific Automatic QoS Settings—trust cos

•Port-Specific Automatic QoS Settings—trust dscp

Port-Specific Automatic QoS Settings—ciscoipphone

Use the ciscoipphone keyword to set the port to trust-cos and to enable trusted boundary. Combined with the global automatic QoS command, all settings are configured on the switch to properly handle the signaling, voice bearer, and PC data entering and leaving the port.

In addition to the switch-side QoS settings that are covered by the global automatic QoS command, the phone has a few QoS features that you need to configure for proper labeling to occur. The 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 the packets in case the port is untrusted (ext-cos).

AVVID recommends an untrusted and cos-ext value of 0. The 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 52-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 You must enable CDP version 2 for trusted boundary to work. If CDP version 2 is not enabled, a syslog message displays. See the "CDP Warning" section.

Table 52-7 Port-Specific Settings for Voice (ciscoipphone Keyword)

Item
Value

Interface type

Port-based

Policy source—config

Local

Policy source—runtime

Local (as per default)

Trust type—config

Trust-cos

Trust type—runtime

Trust-cos

Default CoS—config

0 (as per default)

Default CoS—runtime

0 (as per default)

Trust-device

Ciscoipphone

QoS ACL attached to port

trust-cos any (if 1q4t/2q2t port, otherwise none)

QoS ACL name

ACL_IP-PHONES (if 1q4t/2q2t port, otherwise
none)1 , 2 , 3

Trust-ext

Untrusted

Cos-ext

0

1 Only the 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.

3 ACL_IP-PHONES acl will not be created on WS-X6148-RJ-45 and WS-X6148-RJ-21 modules.


Port-Specific Automatic QoS Settings—ciscosoftphone

On the ports that connect to a Cisco SoftPhone, the 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 the PC users could send the nonpriority traffic with DSCP 46 and gain unauthorized performance benefits. Policing on all inbound traffic prevents the 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 that is 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 24) is also policed and marked down to zero if excess signaling traffic is detected. All the other inbound traffic types are reclassified to default traffic (DSCP 0 - BE).

Caution You must disable trusted boundary for the Cisco SoftPhone ports.

Table 52-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 52-8 Port-Specific Settings for Voice (ciscosoftphone Keyword) 

Item
Value

Interface type

Port-based

Policy source—config

Local

Policy source—runtime

Local

Trust type—config

untrusted

Item
Value

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-DSCP24-x-y any dscp-field 24 *

QoS ACL name

ACL_IP-SOFTPHONES-x-y3 , 4

QoS policers

aggregate POLICE_SOFTPHONE-DSCP46-3-1 rate 320 burst 20 policed-dscp

aggregate POLICE_SOFTPHONE-DSCP24-3-1 rate 32 burst 8 policed-dscp

QoS policer names

POLICE_SOFTPHONE-DSCP46-x-y

POLICE_SOFTPHONE-DSCP24-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 the IP QoS ACLs are applied (not IPX).

4 If the 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 that all inbound traffic on a Cisco SoftPhone port has the following characteristics:

1. The rate of DCSP 46 is at or less than that of the expected SoftPhone application rate (G.722 - worst case).

2. The rate of DSCP 24 is at or less than the expected signaling rate.

3. All other traffic is remarked to DSCP 0 (default traffic).

Action 3 is accomplished by the default QoS ACL. Any traffic that exceeds actions (1) or (2) is 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 24 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 a 256-kbps maximum packet length of 256 bytes and minor signaling with a maximum packet length of 1000 bytes. Signaling is transmitted with DSCP 24 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 that DSCP 46 is marked down to DSCP 0 and that DSCP 24 is marked down to DSCP 0. The global automatic QoS macro configures the default QoS IP ACL that is used to remark all the 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 the bootup time and NVRAM space could be affected. The 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 running out of NVRAM space, you might need to use the text configuration mode. For more information, see the "Out of TCAM Space" section.

Port-Specific Automatic QoS Settings—trust cos

Use the trust cos automatic QoS keyword for the ports that require a "trust all" solution. Use the keyword only on the ports that connect other switches or known servers because the port trusts all inbound traffic marking in Layer 2 (CoS). Trusted boundary is disabled, and no QoS policing is configured on these types of ports.

Table 52-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 configuration examples.

Table 52-9 Port-Specific Settings for Trust (trust cos Keyword) 

Item
Value

Interface type

Port-based

Policy source—config

Local

Policy source—runtime

Local (as per default)

Trust type—config

Trust-cos

Trust type—runtime

Trust-cos

Default CoS—config

0 (as per default)

Default CoS—runtime

0 (as per default)

Trust-device

None

QoS ACL attached to port

trust-cos any (if 1q4t/2q2t port, otherwise none)

QoS ACL name

ACL_IP-TRUSTCOS (if 1q4t/2q2t port, otherwise none)1 , 2

Trust-ext

Untrusted

Cos-ext

0

1 Only the 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—trust dscp

Use the trust dscp automatic QoS keyword for the ports that require a "trust all" type of solution. Use this keyword only on the ports that connect to the other switches or known servers because the port will be trusting all inbound traffic marking Layer 3 (DSCP). Trusted boundary is disabled, and no QoS policing is configured on these types of ports.

Table 52-10 outlines the details of the configuration after executing the automatic QoS trust macro on a port. See the "Port-Specific Automatic QoS Settings—trust dscp" section for configuration examples.

Table 52-10   Port Specific Settings for Trusts (trust dscp Keyword)

Item
Value

Interface type

Port-based

Policy source—config

Local

Policy source—runtime

Local (as per default)

Trust type—config

Trust-dscp (all except 1q4t/2q2t ports)

Untrusted (1q4t/2q2t ports)

Trust type—runtime

Trust-dscp (all except 1q4t/2q2t ports)

Untrusted (1q4t/2q2t ports)

Default CoS—config

0 (as per default)

Default CoS—runtime

0 (as per default)

Trust-device

None

QoS ACL attached to port

trust-dscp any (if 1q4t/2q2t port, otherwise none)

QoS ACL name

ACL_IP-TRUSTDSCP (if 1q4t/2q2t port, otherwise none)1 , 2

Trust-ext

Untrusted

Cos-ext

0

1 Only the 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

•Port-Specific Automatic QoS Macro—set port qos autoqos

•Displaying the QoS Settings

•Clearing the Automatic QoS Settings

•Tracking the QoS Configuration

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 autoqos 

Console> (enable) set qos autoqos

QoS 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 help

Usage: 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 ciscoipphone

Port 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 ciscosoftphone

Port 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 cos

Port 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 dscp

Port 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 the QoS Settings

Enter the existing QoS show commands to display the QoS settings. These commands include the show port qos and show qos info runtime commands.

Clearing the Automatic QoS Settings

You can clear the automatic QoS configuration by entering a port-based clear command and a global clear command. To clear the automatic QoS configuration, clear each interface on which automatic QoS has run with the port-based clear command and then enter the global clear command as described in the following sections:

•Clearing the Automatic QoS Port-Based Settings

•Clearing the Automatic QoS Global Settings

Clearing the Automatic QoS Port-Based Settings

All automatic QoS settings that are configured through the port-based automatic QoS command can be configured back to the factory-default settings by entering the clear port qos mod/port autoqos command, as follows: 

Console> (enable) set port qos 3/1 autoqos voip ciscosoftphone 

Port 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) clear port qos ?

  <mod/port>                 Module number and Port number(s)

Console> (enable) clear port qos 3/1 ?       

  autoqos                    Clear port based autoqos settings

  cos                        Clear QoS default CoS value on ports

  cos-ext                    Clear QoS default CoS extension on ports

Console> (enable) clear port qos 3/1 autoqos 

Port based QoS settings will be restored back to factory defaults for port 3/1.

Do you want to continue (y/n) [n]? y

Port 3/1 autoqos settings have been cleared.  

It is recommended to execute the "clear qos autoqos" global command if

not executed previously to clear global autoqos settings.

Console> (enable)

The port-based clear command is supported on all ports that support the port-based automatic QoS set commands. All QoS settings that are configured through the automatic QoS port-based command revert back to the factory-default settings (with the exception of automatic QoS ACLs). All QoS ACLs that are mapped to the port are unmapped from the port, even if the QoS ACL is not related to automatic QoS. The QoS ACLs that are created for automatic QoS purposes are cleared when you enter the global clear command.

Clearing the Automatic QoS Global Settings

All QoS settings that are configured through the global automatic QoS command can be configured back to the factory-default settings by entering the clear qos autoqos command, as follows: 

Console> (enable) clear qos autoqos

Its highly recommended to execute clear port autoqos commands prior

to the global clear command:

    clear port qos <mod/port> autoqos


Do you want to continue (y/n) [n]? y

........................

Autoqos ACL 'ACL_IP-SOFTPHONE-3-1' successfully deleted.

Cleared Autoqos policer 'POLICE_SOFTPHONE-DSCP46-3-1'

Cleared Autoqos policer 'POLICE_SOFTPHONE-DSCP24-3-1'


All ingress and egress QoS scheduling parameters set to factory default.

CoS to DSCP, DSCP to COS, IP Precedence to DSCP and policed dscp maps

configured.  Global Autoqos QoS cleared.

Console> (enable)

The QoS ACLs that are created through the set port autoqos commands are cleared when you enter the global automatic QoS clear command. In addition, any policers that are used by the automatic QoS ACLs are cleared.

The global automatic QoS clear command searches for the automatic QoS ACL names. The search algorithm looks for names that begin with these strings:

•ACL_IP-PHONES (for ciscoipphone)

•ACL_IP-SOFTPHONE (for ciscosoftphone)

•ACL_IP-TRUSTCOS (for trust cos)

•ACL_IP-TRUSTDSCP (for trust dscp)

Any QoS ACL that starts with the above strings is considered an automatic QoS ACL and is cleared. If one is found and the QoS ACL is committed and not mapped to a port or a VLAN, the automatic QoS ACL is deleted.

Similarly, the search algorithm looks for the aggregate QoS policers starting with the name: POLICE_SOFTPHONE-DSCP (for ciscosoftphone).

The global clear command searches for the aggregate policer names that begin with POLICE_SOFTPHONE-DSCP. If a policer is found, and there is no QoS ACL that is associated with it, it is deleted. If a policer is found, and there is a QoS ACL that is associated with it, a warning is displayed indicating that the policer is still in use.

Various error conditions can occur when you use the global clear command. If you have properly executed the port-based clear commands before entering the global clear command, no error conditions should occur. However, if you execute the global clear command first or modify the automatic QoS configuration, these error conditions could occur:

•The automatic QoS ACLs are still mapped to a port or VLAN.

The global clear command does not clear the automatic QoS ACLs that are still mapped to a VLAN or port. Instead, the command displays a warning indicating the name of the QoS ACL that is still mapped to a port/VLAN.

•The aggregate policers are still in use.

If the automatic QoS policers are still in use (referenced by a QoS ACL), the global clear command does not remove them. Instead, it displays the name of the aggregate policer.

•The automatic QoS ACLs are uncommitted.

The global clear command removes only the committed automatic QoS ACLs but ignores the uncommitted automatic QoS ACLs.

This example shows what is displayed under these various error conditions: 

Console> (enable) clear qos autoqos

Its highly recommended to execute clear port autoqos commands prior

to the global clear command:

    clear port qos <mod/port> autoqos


Do you want to continue (y/n) [n]? y

........................

Autoqos ACL 'ACL_IP-SOFTPHONE-3-2' successfully deleted.

Autoqos ACL 'ACL_IP-SOFTPHONE-3-3' successfully deleted.

Autoqos ACL 'ACL_IP-SOFTPHONE-3-4' still mapped to port or vlan.

Autoqos ACL 'ACL_IP-SOFTPHONE-3-5' still mapped to port or vlan.

Autoqos ACL 'ACL_IP-SOFTPHONE-3-6' still mapped to port or vlan.

Cleared Autoqos policer 'POLICE_SOFTPHONE-DSCP46-3-2'

Cleared Autoqos policer 'POLICE_SOFTPHONE-DSCP24-3-2'

Cleared Autoqos policer 'POLICE_SOFTPHONE-DSCP46-3-3'

Cleared Autoqos policer 'POLICE_SOFTPHONE-DSCP24-3-3'

Could not clear Autoqos policer ''POLICE_SOFTPHONE-DSCP46-3-4', still in use.

QoS is disabled.


All ingress and egress QoS scheduling parameters set to factory default.

CoS to DSCP, DSCP to COS, IP Precedence to DSCP and policed dscp maps

configured.  Global Autoqos QoS cleared.

Console> (enable)

Tracking the QoS Configuration

A configuration "comment" appears in the configuration file to help you determine where the QoS configuration originated: Traditional QoS or automatic QoS. The comment is created after you enter the global set qos autoqos command and remains in the configuration file until you enter either the clear global autoqos command or the clear qos config command. An example is as follows: 

Console> (enable) set qos autoqos 

..............

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 q