This article describes the following syslog message:
ESWD_ST_CTL_ERROR_IN_EFFECT
This condition occurs when a storm control error condition is detected.
When an
ESWD_ST_CTL_ERROR_IN_EFFECT
event occurs, a message similar to the following is reported:
eswd[10108]: ESWD_ST_CTL_ERROR_IN_EFFECT: ae7.0: storm control in effect on the port
The interface specified in the syslog message has exceeded the threshold for storm control and could either shut down or discard broadcasts, depending on the configuration. That is, the interface is receiving more broadcast traffic (either unicast or multicast) than the broadcast threshold limit set in the configuration.
For further information on this feature, refer to the technical documentation related to Storm Control.
Perform these steps to determine the cause and resolve the problem (if any). Continue through each step until the problem is resolved.
1. Collect the show command output.
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log messages show ethernet-switching interfaces show ethernet-switching table show ethernet-switching-options storm-control
2. Analyze the show command output.
Look for any related events that occurred at or just before the
ESWD_ST_CTL_ERROR_IN_EFFECT
error in the log messages output. These might help identify the cause.
3. Determine the source of the broadcast storm in your network (that is, find the MAC address from which the broadcast address is coming).
4. During a maintenance window, as it will impact transit traffic, enter the command
clear interface statistics
, and change the configuration so that the storm control level is set to 80% of the interface bandwidth, or higher. If this does not resolve the issue, then try disabling the traffic for this interface.