IBM 8685 Hardware Maintenance Manual - Page 47

Power checkout, Troubleshooting the Ethernet controller, Network connection problems

Page 47 highlights

Power checkout Power problems can be difficult to solve. For example, a short circuit can exist anywhere on any of the power distribution buses. Usually a short circuit will cause the power subsystem to shut down because of an overcurrent condition. A general procedure for troubleshooting power problems is as follows: 1. Turn off the server and disconnect all ac power cords. 2. Check for loose cables in the power subsystem. Also check for short circuits, for example, if there is a loose screw causing a short circuit on a circuit board. 3. Remove adapters and disconnect the cables and power connectors to all internal and external devices until the server is at the minimum configuration required to start the server (see "Minimum operating requirements" on page 158). 4. Reconnect all ac power cords and turn on the server. If the server starts up successfully, replace adapters and devices one at a time until the problem is isolated. If the server does not start up from the minimal configuration, replace FRUs of minimal configuration one at a time until the problem is isolated. To use this method, it is important to know the minimum configuration required for a system to start (see page 158). For specific problems, see "Power-supply LED errors" on page 146. Troubleshooting the Ethernet controller This section provides troubleshooting information for problems that might occur with the 10/100/1000 Mbps Ethernet controller. Network connection problems If the Ethernet controller cannot connect to the network, check the following conditions: v Make sure that the cable is installed correctly. The network cable must be securely attached at all connections. If it does the cable is attached but the problem remains, try a different cable. If you set the Ethernet controller to operate at either 100 Mbps or 1000 Mbps, you must use Category 5 or higher cabling. v Determine whether the hub supports auto-negotiation. If it does not, try configuring the integrated Ethernet controller manually to match the speed and duplex mode of the hub. v Check the Ethernet controller LEDs on the operator information panel and on the rear of the server. These LEDs indicate whether a problem exists with the connector, cable, or hub. - The Ethernet transmit/receive activity LED, on the operator information panel, is lit when the Ethernet controller sends or receives data over the Ethernet Network. If the Ethernet transmit/receive activity LED is off, make sure that the hub and network are operating and that the correct device drivers are installed. - The Ethernet link status LED, on the rear of the server, is lit when the Ethernet controller receives a LINK pulse from the hub. If the LED is off, there might be a defective connector or cable or a problem with the hub. v Make sure that you are using the correct device drivers which are supplied with your server. v Check for operating-system-specific causes for the problem. v Make sure that the device drivers on the client and server are using the same protocol. Chapter 3. Diagnostics 37

  • 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

Power checkout
Power problems can be difficult to solve. For example, a short circuit can exist
anywhere on any of the power distribution buses. Usually a short circuit will cause
the power subsystem to shut down because of an overcurrent condition.
A general procedure for troubleshooting power problems is as follows:
1.
Turn off the server and disconnect all ac power cords.
2.
Check for loose cables in the power subsystem. Also check for short circuits, for
example, if there is a loose screw causing a short circuit on a circuit board.
3.
Remove adapters and disconnect the cables and power connectors to all
internal and external devices until the server is at the minimum configuration
required to start the server (see “Minimum operating requirements” on page
158).
4.
Reconnect all ac power cords and turn on the server. If the server starts up
successfully, replace adapters and devices one at a time until the problem is
isolated. If the server does not start up from the minimal configuration, replace
FRUs of minimal configuration one at a time until the problem is isolated.
To use this method, it is important to know the minimum configuration required for a
system to start (see page 158). For specific problems, see “Power-supply LED
errors” on page 146.
Troubleshooting the Ethernet controller
This section provides troubleshooting information for problems that might occur with
the 10/100/1000 Mbps Ethernet controller.
Network connection problems
If the Ethernet controller cannot connect to the network, check the following
conditions:
v
Make sure that the cable is installed correctly.
The network cable must be securely attached at all connections. If it does the
cable is attached but the problem remains, try a different cable.
If you set the Ethernet controller to operate at either 100 Mbps or 1000 Mbps,
you must use Category 5 or higher cabling.
v
Determine whether the hub supports auto-negotiation. If it does not, try
configuring the integrated Ethernet controller manually to match the speed and
duplex mode of the hub.
v
Check the Ethernet controller LEDs on the operator information panel and on the
rear of the server.
These LEDs indicate whether a problem exists with the connector, cable, or hub.
The Ethernet transmit/receive activity LED, on the operator information panel,
is lit when the Ethernet controller sends or receives data over the Ethernet
Network. If the Ethernet transmit/receive activity LED is off, make sure that
the hub and network are operating and that the correct device drivers are
installed.
The Ethernet link status LED, on the rear of the server, is lit when the
Ethernet controller receives a LINK pulse from the hub. If the LED is off, there
might be a defective connector or cable or a problem with the hub.
v
Make sure that you are using the correct device drivers which are supplied with
your server.
v
Check for operating-system-specific causes for the problem.
v
Make sure that the device drivers on the client and server are using the same
protocol.
Chapter 3. Diagnostics
37