Users Guide

Table 33. LED Color and Blinking Patterns (continued)
Component LED Color, Blinking Pattern Status
Amber, blinking Fault
Storage sled Amber, blinking Fault
Solid Blue No fault
Troubleshooting Non-responsive CMC
If you cannot log in to CMC using any of the interfaces (the web interface, Telnet, SSH, remote RACADM, or serial), you can verify the
CMC functionality observing the LEDs on CMC.
Observing LEDs to Isolate the Problem
The CMC has an LED which changes color to indicate:
Table 34. LED color indicators
Color Description
Blue Normal operation
Blue, blinking ID (0.5 second on, 0.5 second off)
Amber Chassis fault summary
Amber, blinking Chassis fault with concurrent ID
Troubleshooting Network Problems
The internal CMC trace log allows you to debug CMC alerts and networking. You can access the trace log using the CMC Web interface
or RACADM. See the gettracelog command section in the RACADM Command Line Reference Guide for iDRAC and CMC.
The trace log tracks the following information:
• DHCP — Traces packets sent to and received from a DHCP server.
• DDNS — Traces dynamic DNS update requests and responses.
• Configuration changes to the network interfaces.
The trace log may also contain CMC firmware-specific error codes that are related to the internal CMC firmware, not the managed
system’s operating system.
General troubleshooting
When a success message is displayed after an operation completion, such as saving a Server Profile, sometimes the action may not take
effect.
To resolve this issue, check if any of the CMC service ports for SSH, Telnet, HTTP, or HTTPS uses ports commonly used by OS services
such as 111. If it is used by CMC service ports, change the settings to a non-reserved port. For more information on reserved ports, see
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml
Troubleshooting storage module in FX2 chassis
The following information helps you to troubleshoot issues related to storage sleds in the FX2 chassis.
• Problem: Storage module is not detected on insertion. Storage module inserted and the associated server powered on, is not
detected
Resolution: . Ensure that the associated server is power cycled after the storage module is inserted.
• Problem: Storage module is inserted and the associated server is power cycled, but the storage module is not detected.
Resolution: Check the chassis log for more details about the failure. Verify if there is any hardware failure such as no detection of
cable spool or RAID.
152
Troubleshooting and recovery