42-71
Cisco7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
OL-4266-08
Chapter42 Configuring PFC QoS
Configuring PFCQo S
Class Map Filtering Guidelines and Restrictions
When configuring class map filtering, follow these guidelines and restrictions:
•With Release 12.2(18)SXE and later releases, PFC QoS supports multiple match criteria in class
maps configured with the match-any keywords.
•With releases earlier than Release 12.2(18)SXE, PFC QoS supports class maps that contain a single
match command.
•With 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 configure both a DSCP value and a Layer4 greater than (gt) or less than (lt) operator in an
IPv6 ACE, you cannot use the ACL for PFCQoS filtering.
–
If configure a DSCP value in one IPv6 ACL and a Layer4 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.
•Release 12.2(18)SXE and later releases support the match protocol ip command for IPv4 traffic.
•PFC QoS does not support the match cos, match any, match classmap, match
destination-address, match input-interface, match qos-group, and match source-address class
map commands.
•Cisco 7600 series routers do not detect the use of unsupported commands until you attach a policy
map to an interface.
•The PFC2 support 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/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/dtnbarad.htm
•Filtering based on IP precedence or DSCP for egress QoS uses the received IP precedence or DSCP.
Egress QoS filtering is not based on any IP precedence or DSCP changes made by ingress QoS.
Note This chapter includes the following ACL documentation:
•Configuring MAC ACLs, page 42-66
•Configuring ARP ACLs for QoS Filtering, page 42-69
Other ACLs are not documented in this publication. See the references under access-list in the
“PFC QoS Policy Configuration Overview” section on page42-65.
Configuring Filtering in a Class Map
To configure filtering in a class map, perform one of these tasks:
Command Purpose
Router(config-cmap)# match access-group name
acl_index_or_name
(Optional) Configures the class map to filter using an ACL.
Router(config-cmap)# no match access-group name
acl_index_or_name
Clears the ACL configuration from the class map.