HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.1.x administrator guide (5697 - Page 287

Creating a TI zone

Page 287 highlights

• FCR does not support Traffic Isolation. • Ports in a TI zone must belong to switches that run Fabric OS v6.0 or later. • Traffic Isolation is not supported in fabrics with switches running firmware versions earlier than Fabric OS 6.0. However, the existence of a TI zone in such a fabric is backward compatible and does not disrupt fabric operation in switches running earlier firmware versions. Limitations and restrictions of Traffic Isolation The following are limitations of TI zones: • A maximum of 255 TI zones can be created in one fabric. A fabric merge resulting in greater than 255 TI zones results in merge failure and the fabrics are segmented. • A TI zone can be created using D,I (Domain, Index) notation only. Use of WWNs is not allowed. • To include a trunk group in a TI zone, you must include all ports of the trunk in the TI zone. • Two N_Ports that have the same shared area cannot be configured in different TI zones. This limitation does not apply to E_Ports that use the same shared area. • Ports that are in different TI zones cannot communicate with each other if failover is disabled, even if they are in the same (regular) zone. Admin Domain considerations for Traffic Isolation Note the following if you implement Admin Domains and TI zones: • TI zones are applicable only in AD0, and the E_Ports that are members of a TI zone must be in the AD0 device list. Because TI zones must use D,I notation, the AD0 device list must be declared using D,I notation for ports that are to be used in TI zones. • A port used in a TI zone cannot be a member of multiple Admin Domains. • Use care if defining TI zones with ports that are shared across Admin Domains because of the limitation that a given port can appear in only one TI zone. Use the zone --validate command to detect conflicting members across Admin Domains. Best practice: Do not use ports that are shared across Admin Domains in a TI zone. Creating a TI zone When you create a TI zone, by default, failover is enabled and the zone is activated. To create a TI zone: 1. Connect to the switch and log in as admin. 2. Enter the zone --create command. zone --create -t objtype [-o optlist] name -p "portlist" where: objtype optlist name portlist The zone object type, which is ti for TI zones. A list of options for creating the zone and controlling failover mode. • Activate the zone after it is created. • Deactivate the zone after it is created. • Disable failover mode. • Enable failover mode. The name of the zone to be created. The list of ports to be included in the TI zone. Ports are designated using "D,I" (Domain,Index) format. Multiple ports are separated by a semicolon, followed by a space. 3. Enter the cfgEnable command for the appropriate zone configuration to make the change effective. The following examples create a TI zone named "redzone", which contains E_Ports 1,1 and 2,4 and N_Ports 1,8 and 2,6. Fabric OS 6.1.x administrator guide 287

  • 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
  • 466
  • 467
  • 468
  • 469
  • 470
  • 471
  • 472
  • 473
  • 474
  • 475
  • 476
  • 477
  • 478
  • 479
  • 480
  • 481
  • 482
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492

Fabric OS 6.1.x administrator guide
287
FCR does not support Traffic Isolation.
Ports in a TI zone must belong to switches that run Fabric OS v6.0 or later.
Traffic Isolation is not supported in fabrics with switches running firmware versions earlier than Fabric
OS 6.0. However, the existence of a TI zone in such a fabric is backward compatible and does not
disrupt fabric operation in switches running earlier firmware versions.
Limitations and restrictions of Traffic Isolation
The following are limitations of TI zones:
A maximum of 255 TI zones can be created in one fabric. A fabric merge resulting in greater than 255
TI zones results in merge failure and the fabrics are segmented.
A TI zone can be created using D,I (Domain, Index) notation only. Use of WWNs is not allowed.
To include a trunk group in a TI zone, you must include all ports of the trunk in the TI zone.
Two N_Ports that have the same shared area cannot be configured in different TI zones. This limitation
does not apply to E_Ports that use the same shared area.
Ports that are in different TI zones cannot communicate with each other if failover is disabled, even if
they are in the same (regular) zone.
Admin Domain considerations for Traffic Isolation
Note the following if you implement Admin Domains and TI zones:
TI zones are applicable only in AD0, and the E_Ports that are members of a TI zone must be in the AD0
device list. Because TI zones must use D,I notation, the AD0 device list must be declared using D,I
notation for ports that are to be used in TI zones.
A port used in a TI zone cannot be a member of multiple Admin Domains.
Use care if defining TI zones with ports that are shared across Admin Domains because of the limitation
that a given port can appear in only one TI zone. Use the
zone --validate
command to detect
conflicting members across Admin Domains.
Best practice:
Do not use ports that are shared across Admin Domains in a TI zone.
Creating a TI zone
When you create a TI zone, by default, failover is enabled and the zone is activated.
To create a TI zone:
1.
Connect to the switch and log in as admin.
2.
Enter the
zone --create
command.
zone --create -t objtype [-o optlist] name -p "portlist"
where:
3.
Enter the
cfgEnable
command for the appropriate zone configuration to make the change effective.
The following examples create a TI zone named “redzone”, which contains E_Ports 1,1 and 2,4 and
N_Ports 1,8 and 2,6.
objtype
The zone object type, which is
ti
for TI zones.
optlist
A list of options for creating the zone and controlling failover mode.
Activate the zone after it is created.
Deactivate the zone after it is created.
Disable failover mode.
Enable failover mode.
name
The name of the zone to be created.
portlist
The list of ports to be included in the TI zone. Ports are designated using
“D,I” (Domain,Index) format. Multiple ports are separated by a semicolon,
followed by a space.