CLI Reference Guide-R05

Table Of Contents
Chapter 14
| Congestion Control Commands
Storm Control Commands
– 429 –
Storm Control Commands
Storm control commands can be used to configure broadcast, multicast, and
unknown unicast storm control thresholds. Traffic storms may occur when a device
on your network is malfunctioning, or if application programs are not well
designed or properly configured. If there is too much traffic on your network,
performance can be severely degraded or everything can come to complete halt.
You can protect your network from traffic storms by setting a threshold for
broadcast, multicast or unknown unicast traffic. Any packets exceeding the
specified threshold will then be dropped.
switchport
packet-rate
This command configures broadcast, multicast and unknown unicast storm
control. Use the no form to restore the default setting.
Syntax
switchport {broadcast | multicast | unknown-unicast} packet-rate rate
no switchport {broadcast | multicast | unknown-unicast}
broadcast - Specifies storm control for broadcast traffic.
multicast - Specifies storm control for multicast traffic.
unknown-unicast - Specifies storm control for unknown unicast traffic.
rate - Threshold level as a rate; i.e., kilobits per second (kbps).
(Range: 64-1000000 for Gigabit Ethernet ports)
Default Setting
Broadcast Storm Control: Enabled, packet-rate limit: 64 kbps
Multicast Storm Control: Disabled
Unknown Unicast Storm Control: Disabled
Command Mode
Interface Configuration (Ethernet, Port Channel)
Table 84: Rate Limit Commands
Command Function Mode
storm-sample-type Toggles threshold value units of storm control
settings to be either packets per second or kilobits
per second
GC
switchport packet-rate
*
* Enabling hardware-level storm control with this command on a port will disable software-level
automatic storm control on the same port if configured by the auto-traffic-control command.
Configures broadcast, multicast, and unknown
unicast storm control thresholds
IC
show interfaces
switchport
Displays the administrative and operational status
of an interface
NE, PE