Cisco WS-SUP32-GE-3B Software Configuration Guide - Page 604

Configuring PFC QoS Chapter 38 Configuring PFC QoS Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports PFC QoS supports ingress CoS mutation on IEEE 802.1Q tunnel ports configured to trust received CoS (see the "Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports" section on page 38-72 for the list of supported modules). When you configure ingress CoS mutation on an IEEE 802.1Q tunnel port that you have configured to trust received CoS, PFC QoS uses the mutated CoS value instead of the received CoS value in the ingress drop thresholds and for any trust CoS marking and policing. These sections describe how to configure ingress CoS mutation: • Ingress CoS Mutation Configuration Guidelines and Restrictions, page 38-70 • Configuring Ingress CoS Mutation Maps, page 38-71 • Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports, page 38-72 Ingress CoS Mutation Configuration Guidelines and Restrictions When configuring ingress CoS mutation, follow these 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. • PFC QoS supports ingress CoS mutation on WS-X6704-10GE, WS-X6748-SFP, WS-X6724-SFP, and WS-X6748-GE-TX switching modules. • 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-X6748-SFP-48 ports, 4 port groups: ports 1-12, 13-24, 25-36, and 37-48 - WS-X6724-SFP-24 ports, 2 port groups: ports 1-12 and 13-24 - 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. 38-70 Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY OL-11439-03