IBM BladeCenter HS20 Type 8832 Maintenance And Troubleshooting Manual

Also see for eServer BladeCenter HS20 Type 8832: Setup guide Installation and user guide Problem determination and service guide

Contents

c. If you run the diagnostic programs with either no mouse or a mouseattached to the BladeCenter unit that is not controlled by the blade server,you will not be able to navigate between test categories using the Next Catand Prev Cat buttons. All other functions provided by mouse-selectablebuttons are also available using the function keys.d. You can view server configuration information (such as system configuration,memory contents, and device drivers) by selecting Hardware Info from thetop of the screen.If the diagnostic programs do not detect any hardware errors but the problempersists during normal server operations, a software error might be the cause. Ifyou suspect a software problem, see the information that comes with the softwarepackage.Viewing the test logWhen the tests are completed, you can view the test log by selecting Utility fromthe top of the screen and then selecting View Test Log.Notes:1. You can view the test log only while you are in the diagnostic programs. Whenyou exit the diagnostic programs, the test log is cleared (saved test logs are notaffected). To save the test log so that you can view it later, click Save Log onthe diagnostic programs screen and specify a location and name for the savedlog file.2. To save the test log to a diskette, you must use a diskette that you haveformatted yourself; this function does not work with preformatted diskettes. If thediskette has sufficient space for the test log, the diskette may contain otherdata.Diagnostic error message tablesFor descriptions of the error messages that might appear when you run thediagnostic programs, see “Diagnostic error codes” on page 68.Notes:1. Depending on the server configuration, some of these error messages might notappear when you run the diagnostic programs.2. If diagnostic error messages appear that are not listed in the error messagetables, make sure that the server has the latest levels of BIOS, serviceprocessor, and diagnostics microcode installed.Error symptomsThis section describes methods for troubleshooting other error symptoms.Error symptom chartsYou can use the error symptom charts to find solutions to problems that havedefinite symptoms (see “Error symptoms” on page 77).If you cannot find the problem in the error symptom charts, go to “Starting thediagnostic programs” on page 22 to test the blade server.Chapter 4. Diagnostics 23