Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual page 545

Chapter 38 Configuring PFC QoS
Port-Based PFC QoS and VLAN-Based PFC QoS
You can configure each ingress LAN port for either physical port-based PFC QoS (default) or
VLAN-based PFC QoS and attach a policy map to the selected interface.
On ports configured for port-based PFC QoS, you can attach a policy map to the ingress LAN port as
follows:
•
•
On a nontrunk ingress LAN port configured for VLAN-based PFC QoS, traffic received through the port
is subject to the policy map attached to the port's VLAN.
On a trunking ingress LAN port configured for VLAN-based PFC QoS, traffic received through the port
is subject to the policy map attached to the traffic's VLAN.
PFC QoS Egress Port Features
These sections describe PFC QoS egress port features:
•
•
•
•
•
•
OL-11439-03
On a nontrunk ingress LAN port configured for port-based PFC QoS, all traffic received through the
port is subject to the policy map attached to the port.
On a trunking ingress LAN port configured for port-based PFC QoS, traffic in all VLANs received
through the port is subject to the policy map attached to the port.
Flowchart of PFC QoS Egress LAN Port Features, page 38-12
Egress CoS Values, page 38-12
Egress DSCP Mutation with a PFC3B, page 38-12
Egress ToS Byte, page 38-13
Egress PFC QoS Interfaces, page 38-13
Egress ACL Support for Remarked DSCP, page 38-13
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
Understanding How PFC QoS Works
38-11