Guidelines And Limitations For Traffic Storm Control - Cisco Nexus 3000 Series Configuration Manual

Configuring Traffic Storm Control
• Trap—You can configure traffic storm control to generate an SNMP trap when ingress traffic exceeds
By default, Cisco NX-OS takes no corrective action when traffic exceeds the configured level.

Guidelines and Limitations for Traffic Storm Control

When configuring the traffic storm control level, follow these guidelines and limitations:
• You can configure traffic storm control on a port-channel interface.
• Specify the level as a percentage of the total interface bandwidth:
• There are local link and hardware limitations that prevent storm-control drops from being counted
• Because of hardware limitations and the method by which packets of different sizes are counted, the
• Due to a hardware limitation, the output for the show interface counters storm-control command does
• Due to a hardware limitation, the packet drop counter cannot distinguish between packet drops caused
• Storm control is only for ingress traffic, specifically for unknown unicast, unknown multicast, and
• The link-level control protocols (LACP, LLDP and so on) are not affected in case of a traffic storm. The
• The burst size values are:
OL-29545-03
the shutdown and no shutdown options on the configured interface, or the error-disable detection and
recovery feature. You are recommended to use the errdisable recovery cause storm-control command
for error-disable detection and recovery along with the errdisable recovery interval command for
defining the recovery interval. The interval can range between 30 and 65535 seconds.
the configured traffic storm control level. The SNMP trap action is enabled by default. However, storm
control traps are not rate-limited by default. You can control the number of traps generated per minute
by using the snmp-server enable traps storm-control trap-rate command.
◦ The level can be from 0 to 100.
◦ The optional fraction of a level can be from 0 to 99.
◦ 100 percent means no traffic storm control.
◦ 0.0 percent suppresses all traffic.
separately. Instead, storm-control drops are counted with other drops in the discards counter.
level percentage is an approximation. Depending on the sizes of the frames that make up the incoming
traffic, the actual enforced level might differ from the configured level by several percentage points.
not show ARP suppressions when storm control is configured and the interface is actually suppressing
ARP broadcast traffic. This limitation can lead to the configured action not being triggered, but the
incoming ARP broadcast being correctly storm suppressed.
by a traffic storm and certain other discarded input frames. This limitation can lead to the configured
action being triggered even in the absence of a traffic storm.
broadcast traffic.
storm control is applied to data plane traffic only.
◦ For a 10G port, 48.68 Mbytes/390Mbits
◦ For a 1G port, 25 Mbytes/200Mbits
Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide, Release 6.x
Guidelines and Limitations for Traffic Storm Control
145