HP StorageWorks 4/32 HP StorageWorks DC and DC04 SAN Backbone Director Switche - Page 82

Removing a control processor blade (CP8)

Page 82 highlights

7. Logged into the active CP, use the configUpload command to upload the DC SAN Director configuration to a specified FTP server. Enter information at the prompts. This is a sample of backing up the configuration files: swDir:admin> configUpload Protocol (scp or ftp) [ftp]: ftp Server Name or IP Address [host]: 123.456.78.90 User Name [None]: user File Name [config.txt]: config.txt Password: xxxxxxxx upload complete Removing a control processor blade (CP8) The DC SAN Director continues to operate while a CP blade is being replaced if the redundant CP blade is active and a failover does not occur. You can prevent failover by entering the haDisable command. CAUTION: Wear a grounded ESD strap when handling DC SAN Director components. The Director chassis provides a grounding connection above the power connectors. Also, store ESD-sensitive components in antistatic packaging. To remove a CP blade: IMPORTANT: The CP8 blade is compatible with the DC SAN Director and the DC04 SAN Director. 1. Remove the chassis door. See "Removing the chassis door" on page 73. 2. Login to the active CP as the admin user. You can use a serial cable or Telnet, Web Tools, or Fabric Manger. Determine which CP is active using the haShow command or view the active LED on the front of the CP. 3. If the faulty CP is the active CP, issue the haFailover command. Wait until the failover has completed. Use the haShow command to verify that the CPs are synchronized and the failover is complete. 4. Power off the blade by sliding the slider switch in the top ejector down to the off position (see Figure 30). 5. Disconnect all cables from the faulty (standby) CP. 6. Unscrew the thumb screw from both ejectors using the Phillips screwdriver. 82 Replacing DC 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

7.
Logged into the active CP, use the
configUpload
command to upload the DC SAN Director
configuration to a specified FTP server. Enter information at the prompts.
This is a sample of backing up the configuration files:
swDir:admin>
configUpload
Protocol (scp or ftp) [ftp]: ftp
Server Name or IP Address [host]: 123.456.78.90
User Name [None]: user
File Name [config.txt]: config.txt
Password: xxxxxxxx
upload complete
Removing a control processor blade (CP8)
The DC SAN Director continues to operate while a CP blade is being replaced if the redundant CP
blade is active and a failover does not occur. You can prevent failover by entering the
haDisable
command.
CAUTION:
Wear a grounded ESD strap when handling DC SAN Director components. The Director chassis
provides a grounding connection above the power connectors. Also, store ESD-sensitive components
in antistatic packaging.
To remove a CP blade:
IMPORTANT:
The CP8 blade is compatible with the DC SAN Director and the DC04 SAN Director.
1.
Remove the chassis door. See “
Removing the chassis door
” on page 73.
2.
Login to the active CP as the admin user. You can use a serial cable or Telnet, Web Tools, or
Fabric Manger. Determine which CP is active using the
haShow
command or view the active
LED on the front of the CP.
3.
If the faulty CP is the active CP, issue the
haFailover
command. Wait until the failover has
completed. Use the
haShow
command to verify that the CPs are synchronized and the failover
is complete.
4.
Power off the blade by sliding the slider switch in the top ejector down to the off position (see
Figure 30
).
5.
Disconnect all cables from the faulty (standby) CP.
6.
Unscrew the thumb screw from both ejectors using the Phillips screwdriver.
Replacing DC SAN Director field-replaceable units (FRUs)
82