Configure Link Flap Prevention on a Cisco Business Switch using CLI

Objective

Link flap is a situation in which a physical interface on the switch continually goes up and down, three or more times a second for duration of at least 10 seconds. The common cause is usually related to bad, unsupported, or non-standard cable or Form-Factor Pluggable (SFP), or related to other link synchronization issues. The cause for link flapping can be intermittent or permanent.

Link flap prevention mechanism minimizes the disruption to switch and network operation in a link flap situation. It stabilizes the network topology by automatically setting the ports that experience excessive link flap events to err-disable state ports. This mechanism also provides time to debug and locate root cause for flapping. A syslog message or Simple Network Management Protocol (SNMP) trap is sent to alert regarding link flap and port shutdown. The interface will become active again only if specifically enabled by the system administrator.

This article provides instructions on how to enable the Link Flap Prevention feature, configure Automatic ErrDisable Recovery settings, and reactivate a suspended interface through the Command Line Interface (CLI) of the switch.

Applicable Devices | Software Version

• CBS250 (Data Sheet) | 3.1.0.57 (Download latest)
• CBS350 (Data Sheet) | 3.1.0.57 (Download latest)
• CBS350-2X (Data Sheet) | 3.1.0.57 (Download latest)
• CBS350-4X (Data Sheet) | 3.1.0.57 (Download latest)

Configure Link Flap Prevention Settings

Enable Link Flap Prevention

Step 1

Log in to the switch console. The default username and password is cisco/cisco. If you have configured a new username or password, enter the credentials instead.

To learn how to access a Cisco Business Switch CLI through SSH or Telnet, click here.

Step 2

From the Privileged EXEC mode of the switch, enter the Global Configuration mode by entering the following:

CBS350#configure

Step 3

To globally enable setting a physical interface to err-disable state due to excessive link flapping, enter the following:

CBS350(config)#link-flap prevention [enable | disable]

Step 4

(Optional) To disable link flap prevention on the switch, enter the following:

CBS350(config)#no link-flap prevention

Step 5

(Optional) To enable jumbo frames on the switch, enter the following:

CBS350(config)#port jumbo-frame

You have now successfully configured the Link Flap Prevention settings on your switch through the CLI.

Configure Automatic ErrDisable Recovery Settings

To enable the function of automatically reactivating a port that has been shut down because of an error condition after the Automatic Recovery Interval has passed, follow these steps:

Step 1

In the Global Configuration mode, enter the Interface Configuration context by entering the following:

CBS350(config)#errdisable recovery cause link-flapping

• link-flapping - Enables the error recovery mechanism for the link-flap prevention Err-Disable state.

Step 2

To set the error recovery timeout interval of the errdisable recovery, enter the following:

CBS350(config)#errdisable recovery interval [seconds]

• seconds - Specifies the error recovery timeout interval in seconds. The range is from 30 to 86400 seconds. The default value is 300 seconds.

Step 3

Enter the exit command to go back to the Privileged EXEC mode:

CBS350(config)#exit

You have now successfully configured the automatic errdisable recovery settings on your switch through the CLI.

Reactivate a Suspended Interface

To manually reactivate an interface that was shut down, follow the steps:

Step 1

To activate an interface that was configured to be active but was shut down by the system, enter the following:

CBS350#set interface active [interface-id]

Step 2

(Optional) In the Privileged EXEC mode of the switch, save the configured settings to the startup configuration file by entering the following:

CBS350#copy running-config startup-config

Step 3

(Optional) Press Y for Yes or N for No on your keyboard once the Overwrite file [startup-config].... prompt appears.

You have now successfully reactivated a suspended interface on your switch through the CLI.

Revision History

Revision	Publish Date	Comments
1.0	15-Jul-2020	Initial Release