IBM HS20 Hardware Maintenance Manual - Page 96

Service processor error codes, form generally beginning with A2, A3, A4, A5, A6, A7, AD, AE

Page 96 highlights

Note: See "System" on page 94 to determine which components should be replaced by a field service technician. Network connection problems Symptom FRU/action One or more blade servers are unable to communicate with the network. Verify that: v The switch modules for the network interface being used are installed in the correct BladeCenter bays and are configured and operating correctly. See the IBM BladeCenter Type 8677 Hardware Maintenance Manual and Troubleshooting Guide on the IBM BladeCenter Documentation CD for details. v The settings in the switch module are appropriate for the blade server (settings in the switch module are blade-specific). If you installed an I/O expansion option, verify that: v The option is designed for the blade server. v You followed the installation instructions that came with the option. v The option is installed correctly. v You have not loosened any other installed options or cables. v You updated the configuration information in the Configuration/Setup Utility program. Whenever memory or an option is changed, you must update the configuration. If the problem remains, see "Undetermined problems" on page 90. Note: See "System" on page 94 to determine which components should be replaced by a field service technician. Service processor problems Symptom FRU/action Service processor in the management module reports a general monitor failure. v Disconnect the BladeCenter unit from all electrical sources, wait for 30 seconds, reconnect the BladeCenter unit to the electrical sources, and restart the server. If the problem remains, see "Undetermined problems" on page 90 and the IBM BladeCenter Type 8677 Hardware Maintenance Manual and Troubleshooting Guide on the IBM BladeCenter Documentation CD Service processor error codes Note: These codes are viewed in the BladeCenter management module log. When viewed from POST, service processor error codes will appear in hexadecimal form (generally beginning with A2, A3, A4, A5, A6, A7, AD, AE, or E1). However, when viewed from the System Error Log, the messages will appear as text. To determine a possible error condition for the service processor, the System Error Log (see "Viewing error logs from the Configuration/Setup Utility program" on page 21) will refer you to the management module log in the BladeCenter unit. 86 BladeCenter HS20 Type 8832: 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

Note:
See “System” on page 94 to determine which components should be replaced by a field service technician.
Network connection problems
Symptom
FRU/action
One or more blade servers are
unable to communicate with the
network.
Verify that:
v
The switch modules for the network interface being used are installed in the
correct BladeCenter bays and are configured and operating correctly. See the
IBM
BladeCenter Type 8677 Hardware Maintenance Manual and
Troubleshooting Guide
on the IBM
BladeCenter Documentation
CD for details.
v
The settings in the switch module are appropriate for the blade server (settings
in the switch module are blade-specific).
If you installed an I/O expansion option, verify that:
v
The option is designed for the blade server.
v
You followed the installation instructions that came with the option.
v
The option is installed correctly.
v
You have not loosened any other installed options or cables.
v
You updated the configuration information in the Configuration/Setup Utility
program. Whenever memory or an option is changed, you must update the
configuration.
If the problem remains, see “Undetermined problems” on page 90.
Note:
See “System” on page 94 to determine which components should be replaced by a field service technician.
Service processor problems
Symptom
FRU/action
Service processor in the
management module reports a
general monitor failure.
v
Disconnect the BladeCenter unit from all electrical sources, wait for 30 seconds,
reconnect the BladeCenter unit to the electrical sources, and restart the server. If
the problem remains, see “Undetermined problems” on page 90 and the IBM
BladeCenter Type 8677 Hardware Maintenance Manual and Troubleshooting
Guide
on the IBM
BladeCenter Documentation
CD
Service processor error codes
Note:
These codes are viewed in the BladeCenter management module log.
When viewed from POST, service processor error codes will appear in hexadecimal
form (generally beginning with A2, A3, A4, A5, A6, A7, AD, AE, or E1). However,
when viewed from the System Error Log, the messages will appear as text. To
determine a possible error condition for the service processor, the System Error Log
(see “Viewing error logs from the Configuration/Setup Utility program” on page 21)
will refer you to the management module log in the BladeCenter unit.
86
BladeCenter HS20 Type 8832: Hardware Maintenance Manual and Troubleshooting Guide