Configuring Traffic Classes; Configuring Acl Classification - Cisco Nexus 7000 Series Configuration Manual

Configuring Traffic Classes

• Queuing cbqosmib will only be pulled when the following actions are configured: queue-limit,
• For F1 module proxy-forwarded traffic, ACL classification is matched against the layer 3 protocols
• show policy-map interface [interface type] type queuing uses L2 MTU (Frame length) and counts as
• show policy-map interface [interface type] type qos uses L3 MTU (Packet length).
Table 10: Protocol Number and Associated Layer 3 Protocol
Protocol Number
1
2
4
6
17
Note Layer 3 protocols not listed in the table are classified as protocol number 4 (IPv4 Encapsulation).
Configuring Traffic Classes

Configuring ACL Classification

Note The device does not support the no form of the match access-group name command.
You can classify traffic by matching packets based on existing ACLs. The permit and deny ACL keywords
are ignored in the matching. QoS does not use the permit-deny functions of ACLs. You can classify by either
IPv4 or IPv6.
Support is available for controlling deny access control entry ([no] hardware access-list allow deny ace) in
the CLI. For more information about this support, see the Cisco Nexus 7000 Series NX-OS Security
Configuration Guide.
Note Tunneled IP packets are matched unless the tunneling protocol is also IP, and then the match applies to the
outer IP header and not the encapsulated IP header.
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
32
random-detect, bandwidth, and priority.
shown in the following table.
a full packet length.
Layer 3 Protocol
ICMP
IGMP
IPv4 Encapsulation
TCP
UDP
Configuring Classification