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

About PID Mapping, Dynamic PID, Static PID

Page 146 highlights

Updating Switches to the Core PID Addressing Note: It is recommended not to use drivers that bind by PID. There are several routine maintenance procedures which may result in a device receiving a new PID. Refer to About PID Mapping for more information. About PID Mapping A PID is a Port Identifier. PIDs are used by the routing and zoning services in Fibre Channel fabrics to identify ports in the network. They are not used to uniquely identify a device; this is done using the World Wide Name (WWN). Some device drivers map logical disk drives to physical Fibre Channel counterparts by PID. An example in a Windows HBA driver is "Drive E: = PID 011F00". Most drivers can either dynamically change PID mappings or use the WWN of the Fibre Channel disk for mapping, not the PID. For example, "Drive E: = WWN 10:00:00:60:69:51:0e:8b". Dynamic PID WWN or dynamic PID binding is most typically used. In this case, changing the device's PID does not affect the mapping. However, before updating the PID format, it is necessary to determine whether or not any devices in the SAN bind by PID (see Evaluate the Fabric). Static PID For those few drivers that use static PID binding, when the format is changed (PID 010F00), the mapping breaks and must be manually fixed. (The driver still has "Drive E: = PID 011F00" but the actual device address is now "010F00"). This can be done by rebooting the host or using a manual update procedure on the host. To manually correct broken mapping due to static PIDs, refer to the following sections for more detail: ■ Evaluate the Fabric of this chapter discusses in more detail the process of updating to the new PID format. This starts with evaluating a production SAN to see which if any devices bind by PID. Then either an online or offline update procedure is chosen to perform the actual update. ■ Frequently Asked Questions provides a Q&A format to discuss the issues surrounding a core PID format update. 146 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
146
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Note:
It is recommended not to use drivers that bind by PID. There are several routine
maintenance procedures which may result in a device receiving a new PID. Refer to
About PID Mapping for more information
.
About PID Mapping
A PID is a Port Identifier. PIDs are used by the routing and zoning services in
Fibre Channel fabrics to identify ports in the network. They are not used to
uniquely identify a device; this is done using the World Wide Name (WWN).
Some device drivers map logical disk drives to physical Fibre Channel
counterparts by PID. An example in a Windows HBA driver is “Drive E: = PID
011F00”. Most drivers can either dynamically change PID mappings or use the
WWN of the Fibre Channel disk for mapping, not the PID. For example, “Drive
E: = WWN 10:00:00:60:69:51:0e:8b”.
Dynamic PID
WWN or dynamic PID binding is most typically used. In this case, changing the
device’s PID does not affect the mapping. However, before updating the PID
format, it is necessary to determine whether or not any devices in the SAN bind by
PID (see
Evaluate the Fabric
).
Static PID
For those few drivers that use static PID binding, when the format is changed (PID
010F00), the mapping breaks and must be manually fixed. (The driver still has
“Drive E: = PID 011F00” but the actual device address is now “010F00”). This
can be done by rebooting the host or using a manual update procedure on the host.
To manually correct broken mapping due to static PIDs, refer to the following
sections for more detail:
Evaluate the Fabric
of this chapter discusses in more detail the process of
updating to the new PID format. This starts with evaluating a production SAN
to see which if any devices bind by PID. Then either an online or offline
update procedure is chosen to perform the actual update.
Frequently Asked Questions
provides a Q&A format to discuss the issues
surrounding a core PID format update.