IBM HS20 Hardware Maintenance Manual - Page 29

Diagnostics, General checkout - upgrade

Page 29 highlights

Chapter 4. Diagnostics This section provides basic troubleshooting information to help you solve some common problems that might occur with the blade server. If you cannot locate and correct the problem using the information in this section, see Appendix A, "Getting help and technical assistance," on page 95 for more information. General checkout The server diagnostic programs are stored in the upgradeable read-only memory (ROM). These programs test the major components of the blade server. The diagnostics can be downloaded from http://www.ibm.com/pc/support/. If you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly. When you run the diagnostic programs, a single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After the cause of the first error message is corrected, the other error messages might not occur the next time you run the test. Notes: 1. If multiple error codes are displayed, diagnose the first error code that is displayed. 2. If the server stops with a POST error, go to "POST error codes" on page 71. 3. If the blade server stops and no error is displayed, go to "Undetermined problems" on page 90. 4. For safety information, see Appendix B, "Safety information," on page 97. 5. For intermittent problems, check the error log. 6. If blade front panel shows no LEDs, verify blade status and errors in BladeCenter web interface; also see "Undetermined problems" on page 90. 7. If device errors occur, see "Error symptoms" on page 77. © Copyright IBM Corp. 2003 19

  • 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

Chapter 4. Diagnostics
This section provides basic troubleshooting information to help you solve some
common problems that might occur with the blade server.
If you cannot locate and correct the problem using the information in this section,
see Appendix A, “Getting help and technical assistance,” on page 95 for more
information.
General checkout
The server diagnostic programs are stored in the upgradeable read-only memory
(ROM). These programs test the major components of the blade server. The
diagnostics can be downloaded from http://www.ibm.com/pc/support/.
If you cannot determine whether a problem is caused by the hardware or by the
software, you can run the diagnostic programs to confirm that the hardware is
working properly.
When you run the diagnostic programs, a single problem might cause several error
messages. When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages
might not occur the next time you run the test.
Notes:
1.
If multiple error codes are displayed, diagnose the first error code that is
displayed.
2.
If the server stops with a POST error, go to “POST error codes” on page 71.
3.
If the blade server stops and no error is displayed, go to “Undetermined
problems” on page 90.
4.
For safety information, see Appendix B, “Safety information,” on page 97.
5.
For intermittent problems, check the error log.
6.
If blade front panel shows no LEDs, verify blade status and errors in
BladeCenter web interface; also see “Undetermined problems” on page 90.
7.
If device errors occur, see “Error symptoms” on page 77.
© Copyright IBM Corp. 2003
19