Users Guide

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 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.
• Conguration changes to the network interfaces.
The trace log may also contain CMC rmware-specic error codes that are related to the internal CMC rmware, not the managed
system’s operating system.
General troubleshooting
When a success message is displayed after an operation completion, such as saving a Server Prole, sometimes the action may not
take eect.
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.
• Problem: Storage Amber LED blinks.
Resolution: Ensure that the storage module is inserted properly and check the chassis log for warning messages. This error can
be cleared only if the underlying fault is addressed and the associated host is power cycled with the sled removed or through a
sled virtual reseat.
Problem: Storage module RAID rmware update is not eective.
Resolution: When in split-dual host mode, each host that is connected to the storage sled RAID must be power cycled for the
RAID rmware change to be eective.
• Problem: PCIe slot reassignment option is disabled in the GUI.
Resolution: Ensure that all hosts in the chassis are powered on. If you attempt changing this setting from RACADM while a host
is powered on, an error message is displayed. The chassis conguration administrator privilege is required to change this setting.
• Problem: PCIe slot reassignment enabled and host is powered on, but the PCIe slots are not powered on.
Resolution: Check the Chassis Log for warning messages associated with outdated BIOS, iDRAC, or unsupported host.
149