Filter
Top Products
Table 2. Troubleshooting charts
Device Suggested action
Blade server problem
Blade servers turn off for no
apparent reason.
All blade bays must have a blade server, expansion unit, or filler blade in them. Blade
bays that do not have these items installed or have them installed improperly disturb
airflow in the BladeCenter unit with an adverse effect on BladeCenter unit cooling. If
the BladeCenter unit begins to overheat, blade server processors will begin to slow
down and will eventually turn off the system.
Blade server does not turn off
during Red Hat Linux 7.3
shutdown.
Issuing any of the Linux shutdown commands shuts down the operating system, but
does not turn off the blade server. The blade server shuts down to the point where a
message is displayed on the management module saying that the blade server is off,
but the blade server power-on LED remains lit.
Complete the instructions provided for Red Hat Linux in the User's Guide or the
Command-Line Interface Reference Guide for your management module type to
enable Wake On LAN for both onboard Broadcom integrated Ethernet controllers.
This will allow the blade server to restart using Wake on LAN even if the Linux
shutdown is incomplete and the blade server does not turn off.
Forcing a blade server to turn off
Complete the following steps to turn off a blade server after an incomplete Linux
shutdown:
1. Manually press the power-control button on the front of the blade server (behind
the control panel door) to turn off the blade server. Turning off the blade server in
this way is considered an improper shutdown by the Wake on LAN feature, and
the Wake on LAN feature will not restart the blade server.
2. Unlatch and slide the blade server partially out of the BladeCenter; then, reinstall
it to reset the blade server power state and re-enable its previously programmed
Wake on LAN capability.
Blade server does not turn off
during SuSE Linux 8.0
shutdown.
Issuing any of the Linux shutdown commands shuts down the operating system but
does not turn off the blade server. The blade server shuts down to the point where a
message is displayed on the management module saying that the blade server is off,
but the blade server power-on LED remains lit.
A blade server running SuSE Linux 8.0 will not turn off during shutdown if ACPI is not
enabled. Complete the following steps to enable ACPI:
1. Type the following command: modprobe ospm_system
2. Type the following command to save this setting upon subsequent reboots: echo
"/sbin/modprobe ospm_system" >> /etc/init.d/boot.local
Blade server does not turn
on, the amber system-error
LED on the BladeCenter
system-LED panel is lit, the
amber blade error LED on the
blade server LED panel is lit,
and the system-error log
contains the following
message: "CRUs
MisMatched".
The problem occurs after installing the second microprocessor option or after
replacing a failed microprocessor in a two-way Blade server.
The processor with the lowest feature set and stepping level must be used as the
Bootstrap Processor (BSP). This is Microprocessor 1 in location U66. Move the
microprocessor in location U66 to location U70, and move the microprocessor in
location U70 to location U66.
60 BladeCenter E Type 8677 and 1881: Hardware Maintenance Manual and Troubleshooting Guide