IBM 867282X Maintenance Manual - Page 9

General checkout, Notes

Get IBM 867282X - Eserver xSeries 300 PDF manuals and user guides
UPC - 087944650966
View all IBM 867282X manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

Chapter 1. General checkout The server diagnostic programs are stored on CD-ROM. These programs are the primary method of testing the major components of the server: the system board, Ethernet controller, video controller, RAM, keyboard, mouse (pointing device), diskette drive, serial ports, and hard drives. You can also use them to test some external devices. See "Diagnostic programs and error messages" on page 12. Also, 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. A failed system might be part of a shared DASD cluster (two or more systems sharing the same external storage device(s)). Prior to running diagnostics, verify that the failing system is not part of a shared DASD cluster. A system might be part of a cluster if: v The customer identifies the system as part of a cluster. v One or more external storage units are attached to the system and at least one of the attached storage units is additionally attached to another system or unidentifiable source. v One or more systems are located near the failing system. If the failing system is suspected to be part of a shared DASD cluster, all diagnostic tests can be run except diagnostic tests which test the storage unit (DASD residing in the storage unit) or the storage adapter attached to the storage unit. Notes: 1. Safety information, see "Safety information" on page 75. 2. For systems that are part of a shared DASD cluster, run one test at a time in looped mode. Do not run all tests in looped mode, as this could enable the DASD diagnostic tests. 3. If multiple error codes are displayed, diagnose the first error code displayed. 4. If the computer hangs with a POST error, go to "POST error codes" on page 69. © Copyright IBM Corp. 2000 1

  • 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
Chapter 1. General checkout
The server diagnostic programs are stored on CD-ROM. These programs are the
primary method of testing the major components of the server: the system board,
Ethernet controller, video controller, RAM, keyboard, mouse (pointing device),
diskette drive, serial ports, and hard drives. You can also use them to test some
external devices. See
“
Diagnostic programs and error messages
”
on page 12.
Also, 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.
A failed system might be part of a shared DASD cluster (two or more systems
sharing the same external storage device(s)). Prior to running diagnostics, verify
that the failing system is not part of a shared DASD cluster.
A system might be part of a cluster if:
v
The customer identifies the system as part of a cluster.
v
One or more external storage units are attached to the system and at least one of
the attached storage units is additionally attached to another system or
unidentifiable source.
v
One or more systems are located near the failing system.
If the failing system is suspected to be part of a shared DASD cluster, all
diagnostic tests can be run except diagnostic tests which test the storage unit
(DASD residing in the storage unit) or the storage adapter attached to the storage
unit.
Notes:
1.
Safety information, see
“
Safety information
”
on page 75.
2.
For systems that are part of a shared DASD cluster, run one test at a time in
looped mode. Do not run all tests in looped mode, as this could enable the
DASD diagnostic tests.
3.
If multiple error codes are displayed, diagnose the first error code displayed.
4.
If the computer hangs with a POST error, go to
“
POST error codes
”
on page 69.
© Copyright IBM Corp. 2000
1