This article explains the steps to be taken when interface goes physically down due to the storm control being in effect.
Below logs are seen during the issue time:
mib2d[18395]: SNMP_TRAP_LINK_DOWN: ifIndex 777, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-2/0/42
mib2d[18395]: SNMP_TRAP_LINK_UP: ifIndex 777, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-2/0/42
l2ald[18397]: L2ALD_ST_CTL_IN_EFFECT: ge-2/0/42.0: storm control in effect on the port
l2ald[18397]: L2ALD_ST_CTL_DISABLED: ge-2/0/42.0: storm control disabled port
ge-2/0/42 {
unit 0 {
family ethernet-switching {
interface-mode access;
vlan {
members TVI-GREEN2;
}
storm-control TVI-STORM;
forwarding-options {
storm-control-profiles TVI-STORM {
all {
bandwidth-percentage 1;
action-shutdown;
storm-control-profiles default {
all;
As per the interface configuration we see that the interface is configured under storm control and has an action to shut down the port if the bandwidth is exceeded.
As per the var logs I see that the port was disabled due to the storm control.
If you configure the action-shutdown statement without configuring either the port-error-disable or recovery-timeout statement, the interfaces that are enabled for storm control are shut down when the storm control level is exceeded, and they do not recover automatically from that port-error condition.
If you do not configure the switch for auto recovery from the disabled condition, you can bring up the disabled interfaces by running one of the following commands:
>clear ethernet-switching recovery-timeout
Below command can be configured for auto-recovery:
#set interfaces ge-2/0/42 unit 0 family ethernet-switching recovery-timeout 10
If you enable storm control with the action-shutdown option and you enable recovery-timeout, the interface is temporarily disabled when applicable traffic exceeds the specified levels. Depending upon the configuration, applicable traffic can include broadcast, unknown unicast, and multicast traffic.
2025-02-10 : Article Created
2025-02-17 : Article Validated
https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/recovery-timeout-edit-interfaces.html