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

Evaluate the Fabric, Gathering Information, Collect Device, Software, Hardware, and Config Data

Page 148 highlights

Updating Switches to the Core PID Addressing Evaluate the Fabric The fabric must be evaluated to: ■ Find any devices which bind to PIDs ■ Determine how each device driver will respond to the PID format change ■ Determine how any multi-pathing software will respond to a fabric service interruption If current details about the SAN are already available, it may be possible to skip the Data Collection step. If not, it is necessary to collect information about each device in the SAN. Any type of device may be able to bind by PID; each device should be evaluated prior to attempting an online update. This information has broad applicability, since PID-bound devices are not able to seamlessly perform in many routine maintenance or failure scenarios. Gathering Information Collect Device, Software, Hardware, and Config Data The following is a non-comprehensive list of information to collect: ■ HBA driver versions ■ Fabric OS versions ■ RAID array microcode versions ■ SCSI bridge code versions ■ JBOD drive firmware versions ■ Multi-pathing software versions ■ HBA time-out values ■ Multi-pathing software time-out values ■ Kernel time-out values ■ Configuration of switch 148 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
148
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Evaluate the Fabric
The fabric must be evaluated to:
Find any devices which bind to PIDs
Determine how each device driver will respond to the PID format change
Determine how any multi-pathing software will respond to a fabric service
interruption
If current details about the SAN are already available, it may be possible to skip
the Data Collection step. If not, it is necessary to collect information about each
device in the SAN. Any type of device may be able to bind by PID; each device
should be evaluated prior to attempting an online update. This information has
broad applicability, since PID-bound devices are not able to seamlessly perform in
many routine maintenance or failure scenarios.
Gathering Information
Collect Device, Software, Hardware, and Config Data
The following is a non-comprehensive list of information to collect:
HBA driver versions
Fabric OS versions
RAID array microcode versions
SCSI bridge code versions
JBOD drive firmware versions
Multi-pathing software versions
HBA time-out values
Multi-pathing software time-out values
Kernel time-out values
Configuration of switch