IBM HS20 Hardware Maintenance Manual - Page 30

Diagnostic tools overview, USE THE FOLLOWING PROCEDULE TO CHECKOUT THE SERVER.

Get IBM HS20 - BladeCenter - 8832 PDF manuals and user guides
UPC - 087944983033
View all IBM HS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

001 USE THE FOLLOWING PROCEDULE TO CHECKOUT THE SERVER. 1. Turn off the server and all external devices, if attached. 2. Check all cables and power cords. 3. Set all display controls to the middle position. 4. Turn on all external devices. 5. Turn on the server. 6. Record any POST error messages that are displayed on the screen. If an error is displayed, look up the first error in the "POST error codes" on page 71. 7. Check the information LED panel Blade-error LED; if it is on, see "Light path diagnostics" on page 24. 8. Check the system-error log. If an error was recorded by the system, see Chapter 8, "Symptom-to-FRU index," on page 65. 9. Start the diagnostic programs. 10. Check for the following responses: v One beep. v Readable instructions or the main menu. 002 DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES? NO. Find the failure symptom in Chapter 8, "Symptom-to-FRU index," on page 65. YES. Run the diagnostic programs. If necessary, see "Diagnostic programs and error messages" on page 21. If you receive an error, see Chapter 8, "Symptom-to-FRU index," on page 65. If the diagnostic programs were completed successfully and you still suspect a problem, see "Undetermined problems" on page 90. Diagnostic tools overview The following tools are available to help you identify and solve hardware-related problems: v POST beep codes The power-on self-test (POST) beep codes indicate the detection of a problem. - One beep indicates successful completion of POST. - More than one beep indicates that POST detected a problem. Error messages also appear during startup if POST detects a hardware-configuration problem. See "Beep symptoms" on page 65 for more information. v Error symptom charts These charts list problem symptoms and steps to correct the problems. See "Error symptoms" on page 77 for more information. v Diagnostic programs and error messages The system diagnostic programs are provided in ROM. These programs (see "Diagnostic programs and error messages" on page 21) test the major components of the blade server. v Light path diagnostics feature Use the light path diagnostics feature to identify system errors quickly. See the "Light path diagnostics" on page 24 for more information. 20 BladeCenter HS20 Type 8832: Hardware Maintenance Manual and Troubleshooting Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
±001²
USE THE FOLLOWING PROCEDULE TO CHECKOUT THE SERVER.
1.
Turn off the server and all external devices, if attached.
2.
Check all cables and power cords.
3.
Set all display controls to the middle position.
4.
Turn on all external devices.
5.
Turn on the server.
6.
Record any POST error messages that are displayed on the screen. If
an error is displayed, look up the first error in the “POST error codes”
on page 71.
7.
Check the information LED panel Blade-error LED; if it is on, see
“Light path diagnostics” on page 24.
8.
Check the system-error log. If an error was recorded by the system,
see Chapter 8, “Symptom-to-FRU index,” on page 65.
9.
Start the diagnostic programs.
10.
Check for the following responses:
v
One beep.
v
Readable instructions or the main menu.
±002²
DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?
NO.
Find the failure symptom in Chapter 8, “Symptom-to-FRU index,” on
page 65.
YES.
Run the diagnostic programs. If necessary, see “Diagnostic programs
and error messages” on page 21.
If you receive an error, see Chapter 8, “Symptom-to-FRU index,” on page
65.
If the diagnostic programs were completed successfully and you still
suspect a problem, see “Undetermined problems” on page 90.
Diagnostic tools overview
The following tools are available to help you identify and solve hardware-related
problems:
v
POST beep codes
The power-on self-test (POST) beep codes indicate the detection of a problem.
–
One beep indicates successful completion of POST.
–
More than one beep indicates that POST detected a problem. Error messages
also appear during startup if POST detects a hardware-configuration problem.
See “Beep symptoms” on page 65 for more information.
v
Error symptom charts
These charts list problem symptoms and steps to correct the problems. See
“Error symptoms” on page 77 for more information.
v
Diagnostic programs and error messages
The system diagnostic programs are provided in ROM. These programs (see
“Diagnostic programs and error messages” on page 21) test the major
components of the blade server.
v
Light path diagnostics feature
Use the light path diagnostics feature to identify system errors quickly. See the
“Light path diagnostics” on page 24 for more information.
20
BladeCenter HS20 Type 8832: Hardware Maintenance Manual and Troubleshooting Guide