Cisco MDS-9124 Troubleshooting Guide - Page 119

Chapter 4 Troubleshooting Hardware Troubleshooting Switching and Services Modules Send documentation comments to [email protected] • 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 Module Bootup When a module is inserted into the switch, the supervisor puts the module in powered-up state. In this state, the supervisor waits for the module to boot and send its identification to the active supervisor. If the supervisor does not receive the registration from the module within a given time frame, it power cycles the module. This failure is called a boot-up failure. The failure codes for boot-up failure can be obtained using the show platform internal event-history errors CLI command. (See Example 4-15.) Example 4-15 Finding Boot-Up Failure Codes switch# show platform internal event-history errors The following error codes are defined No Boot Device = 0xF1 Boot Failed = 0xC0 Net Boot Failed = 0xD0 Unknown Status = 0x1B Image Download Once the supervisor receives the registration message, it checks the image compatibility matrix. The image compatibility determines whether or not the version of code running on the supervisor is compatible with the version of code running on the module. If the versions do not match, the module downloads an updated version of the code, reboots, and sends a registration message again with the updated parameters. If the module is unable to download the code, the supervisor generates the following system message: Error Message MODULE-2-MOD_DNLD_FAIL: Image download failed for module [dec]. Explanation The module failed to download a new image from the supervisor module. Recommended Action Collect module information by entering the show module internal all module command. OL-9285-05 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 4-23