Prerequisites For Policing; Guidelines And Limitations - Cisco Nexus 9000 Series Configuration Manual

Prerequisites for Policing

Product
Cisco NX-OS

Prerequisites for Policing

Policing has the following prerequisites:
• You must be familiar with using modular QoS CLI.
• You are logged on to the device.

Guidelines and Limitations

Policing has the following configuration guidelines and limitations:
• show commands with the internal keyword are not supported.
• Each module polices independently, which might affect QoS features that are applied to traffic that is
• All policers in the ingress direction must use the same mode.
• Policing only supports violated and non-violated statistics when using either double width or single
• Using the optional keyword, no-stats disables statistics and ensures that applicable policies are shared.
• You can only use the set qos-group command in ingress policies.
• When egress RACL and egress QoS are applied together, you can only enable statistics for one or the
• Does not support egress QoS policies on ALE uplink ports on top-of-rack (TOR) platforms.
• When using egress QoS, Cisco recommends using the appropriate match criteria to match data traffic.
•
•
• Egress QoS policies are not supported on Cisco Nexus 9200 Series switches (For 7.0(3)I3(1)).
• QOS policing policies can be enabled on subinterfaces.
Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x
84
distributed across multiple modules. The following are examples of these QoS features:
◦ Policers applied to a port channel interface.
◦ Policers applied to a VLAN.
width TCAM with e-qos-lite.
other, not both.
(Avoid match criteria such as permit ip any any.)
License Requirement
The QoS feature does not a require license. Any
feature not included in a license package is bundled
with the NX-OS image and is provided at no extra
charge to you. For a complete explanation of the
Cisco NX-OS licensing scheme, see the
Licensing Guide.
Configuring Policing
Cisco NX-OS