Interface(s) in error-disable state for Cisco

Vendor

Cisco

Description

Interfaces can be put in err-disable state if certain errors are detected by the devices. Indeni will alert if this happens.

Remediation Steps

Review the causes why some interfaces were put in error-disable state.

1. Use the "show interface" and "show interface status err-disabled" NX-OS commands to identify the reason for the err-disable interface state.

2. View information about the internal state transitions of the port by using the "show system internal ethpm event-history interface X/X" NX-OS command.

3. Review the logs for relevant findings by running the "show logging" NX-OS command.

4. After fixing the issue, run the "shut/no shut" command on the port to re-enable it.

5. It is possible to enable automatic periodic err-disable recovery by using the "errdisable recovery cause" NX-OS configuration command. For more information please review the following CISCO NX-OS guide:

Enabling the Error-Disabled Detection.

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show interface" command. The output includes all the interface related information and statistics.

Why is this important?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show interface" command. The output includes all the interface related information and statistics.

Without Indeni how would you find this?

Error disabled interfaces would generate a syslog event. The user would have to login to the device and use the "show interface" command to identify the reason for the error disabled port.


View Source Code