Owner's Manual

Troubleshooting and Recovery 437
When you type recover and then press <Enter> at the recovery prompt,
the recover reason and available sub-commands display. An example recover
sequence may be:
recover getniccfg
recover setniccfg 192.168.0.120 255.255.255.0
192.168.0.1
recover ping 192.168.0.100
recover fwupdate -g -a 192.168.0.100
NOTE: Connect the network cable to the left most RJ45
NOTE: In recover mode, you cannot ping CMC normally because there is no active
network stack. The recover ping <
TFTP server IP > command allows you to ping to
the TFTP server to verify the LAN connection. You may need to use the recover
reset command after setniccfg on some systems.
Troubleshooting Network Problems
The internal CMC trace log allows you to debug CMC alerting and
networking. You can access the trace log using the CMC Web interface
(see "Using the Diagnostic Console") or RACADM (see "Using the RACADM
Command Line Interface" and the gettracelog command section in the
RACADM Command Line Reference Guide for iDRAC6 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.