Pfc3B Guidelines - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Chapter 38 Configuring PFC QoS

PFC3B Guidelines

•
•
•
•
•
•
•
•
•
•
•
•
•
OL-11439-03
rcv-queue random-detect
–
rcv-queue random-detect max-threshold
–
rcv-queue random-detect min-threshold
–
rcv-queue queue-limit
–
rcv-queue cos-map
–
rcv-queue threshold
–
The PFC3B supports QoS for IPv6 unicast and multicast traffic.
To display information about IPv6 PFC QoS, enter the show mls qos ipv6 command.
The QoS features implemented in the port ASICs (queue architecture and dequeuing algorithms)
support IPv4 and IPv6 traffic.
The PFC3B supports IPv6 named extended ACLs and named standard ACLs.
The PFC3B supports the match protocol ipv6 command.
Because of conflicting TCAM lookup flow key bit requirements, you cannot configure IPv6
DSCP-based filtering and IPv6 Layer 4 range-based filtering on the same interface. For example:
If you configure both a DSCP value and a Layer 4 "greater than" (gt) or "less than" (lt) operator
–
in an IPv6 ACE, you cannot use the ACL for PFC QoS filtering.
If you configure a DSCP value in one IPv6 ACL and a Layer 4 "greater than" (gt) or "less than"
–
(lt) operator in another IPv6 ACL, you cannot use both ACLs in different class maps on the same
interface for PFC QoS filtering.
You can apply aggregate and microflow policers to IPv6 traffic, but you cannot apply microflow
policing to IPv6 multicast traffic.
With egress ACL support for remarked DSCP configured, the PFC3B does not provide
hardware-assistance for these features:
– Cisco IOS reflexive ACLs
TCP intercept
–
Context-Based Access Control (CBAC)
–
Network Address Translation (NAT)
–
You cannot apply microflow policing to ARP traffic.
The PFC3B does not apply egress policing to traffic that is being bridged to the PISA.
The PFC3B does not apply egress policing or egress DSCP mutation to multicast traffic from the
PISA.
With a PFC3B, PFC QoS does not rewrite the ToS byte in bridged multicast traffic.
The PFC3B supports up to 1023 aggregate policers, but some PFC QoS commands other than the
police command will be included in this count. By default, any policy using a set or trust command
will be included in the aggregate policer count. You can disable the addition of the set or trust
commands to the aggregate policer count by entering the no mls qos marking statistics command,
but you will then be unable to collect statistics for the classmaps associated with these commands.
You can view the aggregate policer count in the QoS Policer Resources section of the output of the
show platform hardware capacity qos command.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
PFC QoS Configuration Guidelines and Restrictions
38-41