HP StorageWorks MSA 2/8 HP StorageWorks Fabric OS Procedures V3.1.x/4.1.x User - Page 152

Outline for Offline Update Procedure, Procedures for, Updating the Core PID Format

Page 152 highlights

Updating Switches to the Core PID Addressing 5. Change the PID format on each switch in the fabric (see "Procedures for Updating the Core PID Format", on page 154). 6. Once the fabric has re-converged, use the cfgenable command to update zoning (see "Procedures for Updating the Core PID Format", on page 154). 7. Update their bindings for any devices manually bound by PID. This may involve changing them to the new PIDs, or preferably changing to WWN binding. For any devices automatically bound by PID, two options exist: ■ Execute a custom procedure to rebuild its device tree online. Examples are provided in the "Detailed Update Procedures for HP/UX and AIX" on page 155 section of this chapter. ■ Reboot the device to rebuild the device tree. Some operating systems require a special command to do this, for example "boot -r" in Solaris. 8. For devices that do not bind by PID or have had their PID binding updated, mark online or re-associate the disk devices with the multi-pathing software and resume I/O over the updated fabric. 9. Repeat with the other fabrics. Outline for Offline Update Procedure The following steps are intended to provide SAN administrators a starting point for creating site-specific procedures. 1. Schedule an outage for all devices attached to the fabric. 2. Back up all data and verify backups. 3. Shut down all hosts and storage devices attached to the fabric. 4. Disable all switches in the fabric. 5. Change the PID format on each switch in the fabric (see "Procedures for Updating the Core PID Format", on page 154). 6. Re-enable the switches in the updated fabric one at a time. In a core/edge network, enable the core switches first. 7. Once the fabric has re-converged, use the cfgenable command to update zoning (see "Procedures for Updating the Core PID Format", on page 154). 8. Bring the devices online in the order appropriate to the SAN. This usually involves starting up the storage arrays first, and the hosts last. 152 Fabric OS Procedures Version 3.1.x/4.1.x User 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
  • 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
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270

Updating Switches to the Core PID Addressing
152
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
5.
Change the PID format on each switch in the fabric (see “
Procedures for
Updating the Core PID Format
”, on page 154).
6.
Once the fabric has re-converged, use the
cfgenable
command to update
zoning (see “
Procedures for Updating the Core PID Format
”, on page 154).
7.
Update their bindings for any devices manually bound by PID. This may
involve changing them to the new PIDs, or preferably changing to WWN
binding.
For any devices automatically bound by PID, two options exist:
Execute a custom procedure to rebuild its device tree online. Examples
are provided in the “
Detailed Update Procedures for HP/UX and AIX
” on
page 155 section of this chapter.
Reboot the device to rebuild the device tree. Some operating systems
require a special command to do this, for example “
boot –
r
” in Solaris.
8.
For devices that do not bind by PID or have had their PID binding updated,
mark online or re-associate the disk devices with the multi-pathing software
and resume I/O over the updated fabric.
9.
Repeat with the other fabrics.
Outline for Offline Update Procedure
The following steps are intended to provide SAN administrators a starting point
for creating site-specific procedures.
1.
Schedule an outage for all devices attached to the fabric.
2.
Back up all data and verify backups.
3.
Shut down all hosts and storage devices attached to the fabric.
4.
Disable all switches in the fabric.
5.
Change the PID format on each switch in the fabric (see “
Procedures for
Updating the Core PID Format
”, on page 154).
6.
Re-enable the switches in the updated fabric one at a time. In a core/edge
network, enable the core switches first.
7.
Once the fabric has re-converged, use the
cfgenable
command to update
zoning (see “
Procedures for Updating the Core PID Format
”, on page 154).
8.
Bring the devices online in the order appropriate to the SAN. This usually
involves starting up the storage arrays first, and the hosts last.