Skip to main content

Troubleshooting blade server problems

Use this information to resolve problems with a blade server.

IBM continually updates the support Web site with tips and techniques that you can use to resolve any problems that you may be having with the BladeCenter S system. Go to the BladeCenter support search Web site and search for the terms 8886, retain, and blade to see if any service bulletins have been generated.

Note
For more information about blade servers, see the blade server documentation. To determine which blade servers are compatible with the BladeCenter S chassis, see the IBM ServerProven Web site.
In addition:
  • Blade server cannot communicate with external network
    If a blade server cannot communicate with the external network, there may be an I/O connectivity problem.
  • Blade server will not power on
    If a blade server will not power on, the problem may be caused by the blade itself, power supplies, or by configuration settings within the advanced management module.
  • I-error messages displayed for an Intel-based blade server
    I-error messages are displayed in the advanced management module event log. Use this procedure to resolve problems that cause I-error messages.
  • I-error messages displayed for an AMD-based blade server
    I-error messages are displayed in the advanced management module event log. Use this procedure to resolve problems that cause I-error messages with Opteron-based blade servers.
  • Kernel mode displayed for blade server
    The advanced management module Web interface will display kernel mode on the vital product data (VPD) panel for a blade server when the advanced management module is able to communicate with the service processor on the blade server, but the blade server firmware has a problem. This error will typically occur after updating the firmware for a blade server. In addition to the kernel mode error, the event log will typically display service processor communication errors for multiple blade servers in the BladeCenter S chassis.
  • No LEDs appear
    If LEDs are not lit for a blade server, the problem could be in the power supplies, the device itself, or the bay where the device is installed.
  • No VPD available from advanced management module
    Vital Product Data (VPD) for each blade server in the BladeCenter S chassis is available from the advanced management module interface. Use this procedure to troubleshooting the situation where VPD does not appear.
  • Power LED continually flashes rapidly
    A power LED that continually flashes rapidly for more than two minutes is an indication that the firmware in the advanced management module does not support this blade server or that there is a communications problem between the advanced management module and the blade server.
  • Service processor communication (SP COMM) errors displayed for a blade server
    When a blade server is installed in the BladeCenter S chassis, the advanced management module initiates communication with the service processor on the blade server. Disruptions in this communications results in service processor communication errors being logged in the advanced management module event log. These errors are typically caused by problems in firmware or configuration (either on the advanced management module or on the blade server).
  • Service processor communication error displayed for multiple blade servers
    When attempting to resolve service processor communication errors on multiple blade servers in a BladeCenter S chassis that has been functioning normally, you need to ensure that you have physical access to the BladeCenter S chassis.
  • Watchdog timeout messages displayed for a blade server
    Watchdog timeout messages are displayed in the advanced management module event log. Use this procedure if there are multiple blade servers in a BladeCenter S chassis and you are seeing these messages for only one of the blade servers.
  • Watchdog timeout messages displayed for multiple blade servers
    Watchdog timeout messages are displayed in the advanced management module event log. Use this procedure if you are seeing these messages for multiple blade servers in a BladeCenter S chassis.
Related concepts:
Related tasks: