Isolating component failures

There are times when the only way to isolate the cause of a problem is to start removing components until the problem is resolved. Use this procedure to assist in isolating the root cause of a problem.

Problem

You are having problems with the BladeCenter S system, but you are unable to isolate the problem to a single component.

Note: Before you begin attempting to isolate problems to a specific component, you should first view the advanced management module and attempt to resolve any problems that are found.

To view the event log:

From the advanced management module Web interface, click Monitors > Event log .
For information about the advanced management module Web interface, see the Advanced Management Module User's Guide.
From the advanced management module command-line interface, enter the displaylog command.
For information about the advanced management module command-line interface, see the Advanced Management Module Command-Line Interface Reference Guide.

Investigation

Perform these steps to isolate problems to a specific component:

Power down and disengage all blade servers from the BladeCenter S chassis midplane. Open the release handles and the blade servers will slide out of the bay approximately one inch.
Make sure there is a working power supply in power module bay 1 and disengage power supplies 2, 3, and 4 (pull them out approximately one inch.
Disengage the following components from the midplane:
1. Open the release handles on all I/O modules.
  Important: Disengaging an I/O module will disrupt communications with any external devices that are attached to that I/O module. Make sure that all external devices are powered down before disengaging an I/O module.
2. Open the release handles on the disk storage modules.
  Note: Make sure that all drive activity is stopped (the green LED on the hard disk drive is not blinking) before removing the disk storage module.
Note: If you disengage or remove all devices from the front of the BladeCenter S chassis (media tray, blade servers, and disk storage modules), the power modules will be disabled.
Verify that the ac and dc LEDs are lit for power module 1. If not, see Troubleshooting power problems.
Verify that the advanced management module is working. If not, see Troubleshooting advanced management module problems.
1. Log in to the advanced management module and check the System Status page for any problems.
2. Verify that the power supply is displayed in advanced management module Power Management page.
3. Check the event log for new error messages and resolve any errors that you find. You can ignore messages related to non-redundant modules because components have been removed from the BladeCenter S chassis.
Plug in power supply 2 and verify that the ac and dc LEDs are lit.
Log in to the advanced management module and verify that the power supply is displayed in the advanced management module Power Management page. If so, remove power supply 1.
If you still do not have a minimum configuration that works, contact IBM® Support.
Bring up a blade server by reengaging the blade server and starting it. Choose a blade server that does not require the disk storage modules to boot.
1. Install a blade server in blade server bay 1. Power it up and use the local KVM connection to ensure that it completes POST and starts the operating system.
  - If you do not see any video display while the blade is starting, see Troubleshooting monitor or video problems
  - If the blade server fails with a POST error message or checkpoint code, see the documentation for that blade server.
  - If the blade server starts, but the keyboard or mouse does not work, try a different blade server.
    - If the keyboard or mouse only fails for one blade server, suspect that blade server.
    - If the keyboard or mouse fails for multiple blade servers, suspect the advanced management module. Verify the firmware level of the advanced management module and replace the advanced management module if necessary.
2. Start the blade server on-board diagnostics (press F2 during POST and run diagnostics). If any errors are returned, see Troubleshooting blade server problems.
  Note: For more information about on-board diagnostics and troubleshooting a blade server, see the blade server troubleshooting procedures provided in blade server documentation.
Install the Ethernet switch module in I/O module bay 1 and connect it to the network. Check the advanced management module system status to ensure that it completes POST with no errors in the advanced management module System Status page or the event log.
You should now have a working BladeCenter S system that contains the advanced management module, one blade server, one I/O module, one power supply, the media tray, and the fan modules. Begin installing components back into the BladeCenter S chassis, one at a time, until you see the failure symptom again. Start with the power supplies, then the other I/O modules, and then the blade servers.
If the failure symptom returns after replacing a module or blade server, contact IBM Support for additional resolution procedures.