HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.X Procedures User Guide (AA- - Page 215

Table 45 Effects of PID format changes on configurations, Selecting a PID format

Page 215 highlights

Table 45 Effects of PID format changes on configurations PID format before PID format after change change Configuration effect Native Extended Edge Native Core Extended Edge Core Extended Edge Native Core Native Core Extended Edge No impact No impact You must: • Reenable zoning, if there is an active zone set and it uses port zones. • You do not need to reconfigure DID if using: • Performance monitoring • The configure command to change the PID format • The performance monitor database • The zoning database • Security dcc database (if secure mode is enabled) The DID is converted by FOS. After changing the fabric PID format and verifying correct fabric operation, resave configuration data by running the configUpload command. Before downgrading firmware, change the PID back to supported PIDs, such as Core PID. If the database is converted, save the converted database, and then download the earlier OS. Selecting a PID format All switches in a fabric must use the same PID format, so if you add a switch that uses a different PID format to a fabric, the switch segments from the fabric. The format you select for your fabric depends on the mix of switches in the fabric, and to an extent on the specific releases of Fabric OS in use (for example, Extended Edge PID format is available only in Fabric OS 2.6.2 and later, Fabric OS 3.1.2 and later, and Fabric OS 4.2.0 and later). If you are building a new fabric with switches running various Fabric OS versions, use Core PID format to simplify port-to-area_ID mapping. Table 46 shows various combinations of existing fabrics, new switches added to those fabrics, and the recommended PID format for that combination. The criteria for the recommendations are first to eliminate host reboots, and second to minimize the need for a host reboot in the future. Fabric OS 5.x administrator guide 215

  • 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

Fabric OS 5.x administrator guide
215
After changing the fabric PID format and verifying correct fabric operation, resave configuration data by
running the
configUpload
command.
Before downgrading firmware, change the PID back to supported PIDs, such as Core PID. If the database
is converted, save the converted database, and then download the earlier OS.
Selecting a PID format
All switches in a fabric must use the same PID format, so if you add a switch that uses a different PID
format to a fabric, the switch segments from the fabric. The format you select for your fabric depends on
the mix of switches in the fabric, and to an extent on the specific releases of Fabric OS in use (for
example, Extended Edge PID format is available only in Fabric OS 2.6.2 and later, Fabric OS 3.1.2 and
later, and Fabric OS 4.2.0 and later).
If you are building a new fabric with switches running various Fabric OS versions, use Core PID format to
simplify port-to-area_ID mapping.
Table 46
shows various combinations of existing fabrics, new switches added to those fabrics, and the
recommended PID format for that combination. The criteria for the recommendations are first to eliminate
host reboots, and second to minimize the need for a host reboot in the future.
Table 45
Effects of PID format changes on configurations
PID format before
change
PID format after
change
Configuration effect
Native
Extended Edge
No impact
Extended Edge
Native
No impact
Native
Core
You must:
Reenable zoning, if there is an active zone set and it
uses port zones.
You do not need to reconfigure DID if using:
Performance monitoring
The configure command to change the PID
format
The performance monitor database
The zoning database
Security dcc database (if secure mode is
enabled)
The DID is converted by FOS.
Core
Native
Extended Edge
Core
Core
Extended Edge