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

Upgrade, downgrade, and HA considerations, Port cost considerations

Page 220 highlights

To set and display the router port cost 1. Disable any port on which you want to set the router port cost. 2. Enable admin for the EX_Port/VEX_Port with portCfgExport or portCfgVexport. 3. Enter the fcrRouterPortCost command to display the router port cost per EX_Port. switch:admin_06> fcrrouterportcost Port Cost 7/3 1000 7/4 1000 7/9 1000 7/10 1000 7/13 1000 10/0 1000 You can also use the fcrRouteShow and fcrDbgRoutShow to display the router port cost. 4. Enter the fcrRouterPortCost command with a port and slot number, to display the router port cost for a single EX_Port. switch:admin_06> fcrrouterportcost 7/10 Port Cost 7/10 1000 5. Enter the fcrRouterPortCost command with a port and slot number and a specific cost, to set the router port cost for a single EX_Port. switch:admin_06> fcrrouterportcost 7/10 10,000 6. Enter the fcrRouterPortCost command, to set the cost of the EX_Port back to the default. switch:admin_06> fcrrouterportcost 7/10 0 Upgrade, downgrade, and HA considerations • For HA, the router port cost is synchronized to the standby CP. • When upgrading the router switch from a prior Fabric OS version to Fabric OS v5.2.x, during warm recovery, if EX_Port is online, the default port cost is used. • When downgrading the router switch from Fabric OS v5.2.x to a prior Fabric OS version that does not support router port cost, the port configuration file retains the router port cost values. However, they are not used by the legacy Fabric OS. • Legacy switches in the backbone fabric program all the router ports without considering router port cost. Fabric OS v5.2.x considers the legacy router port cost as 1000 for both EX or VEX_ports. Port cost considerations The router port cost has the following considerations: • Router port sets are defined as follows: • 0-7 and FCIP Tunnel 16-23 • 8-15 and FCIP Tunnel 24-31 More than two routers sets can exist on a chassis (e.g. 4/256 SAN Director). • The router port cost does not help distinguish one IFL (or EX/VEX_Port link) from another, if all the IFLs are connected to the same port set. Therefore, if you connect IF1 and IFL2 to the same edge fabric in port set 0-7 and then configure them to different router port costs, traffic is still balanced across all the IFLs in the same port set. • Use proper SAN design guideline to connect the IFLs to different port sets for effective router port cost use. For example, if both a low speed VEX_Port and a high-speed EX_Port are going to the same edge fabric, connect the lower router cost IFLs to one port group (for example ports 0-7) and the higher 220 Using the FC-FC routing service

  • 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

220
Using the FC-FC routing service
To set and display the router port cost
1.
Disable any port on which you want to set the router port cost.
2.
Enable
admin
for the EX_Port/VEX_Port with
portCfgExport
or
portCfgVexport
.
3.
Enter the
fcrRouterPortCost
command to display the router port cost per EX_Port.
You can also use the
fcrRouteShow
and
fcrDbgRoutShow
to display the router port cost.
4.
Enter the
fcrRouterPortCost
command with a port and slot number, to display the router port cost
for a single EX_Port.
5.
Enter the
fcrRouterPortCost
command with a port and slot number and a specific cost, to set the
router port cost for a single EX_Port.
6.
Enter the
fcrRouterPortCost
command
,
to set the cost of the EX_Port back to the default.
Upgrade, downgrade, and HA considerations
For HA, the router port cost is synchronized to the standby CP.
When upgrading the router switch from a prior Fabric OS version to Fabric OS v5.2.x, during warm
recovery, if EX_Port is online, the default port cost is used.
When downgrading the router switch from Fabric OS v5.2.x to a prior Fabric OS version that does not
support router port cost, the port configuration file retains the router port cost values. However, they are
not used by the legacy Fabric OS.
Legacy switches in the backbone fabric program all the router ports without considering router port
cost. Fabric OS v5.2.x considers the legacy router port cost as 1000 for both EX or VEX_ports.
Port cost considerations
The router port cost has the following considerations:
Router port sets are defined as follows:
0-7 and FCIP Tunnel 16-23
8-15 and FCIP Tunnel 24-31
More than two routers sets can exist on a chassis (e.g. 4/256 SAN Director).
The router port cost does not help distinguish one IFL (or EX/VEX_Port link) from another, if all the IFLs
are connected to the same port set. Therefore, if you connect IF1 and IFL2 to the same edge fabric in
port set 0–7 and then configure them to different router port costs, traffic is still balanced across all the
IFLs in the same port set.
Use proper SAN design guideline to connect the IFLs to different port sets for effective router port cost
use. For example, if both a low speed VEX_Port and a high-speed EX_Port are going to the same edge
fabric, connect the lower router cost IFLs to one port group (for example ports 0–7) and the higher
switch:admin_06> fcrrouterportcost
Port
Cost
------------------------
7/3
1000
7/4
1000
7/9
1000
7/10
1000
7/13
1000
10/0
1000
switch:admin_06> fcrrouterportcost 7/10
Port
Cost
------------------------
7/10
1000
switch:admin_06> fcrrouterportcost 7/10 10,000
switch:admin_06> fcrrouterportcost 7/10 0