HP StorageWorks 4/16 HP StorageWorks DC and DC04 SAN Backbone Director Switche - Page 176

How to determine whether or not to replace a CP blade

Page 176 highlights

• Replacement DC04 SAN Director CP blade (CP8) How to determine whether or not to replace a CP blade The following events might indicate that a CP blade is faulty: • The status LED on the CP blade is amber, or the power LED is not lit. • The CP blade does not respond to Telnet commands, or the serial console is not available. • The slotShow command does not show that the CP blade is enabled. • The haShow command indicates an error. • The clock is inaccurate, or the CP blade does not boot up or shut down normally. • Any of the following messages is displayed in the error log: • Slot unknown message relating to a CP slot • CP blade errors or I2C timeouts • FRU: FRU_FAULTY messages for a CP blade • Configuration loader messages or Sys PCI config messages • Generic system driver messages (FABSYS) • Platform system driver messages (Platform) • EM messages that indicate a problem with a CP blade • Function fail messages for the CP master For more information about error messages, refer to the Fabric OS Message Reference. Recording critical DC04 SAN Director information Back up the DC04 SAN Director configuration before you replace a CP blade. Refer to the HP StorageWorks Fabric OS 6.2.x administrator guide for backup information. To record critical DC04 SAN Director information: 1. Login to the functioning CP blade as admin, using either a Telnet or a serial console connection. 2. Type haShow to determine which CP blade is active: swDir:admin> haShow Local CP (Slot 7, CP1) : Active Remote CP (Slot 6, CP0) : Standby, Healthy HA Enabled, Heartbeat Up, HA State Synchronized 3. Enter all remaining commands from the serial console for the active CP blade, unless otherwise indicated. For more information about commands, refer to the HP StorageWorks Fabric OS 6.2.x administrator guide 176 Replacing DC04 SAN Director field-replaceable units (FRUs)

  • 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
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256

Replacement DC04 SAN Director CP blade (CP8)
How to determine whether or not to replace a CP blade
The following events might indicate that a CP blade is faulty:
The status LED on the CP blade is amber, or the power LED is not lit.
The CP blade does not respond to Telnet commands, or the serial console is not available.
The
slotShow
command does not show that the CP blade is enabled.
The
haShow
command indicates an error.
The clock is inaccurate, or the CP blade does not boot up or shut down normally.
Any of the following messages is displayed in the error log:
Slot unknown
message relating to a CP slot
CP blade errors or I
2
C timeouts
FRU: FRU_FAULTY
messages for a CP blade
Configuration loader messages or
Sys PCI config
messages
Generic system driver messages (
FABSYS
)
Platform system driver messages (
Platform
)
EM
messages that indicate a problem with a CP blade
Function fail messages for the CP master
For more information about error messages, refer to the
Fabric OS Message Reference
.
Recording critical DC04 SAN Director information
Back up the DC04 SAN Director configuration before you replace a CP blade. Refer to the
HP
StorageWorks Fabric OS 6.2.x administrator guide
for backup information.
To record critical DC04 SAN Director information:
1.
Login to the functioning CP blade as
admin
, using either a Telnet or a serial console connection.
2.
Type
haShow
to determine which CP blade is active:
swDir:admin>
haShow
Local CP (Slot 7, CP1) : Active
Remote CP (Slot 6, CP0) : Standby, Healthy
HA Enabled, Heartbeat Up, HA State Synchronized
3.
Enter all remaining commands from the serial console for the
active
CP blade, unless otherwise
indicated. For more information about commands, refer to the
HP StorageWorks Fabric OS 6.2.x
administrator guide
Replacing DC04 SAN Director field-replaceable units (FRUs)
176