Blade(s) down for Cisco

Vendor

Cisco

Description

Indeni will alert one or more blades in a chassis is down.

Remediation Steps

Review the cause for the blades being down.

Most of the module related failures (such as the module not coming up, the module getting reloaded, and so on) can be analyzed by looking at the logs stored on the switch. Use the following CLI commands to identify the problem:

•show system reset-reason module

•show version

•show logging

•show module internal exception-log

•show module internal event-history module

•show module internal event-history errors

•show platform internal event-history errors

•show platform internal event-history module

Further details can be found to the next CISCO troubleshooting guide:

https://www.cisco.com/en/US/products/ps5989/prod_troubleshooting_guide_chapter09186a008067a0ef.html

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the modules state by using the "show module" command.

Why is this important?

This script logs into the Cisco Nexus switch using SSH and retrieves the modules state by using the "show module" command.

Without Indeni how would you find this?

The administrator has to poll the data and monitor the state the modules manually.


View Source Code