HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.x administrator guide (569 - Page 239

Setting a proxy PID, Matching fabric parameters, fcrProxyConfig, fcrXlateConfig, con

Page 239 highlights

higher router cost IFLs (for example ports 8-15). For VEX_Ports, you would use ports in the range of 16-23 or 24-31. You can connect multiple EX_Ports or VEX_Ports to the same edge fabric. The EX_Ports can all be on the same 400 MP Router or 4/256 SAN Director with an B-Series MP Router blade, or they can be on multiple routers. Multiple EX_Ports create multiple paths for frame routing. Multiple paths can be used in two different, but compatible, ways: • Failing over from one path to another • Using multiple paths in parallel to increase effective data transmission rates EX_Ports and VEX_Ports, when connected, are assigned different router port costs and traffic will flow only through the EX_Ports. Routing failover is automatic, but it can result in frames arriving out of order when frames take different routes. The 400 MP Router or 4/256 SAN Director with an B-Series MP Router blade can force in-order delivery, although frame delivery is delayed immediately after the path failover. Source EX_Ports can balance loads across multiple destination EX_Ports attached to the same edge fabric using exchange IDs from the routed frames as keys to distribute the traffic. Setting a proxy PID When a 400 MP Router or 4/256 SAN Director with an B-Series MP Router blade is first configured, the PIDs for the proxy devices are automatically assigned. Proxy PIDs (as well as phantom domain IDs) persist across reboots. The most common situation in which you would set a proxy PID is when you replace a switch. If you replace the switch and want to continue using the old PID assignments, you can configure it to do so; this value remains in the system even if the blade is replaced. To minimize disruption to the edge fabrics, set the proxy PIDs to the same values used with the old hardware. The fcrProxyConfig command displays or sets the persistent configuration of proxy devices. Used with the -s slot option, it can also influence the assignment of the xlate domain port number (which is used to determine the Area_ID field of the PID) and the Port_ID field. Like the PIDs in a fabric, a proxy PID must be unique. If the slot argument results in a duplicate PID, it will be ignored. Proxy PIDs are automatically assigned to devices imported into a fabric, starting at f001. For Proxy IDs projected to a McDATA edge fabric in McDATA fabric mode, use valid ALPAs (lower 8 bits). See the fcrProxyConfig command in the Fabric OS Command Reference Manual for more details. Use the fcrXlateConfig command to display or assign a preferred domain ID to a translate domain. See the fcrXlateConfig command in the Fabric OS Command Reference Manual for more details. Matching fabric parameters By default, EX_Ports and VEX_Ports detect, autonegotiate, and configure the fabric parameters without user intervention. You can optionally configure these parameters manually. To change the fabric parameters on a switch in the edge fabric, execute the configure command. To change the fabric parameters of an EX_Port on the 4/256 SAN Director with a B-Series MP Router blade, use the portCfgEXPort command. If you want to change the fabric parameters of a VEX_Port, then use the portCfgVEXPort command. The PID mode for the backbone fabric PID mode and the edge fabric PID mode do not need to match, but the PID mode for the EX_Port or VEX_Port and the edge fabric to which it is attached must match. You can statically set the PID mode for the fabric by using the -p option with the portCfgEXPort command. (Use the -t option to disable the negotiate fabric parameter feature). Otherwise, the PID mode is autonegotiated. The various edge fabrics may have different PID modes. Fabric parameter settings, namely, E_D_TOV (error-detect timeout value), R_A_TOV (resource-allocation timeout value), and PID format, must be the same on EX_Ports or VEX_Ports and on the fabrics to which they are connected. You can set the PID format on an EX_Port when you configure an interfabric link. The default values for E_D_TOV and R_A_TOV for an EX_Port or VEX_Port must match those values on other Brocade switches. Only if you have adjusted these parameters for the edge fabric do you need to adjust them for an EX_Port or VEX_Port. Fabric OS 5.3.0 administrator guide 241

  • 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
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418
  • 419
  • 420
  • 421
  • 422
  • 423
  • 424
  • 425
  • 426
  • 427
  • 428
  • 429
  • 430
  • 431
  • 432
  • 433
  • 434
  • 435
  • 436
  • 437
  • 438
  • 439
  • 440
  • 441
  • 442
  • 443
  • 444
  • 445
  • 446
  • 447
  • 448
  • 449
  • 450
  • 451
  • 452
  • 453
  • 454
  • 455
  • 456
  • 457
  • 458
  • 459
  • 460
  • 461
  • 462
  • 463
  • 464
  • 465

Fabric OS 5.3.0 administrator guide
241
higher router cost IFLs (for example ports 8–15). For VEX_Ports, you would use ports in the range of
16-23 or 24-31.
You can connect multiple EX_Ports or VEX_Ports to the same edge fabric. The EX_Ports can all be on the
same 400 MP Router or 4/256 SAN Director with an B-Series MP Router blade, or they can be on multiple
routers. Multiple EX_Ports create multiple paths for frame routing. Multiple paths can be used in two
different, but compatible, ways:
Failing over from one path to another
Using multiple paths in parallel to increase effective data transmission rates
EX_Ports and VEX_Ports, when connected, are assigned different router port costs and traffic will flow only
through the EX_Ports. Routing failover is automatic, but it can result in frames arriving out of order when
frames take different routes. The 400 MP Router or 4/256 SAN Director with an B-Series MP Router blade
can force in-order delivery, although frame delivery is delayed immediately after the path failover.
Source EX_Ports can balance loads across multiple destination EX_Ports attached to the same edge fabric
using exchange IDs from the routed frames as keys to distribute the traffic.
Setting a proxy PID
When a 400 MP Router or 4/256 SAN Director with an B-Series MP Router blade is first configured, the
PIDs for the proxy devices are automatically assigned. Proxy PIDs (as well as phantom domain IDs) persist
across reboots.
The most common situation in which you would set a proxy PID is when you replace a switch. If you
replace the switch and want to continue using the old PID assignments, you can configure it to do so; this
value remains in the system even if the blade is replaced. To minimize disruption to the edge fabrics, set
the proxy PIDs to the same values used with the old hardware.
The
fcrProxyConfig
command displays or sets the persistent configuration of proxy devices. Used with
the
-s
slot
option, it can also influence the assignment of the xlate domain port number (which is used to
determine the Area_ID field of the PID) and the Port_ID field. Like the PIDs in a fabric, a proxy PID must be
unique. If the
slot
argument results in a duplicate PID, it will be ignored. Proxy PIDs are automatically
assigned to devices imported into a fabric, starting at f001. For Proxy IDs projected to a McDATA edge
fabric in McDATA fabric mode, use valid ALPAs (lower 8 bits).
See the
fcrProxyConfig
command in the
Fabric OS Command Reference Manual
for more details.
Use the
fcrXlateConfig
command to display or assign a preferred domain ID to a translate domain.
See the
fcrXlateConfig
command in the
Fabric OS Command Reference Manual
for more details.
Matching fabric parameters
By default, EX_Ports and VEX_Ports detect, autonegotiate, and configure the fabric parameters without user
intervention.
You can optionally configure these parameters manually. To change the fabric parameters on a switch in
the edge fabric, execute the
configure
command. To change the fabric parameters of an EX_Port on the
4/256 SAN Director with a B-Series MP Router blade, use the
portCfgEXPort
command. If you want to
change the fabric parameters of a VEX_Port, then use the
portCfgVEXPort
command.
The PID mode for the backbone fabric PID mode and the edge fabric PID mode do not need to match, but
the PID mode for the EX_Port or VEX_Port and the edge fabric to which it is attached must match. You can
statically set the PID mode for the fabric by using the
-p
option with the
portCfgEXPort
command. (Use
the
-t
option to disable the negotiate fabric parameter feature). Otherwise, the PID mode is
autonegotiated. The various edge fabrics may have different PID modes.
Fabric parameter settings, namely, E_D_TOV (error-detect timeout value), R_A_TOV (resource-allocation
timeout value), and PID format, must be the same on EX_Ports or VEX_Ports and on the fabrics to which
they are connected. You can set the PID format on an EX_Port when you configure an interfabric link.
The default values for E_D_TOV and R_A_TOV for an EX_Port or VEX_Port must match those values on other
Brocade switches. Only if you have adjusted these parameters for the edge fabric do you need to adjust
them for an EX_Port or VEX_Port.