Send documentation comments to mdsfeedback-doc@cisco.com
4-24
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 4 Troubleshooting Hardware
Troubleshooting Switching and Services Modules
In addition, the module generates a system message indicating the exact reason why the image download
failed:
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_FAILED: Module image download
process failed. [chars].
Explanation
The add-on image download to the module failed. This module is not operational until
an add-on image has been successfully installed.
Recommended Action Verify the location and version of your module image. Enter install module
CLI command or similar Fabric Manager/Device Manager command to download a new module
image.
If the image download fails, the supervisor power cycles the module. Choose Logs > Switch Resident
> Syslog > Since Reboot in Device Manager or use the show logging CLI command to view the failure
messages.
Runtime Diagnostics
After the module successfully registers with the supervisor, the module checks the hardware. If this fails,
the module reports the error to the supervisor and generates the following system message:
Error Message MODULE-2-MOD_DIAG_FAIL: Module [dec] reported failure on ports
[dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (device error
[hex]).
Explanation
The module reported a failure in the runtime diagnostic. Module manager is going to
power cycle the module.
Recommended Action Collect information about the module by entering the show module internal
all module CLI command.
In addition, this information is stored in the exception log (which is persistent across reboots). The
supervisor then power cycles the module. Choose Logs > Switch Resident > Syslog > Since Reboot in
Device Manager or use the show logging and show module internal exception-log module CLI
commands to retrieve failure information.
Runtime Configuration
After the runtime diagnostics complete successfully, the module informs the supervisor that it is ready
for configuration. Individual supervisor components configure the module. If any component reports a
problem during this stage, the supervisor reboots the module. Use the show module internal
event-history module CLI command to determine which component reported the problem.
Online and Operational
After all the supervisor components have configured the module, the module goes to the ok state. In this
state, the module is online and operational. The supervisor continues to monitor the module periodically
to verify correct operation. The following events are monitored:
• Heartbeat message—Sent between the supervisor and the module to verify that the module is
running.
To Next Page
Loading...
Need help?
General