Owners Manual

Troubleshooting Fan Modules

NOTE: The fan modules are hot swappable. Remove and replace only one fan module at a time in a system that is turned

on. Operating the system without all six fan modules for extended periods of time can cause the system to overheat.

1. Locate the faulty fan. Each fan module has indicators that identify a faulty fan.

2. Remove the fan module.

3. Examine the blades for debris. If debris is present, carefully remove it.

4. Reseat the faulty fan.

5. If none of the fans show a fault LED and the blades do not power on, check the LCD display or CMC for status messages.

6. If the problem is not resolved, install a new fan.

7. If the new fan does not operate, see Getting Help.

Troubleshooting The iKVM Module

When using iDRAC video\console redirection, and you cannot see video through the iKVM when you switch to a blade running Linux, a

typical cause is that a monitor or KVM appliance with a lower resolution has recently been added.

For example, a blade running X Windows under Linux is inserted and powered on. A user connects to the blade in OS GUI mode using the

iDRAC and a video resolution is detected and hard-set for that session. A monitor or KVM appliance is attached to the front or rear iKVM

interface on the M1000e enclosure. The monitor or the KVM appliance is configured with a resolution LOWER than the currently

configured resolution in the X-Window session on the Linux blade. When you select the Linux blade using the front or rear port on the

iKVM, the iDRAC circuit adopts the lower resolution of the external connected devices. The video on the lower resolution monitor or the

KVM appliance is not displayed until X Windows is restarted (iDRAC video should still be viewable.)

1. From the iDRAC session, exit and re-enter GUI mode. The lower resolution is communicated and utilized.

2. Set all monitors or KVM appliances connected to the M1000e enclosure to the same resolution or higher as configured on the Linux

blades in GUI mode.

3. From the lower resolution monitor (no video displayed) press <CTRL><ALT><F3> to change to the non-GUI login screen.

4. Restart X Windows to detect and utilize the lower resolution.

Troubleshooting I/O Modules

NOTE:

To eliminate the possibility of a hardware problem with the module or its attaching devices, first ensure that the

module is properly initialized and configured.

1. Check that you have installed the module in an I/O slot that matches its fabric type.

2. Check that the pass-through module or switch ports are cabled correctly. A given mezzanine card in a full-height blade connects to

two I/O ports on the two associated I/O modules.

3. Using the "17th blade" feature of the CMC, use the Connect Switch-X command to verify that the switch is fully booted, and verify

the switch’s firmware revision and IP address.

4. Verify that the switch module has a valid IP address for the subnet. Verify using the ICMP ping command.

5. Check the network connector indicators on the network switch module:

• If the link indicator displays an error condition, check all cable connections.

• Try another connector on the external switch or hub.

• If the activity indicator does not light, replace the network switch module.

6. Using the switch management interface, verify the switch port properties. If the switch is configured correctly, back up the switch

configuration and replace the switch. See the switch module documentation for details.

7. If the blade requires a mezzanine card for a particular network switch module, ensure that the appropriate mezzanine card is installed.

If so, reseat the mezzanine card. If the network link indicator on the blade is green, then the blade has a valid link to the appropriate

network switch module.

8. Ensure that the appropriate operating system drivers are installed and that the protocol settings are configured to ensure proper

communication.

Troubleshooting The Enclosure