IBM 8685 Hardware Maintenance Manual - Page 168

Problem determination tips, If you suspect a networking problem and all the system tests pass

Get IBM 8685 - eServer xSeries 255 PDF manuals and user guides
UPC - 087944957171
View all IBM 8685 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 168 highlights

Notes: 1. Damaged data in CMOS can cause undetermined problems. 2. Damaged data in BIOS code can cause undetermined problems. Check the LEDs on all the power supplies. If the LEDs indicate the power supplies are working correctly, complete the following steps: 1. Turn off the server. 2. Be sure the server is cabled correctly. 3. Remove or disconnect the following devices (one at a time) until you find the failure (turn on the server and reconfigure each time): v Any external devices v Surge suppressor device (on the server) v Modem, printer, mouse, or non-IBM devices v Each adapter v Drives v Memory modules (minimum requirement = 256 MB (2 banks of 128 MB DIMMs)) Note: Minimum operating requirements are: a. One power supply b. Power backplane c. System board d. One microprocessor and VRM e. Memory module (with a minimum of two 128 MB DIMMs) 4. Turn on the server. If the problem remains, suspect the following FRUs in the order listed: v Power supply v Power backplane v System board Notes: 1. If the problem goes away when you remove an adapter from the system and replacing that adapter does not correct the problem, suspect the system board. 2. If you suspect a networking problem and all the system tests pass, suspect a network cabling problem external to the system. Problem determination tips Due to the variety of hardware and software combinations that can be encountered, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from Service Support and Engineering functions. v Machine type and model v Microprocessor or hard disk upgrades v Failure symptom - Do diagnostics fail? - What, when, where, single, or multiple systems? - Is the failure repeatable? - Has this configuration ever worked? - If it has been working, what changes were made prior to it failing? - Is this the original reported failure? v Diagnostics version - Type and version level 158 xSeries 255 Type 8685: 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
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
Notes:
1.
Damaged data in CMOS can cause undetermined problems.
2.
Damaged data in BIOS code can cause undetermined problems.
Check the LEDs on all the power supplies. If the LEDs indicate the power supplies
are working correctly, complete the following steps:
1.
Turn off the server.
2.
Be sure the server is cabled correctly.
3.
Remove or disconnect the following devices (one at a time) until you find the
failure (turn on the server and reconfigure each time):
v
Any external devices
v
Surge suppressor device (on the server)
v
Modem, printer, mouse, or non-IBM devices
v
Each adapter
v
Drives
v
Memory modules (minimum requirement = 256 MB (2 banks of 128 MB
DIMMs))
Note:
Minimum operating requirements are:
a.
One power supply
b.
Power backplane
c.
System board
d.
One microprocessor and VRM
e.
Memory module (with a minimum of two 128 MB DIMMs)
4.
Turn on the server. If the problem remains, suspect the following FRUs in the
order listed:
v
Power supply
v
Power backplane
v
System board
Notes:
1.
If the problem goes away when you remove an adapter from the system and
replacing that adapter does not correct the problem, suspect the system board.
2.
If you suspect a networking problem and all the system tests pass, suspect a
network cabling problem external to the system.
Problem determination tips
Due to the variety of hardware and software combinations that can be encountered,
use the following information to assist you in problem determination. If possible,
have this information available when requesting assistance from Service Support
and Engineering functions.
v
Machine type and model
v
Microprocessor or hard disk upgrades
v
Failure symptom
–
Do diagnostics fail?
–
What, when, where, single, or multiple systems?
–
Is the failure repeatable?
–
Has this configuration ever worked?
–
If it has been working, what changes were made prior to it failing?
–
Is this the original reported failure?
v
Diagnostics version
–
Type and version level
158
xSeries 255 Type 8685: Hardware Maintenance Manual and Troubleshooting Guide