Catalyst 6500 Release 12.2SY Software Configuration Guide

Configuring Named DSCP Mutation Maps

To configure a named DSCP mutation map, perform this task:

• You can enter up to 8 DSCP values that map to a mutated DSCP value.
• You can enter multiple commands to map additional DSCP values to a mutated DSCP value.
• You can enter a separate command for each mutated DSCP value.

This example shows how to map DSCP 30 to mutated DSCP value 8:

This example shows how to verify the configuration:

Note In the DSCP mutation map displays, the marked-down DSCP values are shown in the body of the matrix; the first digit of the original DSCP value is in the column labeled d1 and the second digit is in the top row. In the example shown, DSCP 30 maps to DSCP 08.

Attaching an Egress DSCP Mutation Map to an Interface

To attach an egress DSCP mutation map to an interface, perform this task:

This example shows how to attach the egress DSCP mutation map named mutmap1 to Fast Ethernet port 5/36:

Ingress CoS Mutation Configuration Guidelines and Restrictions

• Ports that are not configured as IEEE 802.1Q tunnel ports do not support ingress CoS mutation.
• Ports that are not configured to trust received CoS do not support ingress CoS mutation.
• Ingress CoS mutation does not change the CoS value carried by the customer frames. When the customer traffic exits the 802.1Q tunnel, the original CoS is intact.
• These switching modules support ingress CoS mutation:

– WS-X6704-10GE

– WS-X6848-SFP-2T, WS-X6748-SFP

– WS-X6824-SFP-2T, WS-X6724-SFP

– WS-X6848-TX-2T, WS-X6748-GE-TX

• Ingress CoS mutation configuration applies to all ports in a port group. The port groups are:

– WS-X6704-10GE:
4 ports, 4 port groups, 1 port in each group

– WS-X6848-SFP-2T, WS-X6748-SFP:
48 ports, 4 port groups: ports 1–12, 13–24, 25–36, and 37–48

– WS-X6824-SFP-2T, WS-X6724-SFP:
24 ports, 2 port groups: ports 1–12 and 13–24

– WS-X6848-TX-2T, WS-X6748-GE-TX:
48 ports, 4 port groups: ports 1–12, 13–24, 25–36, and 37–48

• To avoid ingress CoS mutation configuration failures, only create EtherChannels where all member ports support ingress CoS mutation or where no member ports support ingress CoS mutation. Do not create EtherChannels with mixed support for ingress CoS mutation.
• If you configure ingress CoS mutation on a port that is a member of an EtherChannel, the ingress CoS mutation is applied to the port-channel interface.
• You can configure ingress CoS mutation on port-channel interfaces.
• With ingress CoS mutation configured on a port-channel interface, the following occurs:

– The ingress CoS mutation configuration is applied to the port groups of all member ports of the EtherChannel. If any member port cannot support ingress CoS mutation, the configuration fails.

– If a port in the port group is a member of a second EtherChannel, the ingress CoS mutation configuration is applied to the second port-channel interface and to the port groups of all member ports of the second EtherChannel. If any member port of the second EtherChannel cannot support ingress CoS mutation, the configuration fails on the first EtherChannel. If the configuration originated on a nonmember port in a port group that has a member port of the first EtherChannel, the configuration fails on the nonmember port.

– The ingress CoS mutation configuration propagates without limit through port groups, member ports, and port-channel interfaces, regardless of whether or not the ports are configured to trust CoS or are configured as IEEE 802.1Q tunnel ports.

• An EtherChannel where you want to configure ingress CoS mutation must not have member ports that are in port groups containing member ports of other EtherChannels that have member ports that do not support ingress CoS mutation. (This restriction extends without limit through all port-group-linked member ports and port-channel-interface-linked ports.)
• A port where you want to configure ingress CoS mutation must not be in a port group that has a member port of an EtherChannel that has members that do not support ingress CoS mutation. (This restriction extends without limit through all port-group-linked member ports and port-channel-interface-linked ports.)
• There can be only be one ingress CoS mutation configuration applied to all port-group-linked member ports and port-channel-interface-linked ports.

Configuring Ingress CoS Mutation Maps

To configure an ingress CoS mutation map, perform this task:

This example shows how to configure a CoS mutation map named testmap:

This example shows how to verify the map configuration:

Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports

To attach an ingress CoS mutation map to an IEEE 802.1Q tunnel port, perform this task:

This example shows how to attach the ingress CoS mutation map named testmap to Gigabit Ethernet port 1/1:

Mapping Received CoS Values to Internal DSCP Values

To configure the mapping of received CoS values to the DSCP value that PFC QoS uses internally on the PFC, perform this task:

This example shows how to configure the received CoS to internal DSCP map:

This example shows how to verify the configuration:

Mapping Received IP Precedence Values to Internal DSCP Values

To configure the mapping of received IP precedence values to the DSCP value that PFC QoS uses internally on the PFC, perform this task:

This example shows how to configure the received IP precedence to internal DSCP map:

This example shows how to verify the configuration:

Configuring DSCP Markdown Values

To configure the mapping of DSCP markdown values used by policers, perform this task:

When configuring a DSCP markdown map, note the following information:

• You can enter the normal-burst keyword to configure the markdown map used by the exceed-action policed-dscp-transmit keywords.
• You can enter the max-burst keyword to configure the markdown map used by the violate-action policed-dscp-transmit keywords.

Note When you create a policer that does not use the pir keyword, and the maximum_burst_bytes parameter is equal to the normal_burst_bytes parameter (which occurs if you do not enter the maximum_burst_bytes parameter), the exceed-action policed-dscp-transmit keywords cause PFC QoS to mark traffic down as defined by the policed-dscp max-burst markdown map.

• To avoid out-of-sequence packets, configure the markdown maps so that conforming and nonconforming traffic uses the same queue.
• You can enter up to 8 DSCP values that map to a marked-down DSCP value.
• You can enter multiple commands to map additional DSCP values to a marked-down DSCP value.
• You can enter a separate command for each marked-down DSCP value.

Note Configure marked-down DSCP values that map to CoS values consistent with the markdown penalty.

This example shows how to map DSCP 1 to marked-down DSCP value 0:

This example shows how to verify the configuration:

Note In the Policed-dscp displays, the marked-down DSCP values are shown in the body of the matrix; the first digit of the original DSCP value is in the column labeled d1 and the second digit is in the top row. In the example shown, DSCP 41 maps to DSCP 41.

Mapping Internal DSCP Values to Egress CoS Values

To configure the mapping of the DSCP value that PFC QoS uses internally on the PFC to the CoS value used for egress LAN port scheduling and congestion avoidance, perform this task:

• You can enter up to 8 DSCP values that PFC QoS maps to a CoS value.
• You can enter multiple commands to map additional DSCP values to a CoS value.
• You can enter a separate command for each CoS value.

This example shows how to configure internal DSCP values 0, 8, 16, 24, 32, 40, 48, and 54 to be mapped to egress CoS value 0:

This example shows how to verify the configuration:

Note In the Dscp-cos map display, the CoS values are shown in the body of the matrix; the first digit of the DSCP value is in the column labeled d1 and the second digit is in the top row. In the example shown, DSCP values 41 through 47 all map to CoS 05.

Enabling DSCP-Based Queue Mapping

To enable DSCP-based queue mapping, perform this task:

This example shows how to enable DSCP-based queue mapping on 10-Gigabit Ethernet port 6/1:

This example shows how to verify the configuration:

Configuring Ingress DSCP-Based Queue Mapping

• Enabling DSCP-Based Queue Mapping
• Mapping DSCP Values to Standard Receive-Queue Thresholds

Note Ingress DSCP-to-queue mapping is supported only on ports configured to trust DSCP.

Mapping DSCP Values to Standard Receive-Queue Thresholds

To map DSCP values to the standard receive-queue thresholds, perform this task:

When mapping DSCP values, note the following information:

• You can enter up to 8 DSCP values that map to a queue and threshold.
• You can enter multiple commands to map additional DSCP values to the queue and threshold.
• You must enter a separate command for each queue and threshold.

This example shows how to map the DSCP values 0 and 1 to threshold 1 in the standard receive queue for 10-Gigabit Ethernet port 6/1 port 6/1:

Note The receive queue mapping is shown in the second queue thresh dscp-map displayed by the show queueing interface command.

This example shows how to verify the configuration:

Mapping DSCP Values to Standard Transmit-Queue Thresholds

To map DSCP values to standard transmit-queue thresholds, perform this task:

• You can enter up to 8 DSCP values that map to a queue and threshold.
• You can enter multiple commands to map additional DSCP values to the queue and threshold.
• You must enter a separate command for each queue and threshold.

This example shows how to map the DSCP values 0 and 1 to standard transmit queue 1/threshold 1 for 10-Gigabit Ethernet port 6/1 port 6/1:

Note The eighth queue is the strict priority queue in the output of the show queueing interface command.

This example shows how to verify the configuration:

Mapping DSCP Values to the Transmit Strict-Priority Queue

To map DSCP values to the transmit strict-priority queue, perform this task:

• The queue number is always 1.
• You can enter up to 8 DSCP values to map to the queue.
• You can enter multiple commands to map additional DSCP values to the queue.

This example shows how to map DSCP value 7 to the strict-priority queue on 10 Gigabit Ethernet port 6/1:

Note The strict priority queue is queue 8 in the output of the show queueing interface command.

This example shows how to verify the configuration:

http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html

Participate in the Technical Documentation Ideas forum