42-84
Cisco7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
OL-4266-08
Chapter42 Con figuring PFC QoS
Configuring PFCQoS
Ingress CoS Mutation Configuration Guidelines and Restrictions
When configuring ingress CoS mutation, follow these guidelines and restrictions:
•Release 12.2(17b)SXA and later releases support ingress CoS mutation on WS-X6704-10GE,
WS-X6748-SFP, WS-X6724-SFP, and WS-X6748-GE-TX switching modules.
•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.
•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.
–
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.