Pfc3 Guidelines; Pfc2 Guidelines - Cisco 7604 Configuration Manual
Ios software configuration guide
Hide thumbs
Also See for 7604:
- Configuration manual (742 pages) ,
- Installation manual (324 pages) ,
- User manual (98 pages)
Table of Contents
Advertisement
Chapter 41
Configuring PFC QoS
PFC3 Guidelines
•
•
•
•
•
•
•
•
•
•
•
•
•
PFC2 Guidelines
•
OL-4266-08
With Release 12.2(18)SXE and later releases, all versions of the PFC3 support 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 PFC3 supports IPv6 named extended ACLs and named standard ACLs.
In Release 12.2(18)SXE and later releases, the PFC3 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.
In Release 12.2(18)SXE and later releases, 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 PFC3 does not provide
hardware-assistance for these features:
Cisco IOS reflexive ACLs
–
TCP intercept
–
Context-Based Access Control (CBAC)
–
Network Address Translation (NAT)
–
With a PFC3, you cannot apply microflow policing to ARP traffic.
The PFC3 does not apply egress policing to traffic that is being bridged to the MSFC3.
The PFC3 does not apply egress policing or egress DSCP mutation to multicast traffic from the
MSFC3.
With a PFC2 or PFC3A, PFC QoS does not rewrite the ToS byte in bridged multicast traffic.
The PFC3 supports up to 1022 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.
The PFC2 supports the match protocol class map command, which configures NBAR and sends all
traffic on the Layer 3 interface, both ingress and egress, to be processed in software on the MSFC2.
To configure NBAR, refer to this publication:
http://www.cisco.com/en/US/docs/ios/12_4t/qos/configuration/guide/qsnbar1.html
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
PFC QoS Configuration Guidelines and Restrictions
41-53
- Quick Links:
- Supported Hardware and Software
Hide quick links:
Advertisement
Chapters
Table of Contents
