IBM HS20 Hardware Maintenance Manual - Page 33

Viewing the test log, Diagnostic error message tables, Error symptoms, Next Cat, Prev Cat

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 33 highlights

c. If you run the diagnostic programs with either no mouse or a mouse attached 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 Cat and Prev Cat buttons. All other functions provided by mouse-selectable buttons 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 the top of the screen. If the diagnostic programs do not detect any hardware errors but the problem persists during normal server operations, a software error might be the cause. If you suspect a software problem, see the information that comes with the software package. Viewing the test log When the tests are completed, you can view the test log by selecting Utility from the 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. When you exit the diagnostic programs, the test log is cleared (saved test logs are not affected). To save the test log so that you can view it later, click Save Log on the diagnostic programs screen and specify a location and name for the saved log file. 2. To save the test log to a diskette, you must use a diskette that you have formatted yourself; this function does not work with preformatted diskettes. If the diskette has sufficient space for the test log, the diskette may contain other data. Diagnostic error message tables For descriptions of the error messages that might appear when you run the diagnostic programs, see "Diagnostic error codes" on page 68. Notes: 1. Depending on the server configuration, some of these error messages might not appear when you run the diagnostic programs. 2. If diagnostic error messages appear that are not listed in the error message tables, make sure that the server has the latest levels of BIOS, service processor, and diagnostics microcode installed. Error symptoms This section describes methods for troubleshooting other error symptoms. Error symptom charts You can use the error symptom charts to find solutions to problems that have definite symptoms (see "Error symptoms" on page 77). If you cannot find the problem in the error symptom charts, go to "Starting the diagnostic programs" on page 22 to test the blade server. Chapter 4. Diagnostics 23

  • 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
c.
If you run the diagnostic programs with either no mouse or a mouse
attached 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 Cat
and
Prev Cat
buttons. All other functions provided by mouse-selectable
buttons 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 the
top of the screen.
If the diagnostic programs do not detect any hardware errors but the problem
persists during normal server operations, a software error might be the cause. If
you suspect a software problem, see the information that comes with the software
package.
Viewing the test log
When the tests are completed, you can view the test log by selecting
Utility
from
the 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. When
you exit the diagnostic programs, the test log is cleared (saved test logs are not
affected). To save the test log so that you can view it later, click
Save Log
on
the diagnostic programs screen and specify a location and name for the saved
log file.
2.
To save the test log to a diskette, you must use a diskette that you have
formatted yourself; this function does not work with preformatted diskettes. If the
diskette has sufficient space for the test log, the diskette may contain other
data.
Diagnostic error message tables
For descriptions of the error messages that might appear when you run the
diagnostic programs, see “Diagnostic error codes” on page 68.
Notes:
1.
Depending on the server configuration, some of these error messages might not
appear when you run the diagnostic programs.
2.
If diagnostic error messages appear that are not listed in the error message
tables, make sure that the server has the latest levels of BIOS, service
processor, and diagnostics microcode installed.
Error symptoms
This section describes methods for troubleshooting other error symptoms.
Error symptom charts
You can use the error symptom charts to find solutions to problems that have
definite symptoms (see “Error symptoms” on page 77).
If you cannot find the problem in the error symptom charts, go to “Starting the
diagnostic programs” on page 22 to test the blade server.
Chapter 4. Diagnostics
23