Nx boot failure
Configuration changes, such as added devices or adapter firmware updates, and firmware or application
code problems can cause the server to fail POST (the power-on self-test). If this occurs, the server responds
in either of the following ways:
• The server restarts automatically and attempts POST again.
• The server hangs, and you must manually restart the server for the server to attempt POST again.
After a specified number of consecutive attempts (automatic or manual), the Nx boot failure feature causes
the server to revert to the default UEFI configuration and start the Setup utility so that you can make the
necessary corrections to the configuration and restart the server. If the server is unable to successfully
complete POST with the default configuration, there might be a problem with the system board.
To specify the number of consecutive restart attempts that will trigger the Nx boot failure feature, perform the
following steps:
Step 1. In the Setup utility, click
System Settings
➙
Recovery
➙
POST Attempts
➙
POST Attempts
Limit
.
Step 2. The available options are 3, 6, 9, and 255 (disable Nx boot failure). Select your option.
Service processor (IMM) error codes
Use this information to view the IMM error log.
The Integrated Management Module (IMM) log contains up to 512 of the most recent service processor
errors, in IPMI format. These messages are a combination of plain text and error-code numbers. You can
view the IMM log from the Setup utility menu by selecting
Advanced Setup
→
Integrated Management
Module (IMM) Settings
→
IMM System Event Log
.
You can view additional information and error codes in plain text by viewing the Advanced-Management-
Module event log in your BladeCenter unit.
Solving SAS hard disk drive problems
Use this information to diagnose and resolve SAS hard disk drive issues.
For any SAS error message, one or more of the following devices might be causing the problem:
• A failing SAS device (adapter, drive, or controller)
• An incorrect SAS configuration
For any SAS error message, make sure that the SAS devices are configured correctly.
Solving shared BladeCenter resource problems
Use this information to diagnose and resolve shared BladeCenter resource issues.
Problems with BladeCenter shared resources might appear to be in the blade server. The following sections
provide procedures to help you isolate blade server problems from shared BladeCenter resource problems. If
the problem is thought to be with a shared resource, see the
Problem Determination and Service Guide
for
your BladeCenter unit and other BladeCenter component documentation for additional information. If the
problem cannot be solved, see “Solving undetermined problems” on page 262.
258
BladeCenter HS23 Blade ServerProblem Determination and Service Guide
Summary of Contents for BladeCenter HS23 1929
Page 1: ...BladeCenter HS23 Blade Server Problem Determination and Service Guide Machine Types 7875 1929 ...
Page 284: ...268 BladeCenter HS23 Blade ServerProblem Determination and Service Guide ...
Page 289: ...Taiwan BSMI RoHS declaration Appendix B Notices 273 ...
Page 290: ...274 BladeCenter HS23 Blade ServerProblem Determination and Service Guide ...
Page 296: ...280 BladeCenter HS23 Blade ServerProblem Determination and Service Guide ...
Page 297: ......
Page 298: ...Part Number 00KC215 Printed in China 1P P N 00KC215 ...
Page 299: ... 1P00KC215 ...
