-
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
Ethernet Ingress Port Features
Layer 3 Switching Engine Features
Layer 2 Switching Engine Features
Single-Port ATM OC-12 Switching Module Features
Multilayer Switch Feature Card (MSFC or MSFC2)
Ethernet Ingress Port Marking, Scheduling, Congestion Avoidance, and Classification
Ethernet Ingress Port Scheduling and Congestion Avoidance
Ethernet Ingress Port Classification Features with a Layer 3 Switching Engine
Classification, Marking, and Policing with a Layer 3 Switching Engine
Final Layer 3 Switching Engine CoS and ToS Values
Classification and Marking with a Layer 2 Switching Engine
Ethernet Egress Port Scheduling, Congestion Avoidance, and Marking
Scheduling and Congestion Avoidance
Enabling Port-Based or VLAN-Based QoS
Configuring the Trust State of a Port
Configuring the CoS Value for a Port
ACE Name, Marking Rule, Policing, and Filtering Syntax
Creating or Modifying Named IPX ACLs
Creating or Modifying Named MAC ACLs
Creating or Modifying the Default IPX and MAC ACLs
Reverting to Default Values in Default ACLs
Detaching ACLs from Interfaces
Mapping a CoS Value to a Host Destination MAC Address/VLAN Pair
Deleting a CoS Value to a Host Destination MAC Address/VLAN Pair
Enabling or Disabling Microflow Policing of Bridged Traffic
Configuring Standard Receive-Queue Tail-Drop Thresholds
Configuring 2q2t Port Standard Transmit-Queue Tail-Drop Thresholds
Configuring Standard Queue WRED-Drop Thresholds
Allocating Bandwidth Between Standard Transmit Queues
Configuring the Receive-Queue Size Ratio
Configuring the Transmit-Queue Size Ratio
Mapping CoS Values to Drop Thresholds
Associating 1q2t/1p2q2t and 1p1q4t/1p2q2t Ports
Associating 1p1q0t/1p3q1t Ports
Associating 1p1q8t/1p2q1t Ports
Mapping Received CoS Values to Internal DSCP Values
Mapping Received IP Precedence Values to Internal DSCP Values
Mapping Internal DSCP Values to Egress CoS Values
Selecting COPS as the QoS Policy Source
Selecting Locally Configured QoS Policy
Enabling Use of Locally Configured QoS Policy
Removing Roles from Port ASICs
Configuring Policy Decision Point Servers
Deleting the PDP Server Configuration
Configuring the COPS Domain Name
Configuring the COPS Communications Parameters
Enabling Participation in the DSBM Election
Disabling Participation in the DSBM Election
Configuring Policy Decision Point Servers
Deleting the PDP Server Configuration
Configuring RSVP Policy Timeout
Configuring RSVP Use of Local Policy
Configuring QoS Statistics Data Export
Enabling QoS Statistics Data Export Globally
Enabling Per-Port QoS Statistics Data Export
Enabling Per-Aggregate Policer QoS Statistics Data Export
Clearing the Aggregate Policer QoS Statistics
Setting the QoS Statistics Data Export Time Interval
Configuring the QoS Statistics Data Export Destination Host and UDP Port
Displaying QoS Statistics Information
Configuring QoS
This chapter describes how to configure quality of service (QoS) on the Catalyst 6500 series switches and includes the configuration information that is required to support Common Open Policy Service (COPS) and Resource ReSerVation Protocol (RSVP).
Note
•
•
You can configure QoS using one of the following:
•
•
•
•
This chapter consists of these sections:
•
Understanding How QoS Works
Note
•
Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an equal chance of being dropped.
The QoS feature on the Catalyst 6500 series switches selects network traffic, prioritizes it according to its relative importance, and provides priority-indexed treatment through congestion avoidance techniques. Implementing QoS in your network makes network performance more predictable and bandwidth utilization more effective.
QoS sets Layer 2 and Layer 3 values in network traffic to a configured value or to a value based on received Layer 2 or Layer 3 values. IP traffic retains the Layer 3 value when it leaves the switch.
These sections describe QoS:
•
•
•
•
QoS Terminology
This section defines some QoS terminology:
•
•
•
–
Layer 2 Inter-Switch Link (ISL) frame headers have a 1-byte User field that carries an IEEE 802.1p CoS value in the three least significant bits.
Layer 2 802.1Q frame headers have a 2-byte Tag Control Information field that carries the CoS value in the three most significant bits, which are called the User Priority bits.
Other frame types cannot carry CoS values.
Note
–
–
Note
•
•
•
•
•
•
–
–
•
•
•
•
Flowcharts
Figure 43-1 shows how traffic flows through the QoS features; Figure 43-2 through Figure 43-7 show more details of the traffic flow through QoS features.
Figure 43-1 Traffic Flow Through QoS Features
Note
•
•
Figure 43-2 Ethernet ingress Port Classification, Marking, Scheduling, and Congestion Avoidance
Figure 43-3 Layer 3 Switching Engine Classification, Marking, and Policing
Figure 43-4 Layer 2 Switching Engine Classification and Marking
Figure 43-5 Multilayer Switch Feature Card Marking (MSFC and MSFC2)
Figure 43-6 Ethernet Egress Port Scheduling, Congestion Avoidance, and Marking
Figure 43-7 Single-Port ATM OC-12 Switching Module Marking
QoS Feature Set Summary
The QoS feature set on your switch is determined by the switching engine on the supervisor engine. Enter the show module command for the supervisor engine to display your switching engine configuration. The display shows the "Sub-Type" to be one of the following:
•
•
–
–
–
The Layer 3 Switching Engine WS-F6K-PFC and Layer 3 Switching Engine II support similar feature sets. The two Layer 2 switching engines support the same QoS feature set.
These sections describe the QoS feature sets:
•
•
•
•
•
•
Ethernet Ingress Port Features
With any switching engine, QoS supports classification, marking, scheduling, and congestion avoidance using Layer 2 CoS values at Ethernet ingress ports. Classification, marking, scheduling, and congestion avoidance at Ethernet ingress ports do not use or set Layer 3 IP precedence or DSCP values. With a Layer 3 switching engine, you can configure Ethernet ingress port trust states that can be used by the switching engine to set Layer 3 IP precedence or DSCP values and the Layer 2 CoS value. For more information, see the "Ethernet Ingress Port Marking, Scheduling, Congestion Avoidance, and Classification" section.
Layer 3 Switching Engine Features
With a Layer 3 switching engine, QoS supports classification, marking, and policing using IP, IPX, and Media Access Control (MAC) access control lists (ACLs). ACLs contain access control entries (ACEs) that specify Layer 2, 3, and 4 classification criteria, a marking rule, and policers. Marking sets the Layer 3 IP precedence or DSCP values and the Layer 2 CoS value to either received or configured Layer 2 or Layer 3 values. Policing uses bandwidth limits to either drop or mark nonconforming traffic. For more information, see the "Classification, Marking, and Policing with a Layer 3 Switching Engine" section.
During processing, a Layer 3 switching engine associates a DSCP value with all traffic, including non-IP traffic (for more information, see the "Internal DSCP Values" section).
Layer 2 Switching Engine Features
With a Layer 2 Switching Engine, QoS can classify traffic using Layer 2 destination MAC addresses, VLANs, and marking using Layer 2 CoS values. Classification and marking with a Layer 2 Switching Engine do not use or set Layer 3 IP precedence or DSCP values. For more information, see the "Classification and Marking with a Layer 2 Switching Engine" section.
Ethernet Egress Port Features
With any switching engine, QoS supports Ethernet egress port scheduling and congestion avoidance using Layer 2 CoS values. Ethernet egress port marking sets Layer 2 CoS values and, with a Layer 3 switching engine, Layer 3 DSCP values. For more information, see the "Ethernet Egress Port Scheduling, Congestion Avoidance, and Marking" section.
Single-Port ATM OC-12 Switching Module Features
The ingress interface from a single-port ATM OC-12 switching module is untrusted, and QoS sets CoS to zero in all traffic received from it. With a Layer 3 switching engine, QoS can mark IP traffic that is transmitted to a single-port ATM OC-12 switching module with Layer 3 DSCP values.
Multilayer Switch Feature Card (MSFC or MSFC2)
QoS marks IP traffic that is transmitted to an MSFC with Layer 3 DSCP values. CoS is zero in all traffic that is sent from an MSFC to egress ports.
Note
Ethernet Ingress Port Marking, Scheduling, Congestion Avoidance, and Classification
These sections describe Ethernet ingress port marking, scheduling, congestion avoidance, and classification:
•
•
Overview
The trust state of an Ethernet port determines how it marks, schedules, and classifies received traffic, and whether or not congestion avoidance is implemented. You can configure the trust state of each port with one of these keywords:
•
•
•
•
Note
•
For more information, see the "Configuring the Trust State of a Port" section.
In addition to the port configuration keywords listed above, with a Layer 3 switching engine, QoS uses trust-ipprec, trust-dscp, and trust-cos ACE keywords. Do not confuse the ACE keywords with the port keywords.
Ports that are configured with the untrusted keyword are called untrusted ports. Ports that are configured with the trust-ipprec, trust-dscp, or trust-cos keywords are called trusted ports. QoS implements ingress port congestion avoidance only on ports that are configured with the trust-cos keyword.
Ingress port marking, scheduling, and congestion avoidance use Layer 2 CoS values. Ingress port marking, scheduling, and congestion avoidance do not use or set Layer 3 IP precedence or DSCP values.
Marking at Untrusted Ports
QoS marks all frames that are received through untrusted ports with the port CoS value (the default is zero). QoS does not implement ingress port congestion avoidance on untrusted ports: the traffic goes directly to the switching engine.
Marking at Trusted Ports
When an ISL frame enters the switch through a trusted port, QoS accepts the three least significant bits in the User field as a CoS value. When an 802.1Q frame enters the switch through a trusted port, QoS accepts the User Priority bits as a CoS value. QoS marks all traffic that is received in other frame types with the port CoS value.
The port CoS value is configurable for each Ethernet port (for more information, see the "Configuring the CoS Value for a Port" section).
Ethernet Ingress Port Scheduling and Congestion Avoidance
QoS does not implement ingress port congestion avoidance on ports that are configured with the untrusted, trust-ipprec, or trust-dscp keywords: the traffic goes directly to the switching engine.
QoS uses CoS-value-based receive-queue drop thresholds to avoid congestion in traffic entering the switch through a port that is configured with the trust-cos keyword (for more information, see the "Configuring the Trust State of a Port" section).
Receive Queues
Enter the show port capabilities command to see the queue structure of a port. The command displays one of the following:
•
•
•
•
•
Strict-priority queues are serviced in preference to other queues. QoS services traffic in a strict-priority queue before servicing the standard queue. When QoS services the standard queue, after receiving a packet, it checks for traffic in the strict-priority queue. If QoS detects traffic in the strict-priority queue, it suspends its service of the standard queue and completes service of all traffic in the strict-priority queue before returning to the standard queue.
Ingress Scheduling
QoS schedules traffic through the receive queues based on CoS values. In the 1p1q4t, 1p1q0t, and 1p1q8t default configurations, QoS assigns all traffic with CoS 5 to the strict-priority queue; QoS assigns all other traffic to the standard queue. In the 1q4t default configuration, QoS assigns all traffic to the standard queue.
Ingress Congestion Avoidance
Note
If a port is configured with the trust-cos keyword, QoS implements CoS-value-based receive-queue drop thresholds to avoid congestion in received traffic.
1q2t ports have this default drop threshold configuration:
•
•
1q4t ports have this default drop threshold configuration:
•
•
•
•
1p1q4t ports have this default drop-threshold configuration:
•
•
–
–
–
–
1p1q0t ports have this default drop-threshold configuration:
•
•
1p1q8t ports have this default drop-threshold configuration:
•
•
–
–
–
–
–
–
–
Note
Figure 43-8 shows the drop thresholds for a 1q4t port. Drop thresholds in other configurations function similarly.
Figure 43-8 Receive-Queue Drop Thresholds
Ethernet Ingress Port Classification Features with a Layer 3 Switching Engine
You can use the untrusted, trust-ipprec, trust-dscp, and trust-cos port keywords to classify traffic on a per-port basis for a Layer 3 switching engine to mark.
The trust-ipprec and trust-dscp keywords are supported only with a Layer 3 switching engine and are not supported on 1q4t ports except Gigabit Ethernet. On 1q4t ports (except Gigabit Ethernet), the trust-cos port keyword displays an error message, activates receive-queue drop thresholds, and—as indicated by the error message—does not apply the trust-cos trust state to traffic. You must configure the trust-cos ACL that matches the ingress traffic to apply the trust-cos trust state.
In addition to per-port classification, you can create ACEs that classify traffic on a per-packet basis (for IP and IPX traffic, see the "Named IP ACLs" section and the "Creating or Modifying Named IPX ACLs" section) or on a per-frame basis (for other traffic, see the "Creating or Modifying Named MAC ACLs" section), regardless of the port configuration (see the "Marking Rules" section).
To mark traffic in response to per-port classification, the traffic must match an ACE that contains the dscp ACE keyword (see the "Marking Rules" section). In their default configuration, the ACEs in the default ACLs contain the dscp ACE keyword. Table 43-1 lists the per-port classifications and the marking rules that they invoke.
QoS uses configurable mapping tables to set internal and egress DSCP, which is a 6-bit value, from CoS and IP precedence, which are 3-bit values (for more information, see the "Internal DSCP Values" section and the "Configuring DSCP Value Maps" section).
Classification, Marking, and Policing with a Layer 3 Switching Engine
Note
These sections describe classification, marking, and policing with a Layer 3 switching engine:
•
•
Note
Internal DSCP Values
These sections describe the internal DSCP values:
Internal DSCP Sources
During processing, the priority of all traffic (including non-IP traffic) is represented with an internal DSCP value. QoS derives the internal DSCP value from the following:
•
•
•
•
The trust state of traffic is the trust state of the ingress port unless set otherwise by the matching ACE.
Note
QoS uses configurable mapping tables to derive the internal 6-bit DSCP value from CoS or IP precedence, which are 3-bit values (see the"Mapping Received CoS Values to Internal DSCP Values" section or the "Mapping Received IP Precedence Values to Internal DSCP Values" section).
Egress DSCP and CoS Sources
For egress IP traffic, QoS creates a ToS byte from the internal DSCP value (which you can set equal to an IP precedence value) and sends it to the egress port to be written into IP packets. For trust-dscp and untrusted IP traffic, the ToS byte includes the original 2 least-significant bits from the received ToS byte.
For all egress traffic, QoS uses a configurable mapping table to derive a CoS value from the internal DSCP value that is associated with traffic (see the "Mapping Internal DSCP Values to Egress CoS Values" section). QoS sends the CoS value to Ethernet egress ports for use in scheduling and to be written into ISL and 802.1Q frames.
ACLs
QoS uses ACLs that contain ACEs. The ACEs specify classification criteria, a marking rule, and policers. QoS compares received traffic to the ACEs in ACLs until a match occurs. When the traffic matches the classification criteria in an ACE, QoS marks and polices the packet as specified in the ACE and makes no further comparisons.
There are three ACL types: IP, and with a Layer 3 switching engine, IPX and MAC. QoS compares traffic of each type (IP, IPX, and MAC) only to the corresponding ACL type (see Table 43-2).
Table 43-2 Supported Ethertype Field Values
IP
0x0800
IP
IPX
0x8137 and 0x8138
IPX
MAC1
0x0600 and 0x0601
XNS
0x0BAD and 0x0BAF
Banyan VINES
0x6000-0x6009 and 0x8038-0x8042
DECnet
0x809b and 0x80f3
AppleTalk
1 QoS MAC ACLs that do not include an ethertype parameter match traffic with any value in the ethertype field, which allows MAC-level QoS to be applied to any traffic except IP and IPX.
QoS supports user-created named ACLs, each containing an ordered list of ACEs, and user-configurable default ACLs, each containing a single ACE.
Named ACLs
You create a named ACL when you enter an ACE with a new ACL name. You add an ACE to an existing ACL when you enter an ACE with the name of the existing ACL.
You can specify the classification criteria for each ACE in a named ACL. The classification criteria can be specific values or wildcards (for more information, see the "Creating or Modifying ACLs" section).
These sections describe the classification criteria that can be specified in a named ACL:
•
•
•
•
•
•
•
•
IP ACE Layer 3 Classification Criteria
You can create IP ACEs that match traffic with specific Layer 3 values by including these Layer 3 parameters (see the "Named IP ACLs" section):
•
•
•
–
–
–
–
–
–
–
–
Note
IP ACE Layer 4 Protocol Classification Criteria
You can create IP ACEs that match specific Layer 4 protocol traffic by including a Layer 4 protocol parameter (see the "IP ACLs for Other Layer 4 Protocols" section). You can specify the protocol numerically (0-255) or with these keywords: ahp (51), eigrp (88), esp (50), gre (47), igrp (9), icmp (1), igmp (2), igrp (9), ip (0), ipinip (4), nos (94), ospf (89), pcp (108), pim (103), tcp (6), or udp (17).
Note
IP ACE Layer 4 TCP Classification Criteria
You can create Transmission Control Protocol (TCP) ACEs that match traffic for specific TCP ports by including TCP source and/or destination port parameters (for more information, see the "IP ACEs for TCP Traffic" section). You can specify TCP port parameters numerically (0-65535) or with these keywords:
Note
IP ACE Layer 4 UDP Classification Criteria
You can create User Datagram Protocol (UDP) ACEs that match traffic for specific UDP source and/or destination ports by including UDP port parameters (for more information, see the "IP ACEs for UDP Traffic" section). You can specify UDP port parameters numerically (0-65535) or with these keywords:
Note
IP ACE Layer 4 ICMP Classification Criteria
You can create Internet Control Management Protocol (ICMP) ACEs that match traffic containing specific ICMP messages by including ICMP types and optionally, ICMP codes (for more information, see the "IP ACEs for ICMP Traffic" section). You can specify ICMP types and codes numerically (0-255) or with these keywords:
administratively-prohibited
3
13
net-tos-unreachable
3
11
alternate-address1
6
—
net-unreachable
3
0
conversion-error
31
0
network-unknown
3
6
dod-host-prohibited
3
10
no-room-for-option
12
2
dod-net-prohibited
3
9
option-missing
12
1
echo
8
0
packet-too-big
3
4
echo-reply
0
0
parameter-problem
12
0
general-parameter-problem1
12
—
port-unreachable
3
3
host-isolated
3
8
precedence-unreachable
3
15
host-precedence-unreachable
3
14
protocol-unreachable
3
2
host-redirect
5
1
reassembly-timeout
11
1
host-tos-redirect
5
3
redirect1
5
—
host-tos-unreachable
3
12
router-advertisement
9
0
host-unknown
3
7
router-solicitation
10
0
host-unreachable
3
1
source-quench
4
0
information-reply
16
0
source-route-failed
3
5
information-request
15
0
time-exceeded1
11
—
mask-reply
18
0
timestamp-reply
14
0
mask-request
17
0
timestamp-request
13
0
mobile-redirect
32
0
traceroute
30
0
net-redirect
5
0
ttl-exceeded
11
0
net-tos-redirect
5
2
unreachable1
3
—
1 Matches all code values
Note
IP ACE Layer 4 IGMP Classification Criteria
You can create IGMP ACEs that match traffic containing specific IGMP messages by including an IGMP type parameter (for more information, see the "IP ACEs for IGMP Traffic" section). You can specify the IGMP type numerically (0-255) or with these keywords: host-query (1), host-report (2), dvmrp (3), pim (4), or trace (5).
Note
Note
IPX ACE Classification Criteria
You can create IPX ACEs that match specific IPX traffic by including these parameters (for more information, see the "Creating or Modifying Named IPX ACLs" section):
•
•
•
–
–
MAC ACE Layer 2 Classification Criteria
You can create MAC ACEs that match specific Ethernet traffic by including these Layer 2 parameters (for more information, see the "Creating or Modifying Named MAC ACLs" section):
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
QoS MAC ACLs that do not include an ethertype parameter match traffic with any value in the ethertype field, which allows MAC-level QoS to be applied to any traffic except IP and IPX.
Default ACLs
There are three default ACLs, one each for IP, and with a Layer 3 switching engine, IPX and MAC traffic. Each ACL has a single ACE that has a configurable marking rule and configurable policers. The default ACLs have nonconfigurable classification criteria that matches all traffic. QoS compares any traffic with a supported ethertype field value that does not match a named ACL to the default ACLs. Unmatched IP traffic matches the default IP ACL. Unmatched IPX traffic matches the default IPX ACL. Unmatched Ethernet traffic matches the default MAC ACL.
Note
Marking Rules
Note
Marking rules specify how QoS marks traffic when the traffic matches the filtering parameters in an ACE (see the "ACE Name, Marking Rule, Policing, and Filtering Syntax" section). QoS supports four marking rules, that are specified with the following four ACE keywords: trust-dscp, trust-ipprec, trust-cos, and dscp. Each ACE contains one of the keywords. The marking rules are as follows:
•
•
Note
•
•
–
–
–
–
Note
QoS uses configurable mapping tables to set the DSCP value, which is 6 bits, from CoS and IP precedence, which are 3-bit values (for more information, see the "Mapping Received CoS Values to Internal DSCP Values" section and the "Mapping Received IP Precedence Values to Internal DSCP Values" section).
Policers
You can create named policers that specify bandwidth utilization limits, which you can apply to traffic by including the policer name in an ACE (for more information, see the "Creating Policers" section).
Policing uses a token bucket scheme. As packets arrive, the packet size in bytes is added to the bucket level. Every 0.25 ms, a value equal to the token rate is subtracted from the bucket level.
You specify the bandwidth utilization limits as an average rate and a maximum burst size. Packets that exceed these limits are "out of profile." Traffic is in profile as long as it flows in at an average rate and never bursts beyond the burst size.
In each policer, you specify if out-of-profile packets are to be dropped or to have a new DSCP value applied to them (applying a new DSCP value is called "markdown"). Since out-of-profile packets do not retain their original priority, they are not counted as part of the bandwidth that is consumed by in-profile packets.
For all policers, QoS uses a configurable table that maps received DSCP values to marked-down DSCP values (for more information, see the "Mapping DSCP Markdown Values" section). When markdown occurs, QoS gets the marked-down DSCP value from the table. You cannot specify a marked-down DSCP value in individual policers.
Note
You give each policer a unique name when you create it and then use the name to include the policer in an ACE. The same policer can be used in multiple ACEs.
You can create these policers:
•
•
•
–
–
Note
You can include both a microflow policer and an aggregate policer in each ACE to police a flow based on both its own bandwidth utilization and on its bandwidth utilization combined with that of other flows.
For example, you could create a microflow policer named "group_individual" with bandwidth limits that are suitable for individuals in a group and you could create an aggregate policer named "group_all" with bandwidth limits that are suitable for the group as a whole. You could include both policers in ACEs that match the group's traffic. The combination would affect individuals separately and the group cumulatively.
For ACEs that include both a microflow policer and an aggregate policer, QoS responds to an out-of-profile status from either policer, and as specified by the policer, applies a new DSCP value or drops the packet. If both policers return an out-of-profile status, then if either policer specifies that the packet is to be dropped, it is dropped; otherwise, QoS applies a new DSCP value.
Follow these guidelines when creating policers:
•
•
•
•
•
PFC2 Policing Decisions
With a PFC2, the policing decision consists of two levels:
•
•
Packets are dropped if the excess rate aggregate policer returns an out-of-profile decision and the drop indication flag is set, or if the microflow policer returns an out-of-profile decision and the drop indication flag is set.
If an excess police level is set, the excess DSCP mapping is used to replace the original DSCP value with a marked-down value. If only a normal police level is set, the normal DSCP mapping is used. The excess police level has precedence for selecting mapping rules when both police levels are set because the excess police level represents the worst out-of-profile transgression.
Attaching ACLs
You can configure each port for either port-based QoS (default) or VLAN-based QoS (see the "Enabling Port-Based or VLAN-Based QoS" section) and attach ACLs to the selected interface (see the "Attaching ACLs to Interfaces" section). You can attach up to three named ACLs, one of each type (IP, IPX, and Ethernet) to each port and VLAN.
On ports that are configured for VLAN-based QoS, you can attach named ACLs to the port's VLAN. For a trunk, you can attach named ACLs to any VLANs that are allowed on the trunk as follows:
•
•
On ports that are configured for port-based QoS, you can attach named ACLs to the port as follows:
•
•
Final Layer 3 Switching Engine CoS and ToS Values
With a Layer 3 switching engine, QoS associates CoS and ToS values with traffic as specified by the marking rules and policers in the ACE that the traffic matches (see the "Internal DSCP Values" section). The associated CoS and ToS are used at the Ethernet egress port (see the "Ethernet Egress Port Scheduling, Congestion Avoidance, and Marking" section).
Classification and Marking with a Layer 2 Switching Engine
With a Layer 2 Switching Engine, QoS can classify traffic that is addressed to specified MAC address/VLAN pairs to be marked with a configured CoS value (for more information, see the "QoS Terminology" section and the "Mapping a CoS Value to a Host Destination MAC Address/VLAN Pair" section).
Note
Ethernet Egress Port Scheduling, Congestion Avoidance, and Marking
These sections describe Ethernet egress port scheduling, congestion avoidance, and marking:
•
Overview
QoS schedules traffic through the transmit queues based on CoS values and uses CoS-value-based transmit-queue drop thresholds to avoid congestion in traffic that is transmitted from Ethernet ports.
Note
Transmit Queues
Enter the show port capabilities command to see the queue structure of a port. The command displays one of the following:
•
•
•
•
All port types have a low-priority and a high-priority standard transmit queue. 1p3q1t ports have a medium-priority standard transmit queue. 1p2q2t, 1p3q1t, and 1p2q1t ports have a strict-priority transmit queue in addition to the standard queues.
On 2q2t ports, the default QoS configuration allocates a minimum of 80 percent of the total transmit queue size to the low-priority standard queue and a minimum of 20 percent to the high-priority standard queue.
On 1p2q2t, 1p3q1t, and 1p2q1t ports, the switch services traffic in the strict-priority queue before servicing the standard queues. When the switch is servicing a standard queue, after transmitting a packet, it checks for traffic in the strict-priority queue. If the switch detects traffic in the strict-priority queue, it suspends its service of the standard queue and completes service of all traffic in the strict-priority queue before returning to the standard queue.
On 1p2q2t ports, the default QoS configuration allocates a minimum of 70 percent of the total transmit queue size to the low-priority standard queue, a minimum of 15 percent to the high-priority standard queue, and a minimum of 15 percent to the strict-priority queue.
On 1p3q1t ports, the transmit queue size is not configurable and is allocated equally among all queues.
On 1p2q1t ports, the default QoS configuration allocates a minimum of 50 percent of the total transmit queue size to the low-priority standard queue, a minimum of 30 percent to the high-priority standard queue, and a minimum of 20 percent to the strict-priority queue.
Scheduling and Congestion Avoidance
These sections describe scheduling and congestion avoidance:
Note
2q2t Ports
For 2q2t ports, each transmit queue has two tail-drop thresholds that function as follows:
•
–
–
•
–
–
1p2q2t Ports
1p2q2t ports have a strict-priority queue and two standard transmit queues. The two standard transmit queues each have two WRED-drop thresholds.
•
•
–
–
•
–
–
1p3q1t Ports
1p3q1t ports have a strict-priority queue and three standard transmit queues. The standard transmit queues each have one WRED-drop threshold and one nonconfigurable tail-drop threshold.
•
•
•
•
Note
1p2q1t Ports
1p2q1t ports have a strict-priority queue and two standard transmit queues. The standard transmit queues each have one WRED-drop threshold and one nonconfigurable tail-drop threshold.
•
•
–
–
Note
Marking
When traffic is transmitted from the switch, QoS writes the ToS byte into IP traffic (Layer 3 switching engine only) and the CoS value that was used for scheduling and congestion avoidance into ISL or 802.1Q traffic (for more information, see the "Final Layer 3 Switching Engine CoS and ToS Values" section).
QoS Statistics Data Export
The QoS statistics data export feature generates per-port and per-aggregate policer utilization information and forwards this information in UDP packets to traffic monitoring, planning, or accounting applications. You can enable QoS statistics data export on a per-port or per-aggregate policer basis. The statistics data that is generated per port consists of counts of the input and output packets and bytes. The aggregate policer statistics consists of counts of allowed packets and counts of packets exceeding the policed rate.
The QoS statistics data collection occurs periodically at a fixed interval, but the interval at which the data is exported is configurable. QoS statistics collection is enabled by default, and the data export feature is disabled by default for all ports and all aggregate policers that are configured on the Catalyst 6500 series switch.
Note
•
For information on configuring QoS statistics data export, see the "Configuring QoS Statistics Data Export" section.
QoS Default Configuration
Table 43-3 shows the QoS default configuration.
Table 43-3 QoS Default Configuration
QoS enable state
Disabled
Note—With QoS enabled and all other QoS parameters at default values, QoS sets Layer 3 DSCP to 0 and Layer 2 CoS to 0 in all traffic that is transmitted from the switch.
Port CoS value
0
IntraVLAN microflow policing
Disabled
CoS to internal DSCP map
(internal DSCP set from CoS values)CoS 0 = DSCP 0
CoS 1 = DSCP 8
CoS 2 = DSCP 16
CoS 3 = DSCP 24
CoS 4 = DSCP 32
CoS 5 = DSCP 40
CoS 6 = DSCP 48
CoS 7 = DSCP 56IP precedence to internal DSCP map
(internal DSCP set from IP precedence values)IP precedence 0 = DSCP 0
IP precedence 1 = DSCP 8
IP precedence 2 = DSCP 16
IP precedence 3 = DSCP 24
IP precedence 4 = DSCP 32
IP precedence 5 = DSCP 40
IP precedence 6 = DSCP 48
IP precedence 7 = DSCP 56Internal DSCP to egress CoS map
(egress CoS set from internal DSCP values)DSCP 0-7 = CoS 0
DSCP 8-15 = CoS 1
DSCP 16-23 = CoS 2
DSCP 24-31 = CoS 3
DSCP 32-39 = CoS 4
DSCP 40-47 = CoS 5
DSCP 48-55 = CoS 6
DSCP 56-63 = CoS 7Marked-down DSCP from DSCP map
Marked-down DSCP value equals original DSCP value (no markdown)
Policers
None
Named ACLs
None
Default ACLs
Supports per-port classification and marking, sets DSCP to 0 in traffic from untrusted ports, no policing
COPS1 support
Disabled
RSVP support
Disabled
QoS statistics data export
Disabled
Runtime—Port based or VLAN based
Port based
Config—Port based or VLAN based
Port based
Port trust state
Untrusted
2q2t transmit-queue size ratio
Low priority: 80%; high priority: 20%
1p1q0t receive-queue size ratio
Standard: 80%; strict priority: 20%
1p2q2t transmit-queue size ratio
Low priority: 70%; high priority: 15%; strict priority: 15%
1p2q1t transmit-queue size ratio
Low priority: 70%; high priority: 15%; strict priority: 15%
1p2q1t standard transmit-queue low:high priority bandwidth allocation ratio
100:255
2q2t, 1p2q2t, and 1p2q1t standard transmit-queue low:high priority bandwidth allocation ratio
5:255
1p3q1t standard transmit-queue low:medium:high-priority bandwidth allocation ratio
100:150:200
1q4t/2q2t receive and transmit-queue CoS value/drop-threshold mapping
•
transmit queue 1/drop threshold 1 (80%): CoS 0 and 1•
transmit queue 1/drop threshold 2 (100%): CoS 2 and 3•
transmit queue 2/drop threshold 1 (80%): CoS 4 and 5•
transmit queue 2/drop threshold 2 (100%): CoS 6 and 71q2t port receive-queue CoS value/drop-threshold mapping and threshold percentages
•
–
–
•
–
–
Note
1p1q4t/1p2q2t port receive and transmit-queue CoS value/drop-threshold mapping and threshold percentages
•
strict-priority transmit queue 1: CoS 5•
transmit queue 1/drop threshold 1:–
–
•
transmit queue 1/drop threshold 2:–
–
•
transmit queue 2/drop threshold 1:–
–
•
transmit queue 2/drop threshold 2:–
–
1p1q0t receive-queue CoS value mapping
•
CoS 0, 1, 2, 3, 4, 6, and 7•
1p3q1t transmit-queue CoS value/drop-threshold mapping
•
–
–
•
–
–
•
–
–
•
1p1q8t receive-queue port CoS value/drop-threshold mapping
•
CoS 0, 1, 2, 3, 4, 6, and 7:–
Low WRED threshold: 40%
High WRED-drop threshold: 70%–
Low WRED threshold: 40%
High WRED-drop threshold: 70%–
Low WRED threshold: 50%
High WRED-drop threshold: 80%–
Low WRED threshold: 50%
High WRED-drop threshold: 80%–
Low WRED threshold: 60%
High WRED-drop threshold: 90%–
Low WRED threshold: 60%
High WRED-drop threshold: 90%–
Low WRED threshold: 70%
High WRED-drop threshold: 100%•
1p2q1t transmit-queue port CoS value/drop-threshold mapping
•
–
–
–
•
–
–
–
•
Runtime—Port based or VLAN based
VLAN based
Config—Port based or VLAN based
Port based
Port trust state
trust-cos (Layer 2 switching engine)
trust-dscp (Layer 3 switching engine)Receive-queue drop-threshold percentages
All thresholds set to 100%
Transmit-queue drop-threshold percentages
All thresholds set to 100%
Transmit-queue low-priority/high-priority bandwidth allocation ratio
255:1
Transmit-queue size ratio
•
•
CoS value/drop-threshold mapping
Receive-drop threshold 1 and transmit-queue 1/drop threshold 1: CoS 0-7
1 COPS = Common Open Policy Service
Configuring QoS on the Switch
These sections describe how to configure QoS on the Catalyst 6500 series switches:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Enabling QoS
To enable QoS, perform this task in privileged mode:
This example shows how to enable QoS:
Console> (enable) set qos enableQoS is enabled.Console> (enable)Enabling Port-Based or VLAN-Based QoS
Note
By default, QoS uses ACLs that are attached to ports. On a per-port basis, you can configure QoS to use ACLs that are attached to a VLAN. To enable VLAN-based QoS on a port, perform this task in privileged mode:
Step 1
Enable VLAN-based QoS on a port.
set port qos mod/port {port-based | vlan-based}
Step 2
Verify the configuration.
show port qos mod/port
For more information, see the "Attaching ACLs" section.
This example shows how to enable VLAN-based QoS on a port:
Console> (enable) set port qos 1/1-2 vlan-basedHardware programming in progress...QoS interface is set to vlan-based for ports 1/1-2.Console> (enable)Changing a port from port-based to VLAN-based QoS detaches all ACLs from the port. Any ACLs that are attached to the VLAN apply to the port immediately (for more information, see the "Attaching ACLs to Interfaces" section).
Configuring the Trust State of a Port
This command configures the trust state of a port (for more information, see the "Ethernet Ingress Port Marking, Scheduling, Congestion Avoidance, and Classification" section). By default, all ports are untrusted.
To configure the trust state of a port, perform this task in privileged mode:
Step 1
Configure the trust state of a port.
set port qos trust {untrusted | trust-cos | trust-ipprec | trust-dscp}
Step 2
Verify the configuration.
show port qos
Note the following syntax guidelines when configuring the trust state of a port:
•
•
•
This example shows how to configure port 1/1 with the trust-cos keyword:
Console> (enable) set port qos 1/1 trust trust-cosPort 1/1 qos set to trust-cosConsole> (enable)
Note
Configuring the CoS Value for a Port
Note
Unmarked frames from ports that are configured as trusted and all frames from ports that are configured as untrusted are assigned the CoS value that is specified with this command.
To configure the CoS value for a port, perform this task in privileged mode:
Step 1
Configure the CoS value for a port.
set port qos cos cos_value
Step 2
Verify the configuration.
show port qos
This example shows how to configure the port CoS value to 3 for port 1/1:
Console> (enable) set port qos 1/1 cos 3Port 1/1 qos cos set to 3Console> (enable)To revert to the default CoS value for a port, perform this task in privileged mode:
Step 1
Revert to the default CoS value for a port.
clear port qos cos
Step 2
Verify the configuration.
show port qos
This example shows how to revert to the default CoS value for port 1/1:
Console> (enable) clear port qos 1/1 cosPort 1/1 qos cos setting cleared.Console> (enable)Creating Policers
Note
To create a policer, perform this task in privileged mode:
For more information, see the "Policers" section and the"PFC2 Policing Decisions" section.
The policer_name parameter can be up to 31 characters long, is case sensitive, and may include a-z, A-Z, 0-9, the dash character (-), the underscore character (_), and the period character (.). Policer names must start with an alphabetic character (not a digit) and must be unique across all microflow and aggregate policers. You cannot use keywords from any command as a policer name.
The valid values for the rate and erate parameters are 32 Kbps (entered as 32) to 32 Gbps (entered as 32000000); or to classify all traffic as out of profile, set the rate parameter to zero (0). Set the erate parameter to a higher value than the rate parameter. The PFC1 and PFC2 have the following hardware granularity for rate values:
Within each range, QoS programs the hardware with rate values that are multiples of the granularity values.
The valid values for the burst and eburst parameters are 1 Kb (entered as 1) to 32 Mb (entered as 32000). When configuring burst and eburst parameters, note the following:
•
•
•
•
Enter either the drop keyword to cause all out-of-profile packets to be dropped or the policed-dscp keyword to cause all out-of-profile packets with the normal rate to be marked down as specified in the normal markdown DSCP map (for more information, see the "Mapping DSCP Markdown Values" section).
This example shows how to create a microflow policer with a 1-Mbps rate limit and a 10-Mb burst limit that marks down out-of-profile traffic:
Console> (enable) set qos policer microflow my-micro rate 1000 burst 10000 policed-dscpHardware programming in progress...QoS policer for microflow my-micro created successfully.Console> (enable)For PFC2, this example shows how to create an aggregate excess rate policer with a 64-Kbps rate limit and a 128-Kb burst limit that drops traffic exceeding these values:
Console> (enable) set qos policer aggregate test rate 64 burst 128 dropQoS policer for aggregate test created successfully.Console> (enable) show qos policer config aggregate testQoS aggregate policers:QoS aggregate policers:Aggregate name Normal rate (kbps) Burst size (kb) Normal action----------------------------- ------------------ --------------- -------------test 64 128 policed-dscpExcess rate (kbps) Burst size (kb) Excess action------------------ --------------- -------------64 128 dropACL attached------------------------------------Console> (enable)For PFC2, this example shows how to create an aggregate excess rate policer with a 64-Kbps rate limit and a 100-Kb burst limit that will cause all out-of-profile packets to be marked down as specified in the normal markdown DSCP map:
Console> (enable) set qos policer aggregate test2 rate 64 burst 100 policed-dscpQoS policer for aggregate test2 created successfully.Console> (enable) show qos policer config aggregate test2QoS aggregate policers:Aggregate name Normal rate (kbps) Burst size (kb) Normal action----------------------------- ------------------ --------------- -------------test2 64 100 policed-dscpExcess rate (kbps) Burst size (kb) Excess action------------------ -------------- ---------------8000000 100 policed-dscpACL attached------------------------------------Console> (enable)For PFC2, this example shows how to create an aggregate excess rate policer with a 64-Kbps rate limit and a 128-Kb burst limit that will cause traffic that exceeds the normal rate of 64 Kbps and a burst size of 96 Kb to be marked down as specified in the normal markdown DSCP map, and traffic that exceeds 128 Kbps and a burst size of 96 Kb to be dropped:
Console> (enable) set qos policer aggregate test3 rate 64 policed-dscp erate 128 drop burst 96QoS policer for aggregate test3 created successfully.Console> (enable) show qos policer config aggregate test3QoS aggregate policers:Aggregate name Normal rate (kbps) Burst size (kb) Normal action----------------------------- ------------------ --------------- -------------test3 64 96 policed-dscpExcess rate (kbps) Burst size (kb) Excess action------------------ --------------- ---------------128 96 dropACL attached------------------------------------Console> (enable)Deleting Policers
Note
To delete one or all policers, perform this task in privileged mode:
This example shows how to delete the microflow policer named my_micro:
Console> (enable) clear qos policer microflow my_micromy_micro QoS microflow policer cleared.Console> (enable)Creating or Modifying ACLs
Note
These sections describe ACL creation and modification:
•
•
•
•
•
ACL Names
ACL names can be up to 31 characters long, are case sensitive, and may include a-z, A-Z, 0-9, the dash character (-), the underscore character (_), and the period character (.). ACL names must start with an alphabetic character and must be unique across all QoS ACLs of all types. You cannot use keywords from any command as an ACL name.
ACE Name, Marking Rule, Policing, and Filtering Syntax
ACE command syntax is organized as follows:
ACL_command ACL_type_and_name marking_rule policing_rule filteringFor example, in an IP ACE, the command syntax is as follows:
set qos acl ip acl_name {dscp dscp_value | trust-cos | trust-ipprec | trust-dscp} [microflow microflow_name] [aggregate aggregate_name] src_ip_spec [precedence precedence | dscp-field dscp] [before editbuffer_index | modify editbuffer_index]
•
•
•
•
Named IP ACLs
These sections describe creating or modifying IP ACLs:
•
•
Source and Destination IP Addresses and Masks
In IP ACEs, specify the source and destination IP addresses and masks (represented by the src_ip_spec and dest_ip_spec parameters in the following sections) in the form ip_address mask. The mask is mandatory. Use one bits, which need not be contiguous, where you want wildcards.
Use any of the following formats for the address and mask:
•
•
•
Port Operator Parameters
In IP ACEs, the operator parameter can be one of the following:
•
•
•
•
•
See the "Layer 4 Operations Configuration Guidelines" section for restrictions that apply to QoS ACLs.
Precedence Parameter Options
For precedence parameter keyword options in IP ACEs, see the "IP ACE Layer 3 Classification Criteria" section.
IP ACEs for TCP Traffic
To create or modify an IP ACE for TCP traffic, perform this task in privileged mode:
For port parameter keyword options, see the "IP ACE Layer 4 TCP Classification Criteria" section.
The established keyword matches traffic with the ACK or RST bits set.
This example shows how to create an IP ACE for TCP traffic:
Console> (enable) set qos acl ip my_IPacl trust-ipprec microflow my-micro aggregate my-agg tcp any anymy_IPacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)IP ACEs for UDP Traffic
To create or modify an IP ACE for UDP traffic, perform this task in privileged mode:
For port parameter keyword options, see the "IP ACE Layer 4 UDP Classification Criteria" section.
This example shows how to create an IP ACE for UDP traffic:
Console> (enable) set qos acl ip my_IPacl trust-ipprec microflow my-micro aggregate my-agg udp any anymy_IPacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)IP ACEs for ICMP Traffic
To create or modify an IP ACE for ICMP traffic, perform this task in privileged mode:
For icmp_code and icmp_type parameter keyword options, see the "IP ACE Layer 4 ICMP Classification Criteria" section.
This example shows how to create an IP ACE for ICMP echo traffic:
Console> (enable) set qos acl ip my_IPacl trust-ipprec microflow my-micro aggregate my-agg icmp any any echomy_IPacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)IP ACEs for IGMP Traffic
Note
To create or modify an IP ACE for IGMP traffic, perform this task in privileged mode:
For igmp_type parameter keyword options, see the "IP ACE Layer 4 IGMP Classification Criteria" section.
This example shows how to create an IP ACE for IGMP Protocol Independent Multicast (PIM) traffic:
Console> (enable) set qos acl ip my_IPacl trust-ipprec microflow my-micro aggregate my-agg igmp any any pimmy_IPacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)IP ACLs for Other Layer 4 Protocols
To create or modify a named IP ACL with additional parameters that match all Layer 4 protocols, perform this task in privileged mode:
For protocol parameter keyword options, see the "IP ACE Layer 4 Protocol Classification Criteria" section.
This example shows how to create an IP ACE for IPINIP traffic:
Console> (enable) set qos acl ip my_IPacl trust-ipprec microflow my-micro aggregate my-agg ipinip any anymy_IPacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)IP ACEs for Any IP Traffic
To create or modify an IP ACE that matches all IP traffic, perform this task in privileged mode:
This example shows how to create an IP ACE:
Console> (enable) set qos acl ip my_IPacl trust-ipprec microflow my-micro aggregate my-agg anymy_IPacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)Modifying the Default IP ACL
To modify the default IP ACL, perform this task in privileged mode:
For more information, see the "Default ACLs" section.
This example shows how to modify the default IP ACL:
Console> (enable) set qos acl default-action ip dscp 5 microflow my-micro aggregate my-aggQoS default-action for IP ACL is set successfully.Console> (enable)Creating or Modifying Named IPX ACLs
To create or modify a named IPX ACL, perform this task in privileged mode:
The protocol parameter can be specified numerically (0-255) or with these keywords: any, ncp (17), netbios (20), rip (1), sap (4), or spx (5).
The src_net and dest_net parameters are IPX network numbers, entered as up to 8 hexadecimal digits in the range 1 to FFFFFFFE (-1 matches any network number). You do not need to enter leading zeros.
If you specify an IPX destination network, IPX ACEs support the following optional parameters:
•
•
•
This example shows how to create an IPX ACE:
Console> (enable) set qos acl ipx my_IPXacl trust-cos aggregate my-agg -1my_IPXacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)Creating or Modifying Named MAC ACLs
To create or modify a named MAC ACL, perform this task in privileged mode:
Enter the src_mac_spec and dest_mac_spec parameters as a MAC address and a mask. Each parameter is 12 hexadecimal digits (48 bits), formatted as dash-separated pairs. Use one bits, which need not be contiguous, where you want wildcards. Use the any keyword for a MAC address and mask of 0-0-0-0-0-0 ff-ff-ff-ff-ff-ff. Use the host keyword with a MAC address to specify an all-zero mask (mac_address 0-0-0-0-0-0).
Enter the ethertype parameter as 4 hexadecimal digits (16 bits) prefaced with 0x (for example, 0x0600) or as a keyword (see the "MAC ACE Layer 2 Classification Criteria" section).
This example shows how to create a MAC ACE:
Console> (enable) set qos acl mac my_MACacl trust-cos aggregate my-agg any anymy_MACacl editbuffer modified. Use `commit' command to apply changes.Console> (enable)
Note
Creating or Modifying the Default IPX and MAC ACLs
To create or modify the default IPX or MAC ACL, perform this task in privileged mode:
For more information, see the "Default ACLs" section.
This example shows how to modify the default IPX ACL:
Console> (enable) set qos acl default-action ipx dscp 5 aggregate my-aggQoS default-action for IPX ACL is set successfully.Console> (enable)
Note
Deleting Named ACLs
To delete a named ACL, perform this task in privileged mode:
Step 1
Delete a named ACL.
clear qos acl acl_name [editbuffer_index]
Step 2
Verify the configuration.
show qos acl info {acl_name | all}
This example shows how to delete the ACL named icmp_acl:
Console> (enable) clear qos acl icmp_acl 1ACL icmp_acl ACE# 1 is deleted.icmp_acl editbuffer modified. Use `commit' command to apply changes.Console> (enable)Reverting to Default Values in Default ACLs
To revert to the default values for a default ACL, perform this task in privileged mode:
This example shows how to revert to the default values for the default IP ACL:
Console> (enable) clear qos acl default-action ipHardware programming in progress...QoS default-action for IP ACL is restored to default setting.Console> (enable)Discarding Uncommitted ACLs
To discard an uncommitted new ACL or uncommitted changes to an existing ACL, perform this task in privileged mode:
Step 1
Discard an uncommitted ACL.
rollback qos acl {acl_name | all}
Step 2
If you discarded changes to an existing ACL, verify the configuration.
show qos acl info {acl_name | all}
This example shows how to discard an uncommitted ACL named my_acl:
Console> (enable) rollback qos acl my_aclRollback for QoS ACL my_acl is successful.Console> (enable)
Note
Committing ACLs
When you create, change, or delete a named ACL, the changes exist temporarily in an edit buffer in memory. To commit the ACL so that it can be used, perform this task in privileged mode:
Step 1
Commit an ACL.
commit qos acl acl_name
Step 2
Verify the configuration.
show config qos acl {acl_name | all}
This example shows how to commit an ACL named my_acl:
Console> (enable) commit qos acl my_aclHardware programming in progress...ACL my_acl is committed to hardware.Console> (enable)
Note
See the "Configuring and Storing VACLs and QoS ACLs in Flash Memory" section for information about where QoS ACLs are stored.
Attaching ACLs to Interfaces
Note
You can attach one ACL of each type to each VLAN and to each port that is configured for port-based QoS. You cannot attach ACLs to a port that is configured for VLAN-based QoS (for more information, see the "Enabling Port-Based or VLAN-Based QoS" section). When an ACL of a particular type (IP, IPX, or Ethernet) is already attached to an interface, attaching a different ACL of the same type detaches the previous ACL.
To attach an ACL to a port or a VLAN, perform this task in privileged mode:
Step 1
Attach an ACL to an interface.
set qos acl map acl_name {mod/port | vlan}
Step 2
Verify the configuration.
show qos acl map {config | runtime} {acl_name | mod/port | vlan | all}
This example shows how to attach an ACL named my_acl to port 2/1:
Console> (enable) set qos acl map my_acl 2/1Hardware programming in progress...ACL my_acl is attached to port 2/1.Console> (enable)This example shows how to attach an ACL named my_acl to VLAN 4:
Console> (enable) set qos acl map my_acl 4Hardware programming in progress...ACL my_acl is attached to vlan 4.Console> (enable)
Note
Detaching ACLs from Interfaces
Note
To detach an ACL from a port or a VLAN, perform this task in privileged mode:
This example shows how to detach an ACL named my_acl from port 2/1:
Console> (enable) clear qos acl map my_acl 2/1Hardware programming in progress...ACL my_acl is detached from port 2/1.Console> (enable)This example shows how to detach an ACL named my_acl from VLAN 4:
Console> (enable) clear qos acl map my_acl 4Hardware programming in progress...ACL my_acl is detached from vlan 4.Console> (enable)
Note
Mapping a CoS Value to a Host Destination MAC Address/VLAN Pair
Note
To map a CoS value to all frames that are destined for a particular host destination MAC address and VLAN number value pair, perform this task in privileged mode:
Step 1
Map a CoS value to a host destination MAC address/VLAN pair.
set qos mac-cos dest_mac VLAN cos_value
Step 2
Verify the configuration.
show qos mac-cos {dest_mac [vlan] | all}
This example shows how to map CoS 2 to a destination MAC address and VLAN 525:
Console> (enable) set qos mac-cos 00-40-0b-30-03-48 525 2CoS 2 is assigned to 00-40-0b-30-03-48 vlan 525.Console> (enable)Deleting a CoS Value to a Host Destination MAC Address/VLAN Pair
Note
To delete a host destination MAC address and VLAN number value pair CoS assignment, perform this task in privileged mode:
This example shows how to delete all CoS assignments to destination MAC addresses and VLANs:
Console> (enable) clear qos mac-cos allAll CoS to Mac/Vlan entries are cleared.Console> (enable)Enabling or Disabling Microflow Policing of Bridged Traffic
Note
By default, microflow policers affect only Layer 3-switched traffic. To enable or disable microflow policing of bridged traffic on the switch or on specified VLANs, perform one of these tasks in privileged mode:
Note
For more information, see the "Policers" section.
This example shows how to enable microflow policing of traffic in VLANs 1 through 20:
Console> (enable) set qos bridged-microflow-policing enable 1-20QoS microflow policing is enabled for bridged packets on vlans 1-20.Console> (enable)Configuring Standard Receive-Queue Tail-Drop Thresholds
To configure the standard receive-queue tail-drop thresholds on the switch, perform this task in privileged mode:
Configure the standard receive-queue tail-drop thresholds.
set qos drop-threshold port_type rx queue 1 thr1 thr2 thr3 thr4
For more information, see the "Receive Queues" section.
QoS maintains separate configurations for 1q2t, 1q4t, and 1p1q4t ports. This command configures the standard queue. Specify queue 1 (the threshold in the strict-priority queue, when present, is not separately configurable; it uses threshold 4 as specified for queue 1).
The thresholds are all specified as percentages ranging from 1-100. A value of 10 indicates a threshold when the buffer is 10 percent full.
This example shows how to configure the standard receive-queue tail-drop thresholds:
Console> (enable) set qos drop-threshold 1q4t rx queue 1 20 40 75 100Receive drop thresholds for queue 1 set at 20% 40% 75% 100%Console> (enable)
Note
Configuring 2q2t Port Standard Transmit-Queue Tail-Drop Thresholds
To configure the standard transmit-queue tail-drop thresholds on all 2q2t ports, perform this task in privileged mode:
Configure the standard transmit-queue tail-drop thresholds on all 2q2t ports.
set qos drop-threshold port_type tx queue q# thr1 thr2
Queue number 1 is the low-priority transmit queue and queue number 2 is high priority. In each queue, the low-priority threshold number is 1 and the high-priority threshold number is 2.
The thresholds are all specified as percentages ranging from 1-100. A value of 10 indicates a threshold when the buffer is 10 percent full.
This example shows how to configure the low-priority transmit-queue tail-drop thresholds:
Console> (enable) set qos drop-threshold 2q2t tx queue 1 40 100Transmit drop thresholds for queue 1 set at 40% 100%Console> (enable)
Note
Configuring Standard Queue WRED-Drop Thresholds
1p2q2t, 1p3q1t, and 1p2q1t ports have weighted random early detection (WRED)-drop thresholds in their standard transmit queues.
A 1p1q8t port has WRED-drop thresholds in its standard receive queue.
Note
To configure the standard queue WRED-drop thresholds on all ports of each type, perform this task in privileged mode:
When configuring 1p2q2t ports, note the following:
•
•
•
–
–
When configuring 1p3q1t ports, note the following:
•
•
•
•
When configuring 1p1q8t ports, note the following:
•
•
–
–
–
When configuring 1p2q1t ports, note the following:
•
•
•
When configuring thresholds, note the following:
•
•
•
This example shows how to configure the low-priority transmit-queue WRED-drop thresholds:
Console> (enable) set qos wred 1p2q2t queue 1 40:70 70:100WRED thresholds for queue 1 set to 40:70 and 70:100 on all WRED-capable 1p2q2t ports.Console> (enable)
Note
Allocating Bandwidth Between Standard Transmit Queues
The switch transmits frames from one standard queue at a time using a weighted-round robin (WRR) algorithm. WRR uses a weight value to decide how much to transmit from one queue before switching to the other. The higher the weight assigned to a queue, the more transmit bandwidth is allocated to it.
To allocate bandwidth between standard transmit queues, perform this task in privileged mode:
Allocate bandwidth between standard transmit queues.
set qos wrr port_type queue1-weight queue2-weight [queue3-weight]
The valid values for the port_type parameter are 2q2t, 1p2q2t, 1p3q1t, and 1p2q1t.
Note
QoS maintains separate configurations for each port type. This command configures only the standard queues; the strict-priority queue requires no configuration. The valid values for weight range from 1-255.
This example shows how to allocate bandwidth for the 2q2t ports:
Console> (enable) set qos wrr 2q2t 30 70QoS wrr ratio is set successfully.Console> (enable)Configuring the Receive-Queue Size Ratio
For 1p1q0t and 1p1q8t ports, estimate the mix of standard-priority and strict-priority traffic on your network (for example, 85 percent standard-priority traffic and 15 percent strict-priority traffic). Specify queue ratios with the estimated percentages, which must range from 1-99 and together add up to 100.
To configure the receive-queue size ratio, perform this task in privileged mode:
Configure the receive-queue size ratio between receive queue 1 (standard priority) and receive queue 2 (strict priority).
set qos rxq-ratio {1p1q0t | 1p1q8t} queue1-val queue2-val
This example shows how to configure the receive-queue size ratio:
Console> (enable) set qos rxq-ratio 1p1q0t 80 20QoS rxq-ratio is set successfully.Console> (enable)Configuring the Transmit-Queue Size Ratio
For 2q2t, 1p2q2t, and 1p2q1t ports, estimate the mix of traffic of various priorities on your network (for example, 75 percent low-priority traffic, 15 percent high-priority traffic, and 10 percent strict-priority traffic). Specify queue ratios with the estimated percentages, which must range from 1-99 and together add up to 100.
To configure the transmit-queue size ratio for each port type, perform this task in privileged mode:
Configure the transmit-queue size ratio.
set qos txq-ratio {2q2t | 1p2q2t | 1p2q1t} queue1-val queue2-val [queue3-val]
This example shows how to configure the transmit-queue size ratio:
Console> (enable) set qos txq-ratio 2q2t 80 20QoS txq-ratio is set successfully.Console> (enable)Mapping CoS Values to Drop Thresholds
This command associates CoS values with receive- and transmit-queue drop thresholds. QoS maintains separate configurations for each port type.
These sections describe mapping CoS values to drop thresholds:
•
•
•
Associating 1q4t/2q2t Ports
On 1q4t/2q2t ports, you configure the receive queues and the transmit queues with the same command.
To associate CoS values to the drop thresholds on 1q4t/2q2t ports, perform this task in privileged mode:
Step 1
Associate a CoS value to a drop threshold.
set qos map 2q2t tx q# thr# cos coslist
Step 2
Verify the configuration.
show qos info config {1q4t rx | 2q2t tx }
The receive- and transmit-drop thresholds have this relationship:
•
•
•
•
Use the transmit queue and transmit-queue drop-threshold values in this command. This example shows how to associate the CoS values 0 and 1 to both standard receive-queue 1/threshold 1 and standard transmit-queue 1/threshold 1:
Console> (enable) set qos map 2q2t tx 1 1 cos 0,1Qos tx priority queue and threshold mapped to cos successfully.Console> (enable)Associating 1q2t/1p2q2t and 1p1q4t/1p2q2t Ports
On 1q2t/1p2q2t and 1p1q4t/1p2q2t ports, you configure the receive queues and the transmit queues separately.
1q2t Receive Queues
To associate CoS values to 1q2t receive-queue drop thresholds, perform this task in privileged mode:
Step 1
Associate a CoS value to a receive-queue drop threshold.
set qos map 1q2t rx 1 1 cos coslist
Step 2
Verify the configuration.
show qos info config 1q2t rx
Threshold 1 is the low-priority threshold. Threshold 2, the high-priority threshold, is not configurable.
This example shows how to associate the CoS value 3 to high-priority threshold 2:
Console> (enable) set qos map 1q2t rx 1 1 cos 3QoS rx priority queue and threshold mapped to cos successfully.Console> (enable)1p1q4t Receive Queues
To associate CoS values to 1p1q4t receive-queue drop thresholds, perform this task in privileged mode:
Step 1
Associate a CoS value to a receive-queue drop threshold.
set qos map 1p1q4t rx q# thr# cos coslist
Step 2
Verify the configuration.
show qos info config 1p1q4t rx
Queue 1 is the standard queue, and queue 2 is the strict-priority queue.
Threshold numbers range from 1 for low priority to 4 for high priority.
This example shows how to associate the CoS value 5 to strict-priority receive-queue 2/threshold 1:
Console> (enable) set qos map 1p1q4t rx 2 1 cos 5Qos rx strict queue and threshold mapped to cos successfully.Console> (enable)1p2q2t Transmit Queues
To associate CoS values to the 1p2q2t transmit-queue drop thresholds, perform this task in privileged mode:
Step 1
Associate a CoS value to a transmit-queue drop threshold.
set qos map 1p2q2t tx q# thr# cos coslist
Step 2
Verify the configuration.
show qos info config 1p2q2t tx
Queue 1 is standard low priority, queue 2 is high priority, and queue 3 is strict priority.
Threshold 1 is low priority and threshold 2 is high priority.
This example shows how to associate the CoS value 5 to strict-priority transmit-queue 3/drop threshold 1:
Console> (enable) set qos map 1p2q2t tx 3 1 cos 5Qos tx strict queue and threshold mapped to cos successfully.Console> (enable)Associating 1p1q0t/1p3q1t Ports
On 1p1q0t/1p3q1t ports, you configure the receive queues and the transmit queues separately.
1p1q0t Receive Queues
To associate CoS values to 1p1q0t receive queues, perform this task in privileged mode:
Step 1
Associate a CoS value to a receive queue.
set qos map 1p1q0t rx q# cos coslist
Step 2
Verify the configuration.
show qos info config 1p1q0t rx
Queue 1 is the standard queue, and queue 2 is the strict-priority queue.
This example shows how to associate the CoS value 5 to strict-priority receive-queue 2:
Console> (enable) set qos map 1p1q0t rx 2 cos 5QoS queue mapped to cos successfully.Console> (enable)1p3q1t Transmit Queues
With 1p3q1t transmit queues, you can associate a CoS value with either the nonconfigurable tail-drop threshold or the configurable WRED-drop threshold as follows:
•
•
To associate CoS values to the 1p3q1t transmit-queue drop thresholds, perform this task in privileged mode:
Step 1
Associate a CoS value to a transmit-queue drop threshold.
set qos map 1p3q1t tx q# [thr#] cos coslist
Step 2
Verify the configuration.
show qos info config 1p3q1t tx
Queue 1 is the standard low-priority queue, queue 2 is the medium-priority queue, queue 3 is the high-priority queue, and queue 4 is the strict-priority queue.
To map CoS values to the tail-drop threshold, omit the threshold number or enter 0.
The WRED-drop threshold number is 1.
This example shows how to associate the CoS value 0 to transmit-queue 1/drop threshold 1:
Console> (enable) set qos map 1p3q1t tx 1 1 cos 0Qos tx strict queue and threshold mapped to cos successfully.Console> (enable)Associating 1p1q8t/1p2q1t Ports
When you configure 1p1q8t/1p2q1t ports, note the following:
•
•
–
–
1p1q8t Receive Queues
To associate CoS values to 1p1q8t receive queues, perform this task in privileged mode:
Step 1
Associate a CoS value to a receive queue.
set qos map 1p1q8t rx q# [thr#] cos coslist
Step 2
Verify the configuration.
show qos info config 1p1q8t rx
Queue 1 is the standard queue, and queue 2 is the strict-priority queue.
To map CoS values to the tail-drop threshold, omit the threshold number or enter 0.
The WRED-drop threshold number is 1.
This example shows how to associate the CoS value 5 to strict-priority receive-queue 2:
Console> (enable) set qos map 1p1q8t rx 2 cos 5QoS queue mapped to cos successfully.Console> (enable)1p2q1t Transmit Queues
To associate CoS values to the 1p2q1t transmit-queue drop thresholds, perform this task in privileged mode:
Step 1
Associate a CoS value to a transmit-queue drop threshold.
set qos map 1p2q1t tx q# [thr#] cos coslist
Step 2
Verify the configuration.
show qos info config 1p2q1t tx
Queue 1 is the standard low-priority queue, queue 2 is the standard high-priority queue, and queue 3 is the strict-priority queue.
To map CoS values to the tail-drop threshold, omit the threshold number or enter 0.
The WRED-drop threshold number is 1.
This example shows how to associate the CoS value 0 to transmit-queue 1/drop threshold 1:
Console> (enable) set qos map 1p2q1t tx 1 1 cos 0Qos tx strict queue and threshold mapped to cos successfully.Console> (enable)Reverting to CoS Map Defaults
To revert to default CoS value/drop threshold mapping, perform this task in privileged mode:
This example shows how to revert to CoS map defaults:
Console> (enable) clear qos map 1p3q1t txQos map setting cleared.Console> (enable)Configuring DSCP Value Maps
Note
These sections describe how DSCP values are mapped to other values:
•
•
•
Mapping Received CoS Values to Internal DSCP Values
To map received CoS values to the internal DSCP value (see the "Internal DSCP Values" section), perform this task in privileged mode:
Enter 8 DSCP values to which QoS maps received CoS values 0 through 7. This example shows how to map received CoS values to internal DSCP values:
Console> (enable) set qos cos-dscp-map 20 30 1 43 63 12 13 8QoS cos-dscp-map set successfully.Console> (enable)To revert to default CoS to DSCP value mapping, perform this task in privileged mode:
This example shows how to revert to CoS-DSCP map defaults:
Console> (enable) clear qos cos-dscp-mapQoS cos-dscp-map setting restored to default.Console> (enable)Mapping Received IP Precedence Values to Internal DSCP Values
To map received IP precedence values to the internal DSCP value (see the "Internal DSCP Values" section), perform this task in privileged mode:
Enter 8 internal DSCP values to which QoS maps received IP precedence values 0 through 7. This example shows how to map received IP precedence values to internal DSCP values:
Console> (enable) set qos ipprec-dscp-map 20 30 1 43 63 12 13 8QoS ipprec-dscp-map set successfully.Console> (enable)To revert to default IP precedence to DSCP value mapping, perform this task in privileged mode:
This example shows how to revert to QoS map defaults:
Console> (enable) clear qos ipprec-dscp-mapQoS ipprec-dscp-map setting restored to default.Console> (enable)Mapping Internal DSCP Values to Egress CoS Values
To map internal DSCP values to the egress CoS values that are used for egress port scheduling and congestion avoidance, perform this task in privileged mode:
For more information, see the "Internal DSCP Values" section and the "Ethernet Egress Port Scheduling, Congestion Avoidance, and Marking" section.
Enter up to 64 internal DSCP value list/egress CoS value pairs. This example shows how to map internal DSCP values to egress CoS values:
Console> (enable) set qos dscp-cos-map 20-25:7 33-38:3QoS dscp-cos-map set successfully.Console> (enable)To revert to default DSCP/CoS value mapping, perform this task in privileged mode:
This example shows how to revert to DSCP-CoS map defaults:
Console> (enable) clear qos dscp-cos-mapQoS dscp-cos-map setting restored to default.Console> (enable)Mapping DSCP Markdown Values
To map DSCP markdown values used by policers, perform this task in privileged mode:
For more information, see the "Policers" section.
Enter up to 64 DSCP-value-list/DSCP-value pairs.
This example shows how to map DSCP markdown values:
Console> (enable) set qos policed-dscp-map 20-25:7 33-38:3QoS dscp-dscp-map set successfully.Console> (enable)This example shows how to map DSCP markdown values for packets exceeding the excess rate:
Console> (enable) set qos policed-dscp-map 33:30QoS normal-rate policed-dscp-map set successfully.Console> (enable) set qos policed-dscp-map excess-rate 33:30QoS excess-rate policed-dscp-map set successfully.Console> (enable)
Note
To revert to default DSCP markdown value mapping, perform this task in privileged mode:
This example shows how to revert to DSCP markdown map defaults:
Console> (enable) clear qos policed-dscp-mapQoS dscp-cos-map setting restored to default.Console> (enable)
Note
Displaying QoS Information
To display QoS information, perform this task:
This example shows how to display the QoS runtime information for port 2/1:
Console> show qos info config 2/1QoS setting in NVRAM:QoS is enabledPort 2/1 has 2 transmit queue with 2 drop thresholds (2q2t).Port 2/1 has 1 receive queue with 4 drop thresholds (1q4t).Interface type:vlan-basedACL attached:The qos trust type is set to untrusted.Default CoS = 0Queue and Threshold Mapping:Queue Threshold CoS----- --------- ---------------1 1 0 11 2 2 32 1 4 52 2 6 7Rx drop thresholds:Rx drop thresholds are disabled for untrusted ports.Queue # Thresholds - percentage (abs values )------- -------------------------------------1 50% 60% 80% 100%Tx drop thresholds:Queue # Thresholds - percentage (abs values )------- -------------------------------------1 40% 100%2 40% 100%Tx WRED thresholds:WRED feature is not supported for this port_type.Queue Sizes:Queue # Sizes - percentage (abs values )------- -------------------------------------1 80%2 20%WRR Configuration of ports with speed 1000Mbps:Queue # Ratios (abs values )------- -------------------------------------1 1002 255Console> (enable)Displaying QoS Statistics
To display QoS statistics, perform this task:
Display QoS statistics.
show qos statistics {mod[/port] | l3stats | aggregate-policer [policer_name]}
This example shows how to display QoS statistics for port 2/1:
Console> (enable) show qos statistics 2/1On Transmit:Port 2/1 has 2 Queue(s) 2 Threshold(s)Q # Threshold #:Packets dropped--- -----------------------------------------------1 1:0 pkts, 2:0 pkts2 1:0 pkts, 2:0 pktsOn Receive:Port 2/1 has 1 Queue(s) 4 Threshold(s)Q # Threshold #:Packets dropped--- -----------------------------------------------1 1:0 pkts, 2:0 pkts, 3:0 pkts, 4:0 pktsThis example shows how to display QoS Layer 3 statistics:
Console> (enable) show qos statistics l3statsQoS Layer 3 Statistics show statistics since last read.Packets dropped due to policing: 0IP packets with ToS changed: 0IP packets with CoS changed: 26Non-IP packets with CoS changed: 0Console>This example shows how to display QoS aggregate policer statistics:
Console> (enable) show qos statistics aggregate-policerQoS aggregate-policer statistics:Aggregate Policer Packet Count Packets exceed Packets exceednormal rate excess rate-------------------------------- ------------ -------------- -----------------test 1000 20 5Reverting to QoS Defaults
Note
To revert to QoS defaults, perform this task in privileged mode:
This example shows how to revert to QoS defaults:
Console> (enable) clear qos configThis command will disable QoS and take values back to factory default.Do you want to continue (y/n) [n]? yQoS config cleared.Console> (enable)Disabling QoS
To disable QoS, perform this task in privileged mode:
This example shows how to disable QoS:
Console> (enable) set qos disableQoS is disabled.Console> (enable)Configuring COPS Support
Note
Note
These sections describe configuring COPS support:
•
•
•
•
•
•
•
•
•
Note
Port ASICs
Some COPS support features affect all ports that are controlled by a port ASIC. The following sections use the term per-ASIC to identify the features that configure all ports on the same port ASIC:
•
•
•
•
Understanding QoS Policy
The term QoS policy refers to the QoS values in effect, such as port trust state and which ACLs are applied to ports and VLANs.
Selecting COPS as the QoS Policy Source
QoS uses locally configured QoS values as the default QoS policy source. To select COPS as the QoS policy source, perform this task in privileged mode:
Step 1
Select COPS as the QoS policy source.
set qos policy-source {local | cops}
Step 2
Verify the QoS policy source.
show qos policy-source
This example shows how to select COPS as the QoS policy source:
Console> (enable) set qos policy-source copsQoS policy source for the switch set to COPS.Console> (enable) show qos policy-sourceQoS policy source for the switch set to COPS.Console> (enable)Selecting COPS as the QoS policy source switches the following values from locally configured values to received COPS values:
•
•
•
•
•
•
•
Selecting Locally Configured QoS Policy
To select locally configured QoS policy, perform this task in privileged mode:
Step 1
Select locally configured QoS policy.
set qos policy-source {local | cops}
Step 2
Verify the QoS policy source.
show qos policy-source
This example shows how to select locally configured QoS policy:
Console> (enable) set qos policy-source localQoS policy source for the switch set to local.Console> (enable) show qos policy-sourceQoS policy source for the switch set to local.Console> (enable)Enabling Use of Locally Configured QoS Policy
When enabled, COPS is the default QoS policy source for all ports. You can use locally configured QoS policy on a per-ASIC basis. To enable use of locally configured QoS policy on a port ASIC, perform this task in privileged mode:
Step 1
Enable use of locally configured QoS policy on a port.
set port qos policy-source {local | cops}
Step 2
Verify the QoS policy source for the port.
show port qos
This example shows how to enable use of locally configured QoS policy:
Console> (enable) set port qos 1/1 policy-source localQoS policy source set to local on port(s) 1/1-2.Console> (enable)Assigning Port Roles
COPS does not configure ports using slot number and port number parameters. COPS uses roles that you create and assign to port ASICs.
A role is a name that describes the capability of ports (for example, access or mod2_1-4). QoS supports 64 roles per switch. You can assign more than one role to a port ASIC (for example, mod2ports1-12 and access), with the limitation that the combined length of role names that are assigned to a port ASIC cannot exceed 255 characters.
The role name can be up to 31 characters long, is not case sensitive but may include uppercase and lowercase characters, and may consist of a-z, A-Z, 0-9, the dash character (-), the underscore character (_), and the period character (.). Role names cannot start with the underscore character.
The first assignment of a new role to a port creates the role.
To assign roles to a port ASIC, perform this task in privileged mode:
Step 1
Assign roles to a port ASIC.
set port cops {mod/port} roles role1 [role2] ...
Step 2
Verify the roles for the port.
show port cops [mod[/port]]
This example shows how to assign two new roles to the ASIC controlling port 2/1:
Console> (enable) set port cops 2/1 roles mod2ports1-12 accessNew role `mod2ports1-12' created.New role `access' created.Roles added for port 2/1-12.Console> (enable)Removing Roles from Port ASICs
To remove a role from a port ASIC, perform this task in privileged mode:
Step 1
Remove a role from a port ASIC.
clear port cops {mod/port} {all-roles | roles role1 [role2] ...}
Step 2
Verify the roles for the port.
show port cops [mod[/port]]
This example shows how to remove a role from a port ASIC:
Console> (enable) clear port cops 3/1 roles backbone_port main_portRoles cleared for port(s) 3/1-4.Console> (enable)Deleting Roles
To delete a role (which removes it from all ports), perform this task in privileged mode:
Step 1
Delete a role.
clear cops {all-roles | roles role1 [role2] ...}
Step 2
Verify the roles for the port.
show port cops [mod[/port]]
This example shows how to delete a role:
Console> (enable) clear cops roles backbone_port main_portRoles cleared.Console> (enable)Configuring Policy Decision Point Servers
Note
COPS obtains QoS policy from a PDP server. Configure a primary PDP server and optionally, a backup PDP server.
To configure a PDP server, perform this task in privileged mode:
Step 1
Configure a PDP server.
set cops server ip_address [port] [primary] [diff-serv | rsvp]
Step 2
Verify the PDP server configuration.
show cops info
The ip_address parameter can be the IP address or the name of the server.
The port variable is the PDP server TCP port number.
Use the diff-serv keyword to set the address only for COPS.
This example shows how to configure a PDP server:
Console> (enable) set cops server my_server1 primarymy_server1 added to the COPS diff-serv server table as primary server.my_server1 added to the COPS rsvp server table as primary server.Console> (enable)Deleting the PDP Server Configuration
To delete the PDP server configuration, perform this task in privileged mode:
Step 1
Delete the PDP server configuration.
clear cops server {all | ip_address [diff-serv | rsvp]}
Step 2
Verify the PDP server configuration.
show cops info
This example shows how to delete the PDP server configuration:
Console> (enable) clear cops server allAll COPS diff-serv servers cleared.All COPS rsvp servers cleared.Console> (enable)Configuring the COPS Domain Name
PDP servers use a COPS domain name to communicate with policy enforcement point (PEP) devices such as switches. To configure a COPS domain name for the switch, perform this task in privileged mode:
Step 1
Configure the COPS domain name.
set cops domain-name domain_name
Step 2
Verify the COPS domain name.
show cops info
This example shows how to configure a COPS domain name:
Console> (enable) set cops domain-name my_domainDomain name set to my_domain.Console> (enable)Deleting the COPS Domain Name
To delete the COPS domain name, perform this task in privileged mode:
Step 1
Delete the COPS domain name.
clear cops domain-name
Step 2
Verify the configuration.
show cops info
This example shows how to delete the COPS domain name:
Console> (enable) clear cops domain-nameDomain name cleared.Console> (enable)Configuring the COPS Communications Parameters
To configure the parameters that COPS uses to communicate with the PDP server, perform this task in privileged mode:
Step 1
Configure the parameters that COPS uses to communicate with the PDP server.
set cops retry-interval initial increment maximum
Step 2
Verify the configuration.
show cops info
Enter the parameters as a number of seconds in the range from 0 to 65535. The value of the initial parameter plus the value of the increment parameter must not exceed the value of the maximum parameter.
This example shows how to configure the parameters that COPS uses to communicate with the PDP server:
Console> (enable) set cops retry-interval 15 1 30Connection retry intervals set.Console> (enable)Configuring RSVP Support
Note
These sections describe configuring RSVP null service template and receiver proxy functionality support:
•
•
•
•
•
•
Note
Enabling RSVP Support
To enable RSVP support, perform this task in privileged mode:
Step 1
Enable RSVP support on the switch.
set qos rsvp {enable | disable}
Step 2
Verify the configuration.
show qos rsvp info
Step 3
Display RSVP activity.
show qos rsvp flow-info
This example shows how to enable RSVP support:
Console> (enable) set qos rsvp enableRSVP enabled on the switch.Console> (enable)Disabling RSVP Support
To disable RSVP support, perform this task in privileged mode:
Step 1
Disable RSVP support on the switch.
set qos rsvp {enable | disable}
Step 2
Verify the configuration.
show qos rsvp info
This example shows how to disable RSVP support:
Console> (enable) set qos rsvp disableRSVP disabled on the switch.Console> (enable)Enabling Participation in the DSBM Election
Catalyst 6500 series switches can serve as the Designated Subnet Bandwidth Manager (DSBM). You can enable participation in the election of the DSBM on a per-port basis.
Note
To enable the participation of a port in the election of the DSBM, perform this task in privileged mode:
The range for the priority parameter is from 128 to 255.
This example shows how to enable the participation of ports 2/1 and 3/2 in the election of the DSBM:
Console> (enable) set port rsvp 2/1,3/2 dsbm-election enable 232DSBM enabled and priority set to 232 for ports 2/1,3/2.Console> (enable)Disabling Participation in the DSBM Election
To disable the participation of a port in the election of the DSBM, perform this task in privileged mode:
This example shows how to disable the participation of port 2/1 in the election of the DSBM:
Console> (enable) set port rsvp 2/1 dsbm-election disableDSBM disabled for port 2/1.Console> (enable)Configuring Policy Decision Point Servers
Note
When the switch is the DSBM, RSVP communicates with a PDP server. Configure a primary PDP server and optionally, a backup PDP server.
To configure a PDP server, perform this task in privileged mode:
Step 1
Configure a PDP server.
set cops server ip_address [port] [primary] [diff-serv | rsvp]
Step 2
Verify the PDP server configuration.
show cops info
The ip_address parameter can be the IP address or the name of the server.
The port variable is the PDP server TCP port number.
Use the rsvp keyword to set the address only for RSVP.
This example shows how to configure a PDP server:
Console> (enable) set cops server my_server1 primary rsvpmy_server1 added to the COPS rsvp server table as primary server.Console> (enable)Deleting the PDP Server Configuration
To delete the PDP server configuration, perform this task in privileged mode:
Step 1
Delete the PDP server configuration.
clear cops server {all | ip_address [diff-serv | rsvp]}
Step 2
Verify the PDP server configuration.
show cops info
Use the rsvp keyword to delete only the RSVP address.
This example shows how to delete the PDP server configuration:
Console> (enable) clear cops server allAll COPS diff-serv servers cleared.All COPS rsvp servers cleared.Console> (enable)Configuring RSVP Policy Timeout
When the switch is the DSBM and communication with the PDP server is lost, the switch continues to function as the DSBM, using cached values, for the period specified by the timeout value; the behavior for new or modified RSVP path messages is determined by the RSVP local policy setting.
If communication with the PDP server is not reestablished before the timeout period expires, the switch reverts to the role of the Subnet Bandwidth Manager (SBM) client for all ports and forwards RSVP messages to a newly elected DSBM on the segment. When there is no communication with the PDP server, the switch does not participate in election of the DSBM.
To configure the time that the switch continues to be the DSBM after communication with the PDP server is lost, perform this task in privileged mode:
Step 1
Configure the RSVP policy timeout.
set qos rsvp policy-timeout timeout
Step 2
Verify the configuration.
show qos rsvp info
Enter the timeout parameter as a number of minutes in the range from 0 to 65535 (the default is 30).
This example shows how to configure the RSVP policy timeout:
Console> (enable) set qos rsvp policy-timeout 45RSVP database policy timeout set to 45 minutes.Console> (enable)Configuring RSVP Use of Local Policy
To configure how RSVP operates after communication with the PDP is lost, perform this task in privileged mode:
Step 1
Configure how RSVP operates when there is no communication with the PDP server.
set qos rsvp local-policy {forward | reject}
Step 2
Verify the configuration.
show qos rsvp info
The forward keyword sets the local policy to forward all new or modified RSVP path messages. The reject keyword sets the local policy to reject all new or modified RSVP path messages. This example shows how to change the default local RSVP policy setting to reject all new or modified RSVP path messages:
Console> (enable) set qos rsvp local-policy rejectRSVP local policy set to reject.Console> (enable)
Note
Configuring QoS Statistics Data Export
These sections describe how to configure the QoS statistics data export feature:
•
•
•
•
•
•
•
Enabling QoS Statistics Data Export Globally
To export QoS statistics data for ports and aggregate policers, you must first configure the feature globally.
To enable QoS statistics data export globally, perform this task in privileged mode:
Step 1
Enable QoS statistics data export.
set qos statistics export enable | disable
Step 2
Verify the configuration.
show qos statistics export info
This example shows how to enable QoS statistics data export globally and verify the configuration:
Console> (enable) set qos statistics export enableExport is enabled.Export destination:172.20.52.3 SYSLOG facility LOG_LOCAL6 (176), severity LOG_DEBUG (7)Aggregate policer export is not supportedConsole> (enable) show qos statistics export infoStatistics export status and configuration information------------------------------------------------------Export status: enabledExport time interval: 300Export destination:172.20.52.3 SYSLOG facility LOG_LOCAL6 (176), severity LOG_DEBUG (7)Port Export------ --------1/1 disabled1/2 disabled3/1 disabled3/2 disabled5/1 disabled5/2 disabled5/3 disabled5/4 disabled<...output truncated...>Console> (enable)Enabling Per-Port QoS Statistics Data Export
To enable QoS statistics data export on a per-port basis, perform this task in privileged mode:
Step 1
Enable QoS statistics data export per port.
set qos statistics export port mod/port enable | disable
Step 2
Verify the configuration.
show qos statistics export info
Note
This example shows how to enable the QoS statistics data export feature per port and verify the configuration:
Console> (enable) set qos statistics export port 5/1 enablePort export enabled on 5/1.Console> (enable) show qos statistics export infoStatistics export status and configuration information------------------------------------------------------Export status: enabledExport time interval: 300Export destination:172.20.52.3 SYSLOG facility LOG_LOCAL6 (176), severity LOG_DEBUG (7)Port Export------ --------1/1 disabled1/2 disabled3/1 disabled3/2 disabled5/1 enabled5/2 disabled<output truncated>Console> (enable)When enabled on a port, QoS statistics data export contains the following fields, separated by the delimiter character:
•
•
•
•
•
•
•
Enabling Per-Aggregate Policer QoS Statistics Data Export
To enable QoS statistics data export on a per-aggregate policer basis, perform this task in privileged mode:
Note
This example shows how to enable QoS statistics data export for a specific aggregate policer and verify the configuration:
Console> (enable) set qos statistics export aggregate ipagg_3 enableStatistics data export enabled for aggregate policer ipagg_3Console> (enable) show qos statistics export infoStatistics export status and configuration information------------------------------------------------------Export status: enabledExport time interval: 300Export destination:172.20.52.3 SYSLOG facility LOG_LOCAL6 (176), severity LOG_DEBUG (7)Port Export------ --------1/1 disabled1/2 disabled3/1 disabled3/2 disabled5/1 enabled5/2 disabled<output truncated>Aggregate name Export-------------- --------ipagg_3 enabledConsole> (enable)When enabled for a named aggregate policer, QoS statistics data export contains the following fields, separated by the delimiter character:
•
•
•
•
•
•
•
•
Clearing the Aggregate Policer QoS Statistics
To clear the aggregate policer QoS statistics, perform this task in privileged mode:
Step 1
Clear the aggregate policer QoS statistics.
clear qos statistics aggregate-policer [policer_name]
Step 2
Verify the configuration.
show qos statistics export info
This example shows how to clear the QoS aggregate policer statistics for a specific aggregate policer:
Console> (enable) clear qos statistics aggregate-policer aggr_1Aggregate policer 'aggr_1' statistical counters cleared.If you do not specify the aggregate policer, all aggregate policer statistics are cleared:
Console> (enable) clear qos statistics aggregate-policerQoS aggregate policers statistical counters cleared.Setting the QoS Statistics Data Export Time Interval
The default interval at which QoS statistics is exported is 30 seconds. To set the time interval for the QoS statistics data export, perform this task in privileged mode:
Step 1
Set the time interval for the QoS statistics data export.
set qos statistics export interval interval_seconds
Step 2
Verify the configuration.
show qos statistics export info
This example shows how to set the QoS statistics data export interval and verify the configuration:
Console> (enable) set qos statistics export interval 500Time interval set to 500Console> (enable) show qos statistics export infoStatistics export status and configuration information------------------------------------------------------Export status: enabledExport time interval: 500Export destination:172.20.52.3 SYSLOG facility LOG_LOCAL6 (176), severity LOG_DEBUG (7)Port Export------ --------1/1 disabled1/2 disabled3/1 disabled3/2 disabled5/1 enabled5/2 disabled<output truncated>Aggregate name Export-------------- --------ipagg_3 enabledConsole> (enable)Configuring the QoS Statistics Data Export Destination Host and UDP Port
To configure the QoS statistics data export destination host and UDP port number, perform this task in privileged mode:
This example shows how to configure the QoS statistics data export destination host and UDP port number and verify the configuration:
Console> (enable) set qos statistics export destination stargate 9996Statistics data export destination set to stargate port 9996.Console> (enable) show qos statistics export infoStatistics export status and configuration information------------------------------------------------------Export status: enabledExport time interval: 500Export destination:Stargate, UDP port 9996Port Export------ --------1/1 disabled1/2 disabled3/1 disabled3/2 disabled5/1 enabled5/2 disabled<output truncated>Aggregate name Export-------------- --------ipagg_3 enabledConsole> (enable)Displaying QoS Statistics Information
To display the QoS statistics per-aggregate policer packet and byte rates, perform this task in privileged mode:
Display the QoS statistics per-aggregate policer packet and byte rates.
show qos statistics aggregate-policer [policer_name]
This example shows how to display the QoS statistics per-aggregate policer packet and byte rates:
Console> show qos statistics aggregate-policerQoS aggregate-policer statistics:Aggregate Policer Packet Count Packets exceed Packets exceednormal rate excess rate-------------------------------- ------------ -------------- -----------------test 1000 20 5Console>
