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

Defining and naming zones, LSAN zones and fabric-to-fabric communications

Page 316 highlights

address authority (NAA) field in the WWN to detect an FC router. LSAN zone enforcement in the local fabric occurs only if the administration domain member list contains both of the devices (local and imported device) specified in the LSAN zone. For more information, see "Managing administrative domains" on page 151. Defining and naming zones Zones are defined locally on a switch or director. Names and memberships, with the exception of hosts and targets exported from one fabric to another, do not need to be coordinated with other fabrics. For example, in Figure 33 on page 298, when the zones for Edge SAN 1 are defined, you do not need to consider the zones in Edge SAN 2, and vice versa. Zones that contain hosts and targets that are shared between the two fabrics need to be explicitly coordinated. To share devices between any two fabrics, you must create an LSAN zone in both fabrics containing the port WWNs of the devices to be shared. Although an LSAN is managed using the same tools as any other zone on the edge fabric, two behaviors distinguish an LSAN from a conventional zone: • A required naming convention. The name of an LSAN begins with the prefix "LSAN_". The LSAN name is case-insensitive; for example, lsan_ is equivalent to LSAN_, Lsan_, and so on. • Members must be identified by their port WWN because port IDs are not necessarily unique across fabrics. The names of the zones need not be explicitly the same, and membership lists of the zones need not be in the same order. To enable device sharing across multiple fabrics, you must create LSAN zones on the edge fabrics (and optionally on the backbone fabric, as well), using normal zoning operations to create zones with names that begin with the special prefix "LSAN_", and adding host and target port WWNs from both local and remote fabrics to each local zone as desired. Zones on the backbone and on multiple edge fabrics that share a common set of devices will be recognized as constituting a single multi-fabric LSAN zone, and the devices that they have in common will be able to communicate with each other across fabric boundaries. LSAN zones and fabric-to-fabric communications Zoning is enforced by all involved fabrics, any communication from one fabric to another must be allowed by the zoning setup on both fabrics. If the SANs are under separate administrative control, then separate administrators maintain access control. NOTE: If you are managing other switches in a fabric, it is recommended that you run the defZone --show command on your Fabric OS 5.1.0 and later switches as a precaution. Default zoning behavior in Fabric OS 5.1.0 and later operates differently compared to earlier versions of Fabric OS (2.x, 3.x v4.x and 5.0.1). For example, if you issue the defZone --noaccess command on a Fabric OS 5.1.0 or later switch, then default zoning configurations will be created on each switch in the fabric (2.x, 3.x, 4.x or v.0.1 switches). Fabric OS 5.1.0 and later switches do not indicate that a default configuration is enabled when you use the cfgShow or cfgActvShow commands. For more information about default zoning, refer to "Administering Advanced Zoning" on page 389. The following example procedure illustrates how LSANs control which devices can communicate with each other. The example procedure shows the creation of two LSANs (called lsan_zone_fabric75 and lsan_zone_fabric2), which involve the following devices: • Switch1 and the host in fabric75. • Switch2, Target A, and Target B in fabric2. • Switch1 is connected to the 4/256 SAN Director or DC Director with an FR4-18i blade using an EX_Port or VEX_Port. • Switch2 is connected to the 4/256 SAN Director or DC Director with an FR4-18i blade using another EX_Port or VEX_Port. • Host has WWN 10:00:00:00:c9:2b:c9:0c (connected to switch1). • Target A has WWN 50:05:07:61:00:5b:62:ed (connected to switch2). 316 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
  • 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

316
Using the FC-FC Routing Service
address authority (NAA) field in the WWN to detect an FC router. LSAN zone enforcement in the local
fabric occurs only if the administration domain member list contains both of the devices (local and
imported device) specified in the LSAN zone.
For more information, see ”
Managing administrative domains
” on page 151.
Defining and naming zones
Zones are defined locally on a switch or director. Names and memberships, with the exception of hosts
and targets exported from one fabric to another, do not need to be coordinated with other fabrics. For
example, in
Figure 33
on page 298, when the zones for Edge SAN 1 are defined, you do not need to
consider the zones in Edge SAN 2, and vice versa.
Zones that contain hosts and targets that are shared between the two fabrics need to be explicitly
coordinated. To share devices between any two fabrics, you must create an LSAN zone in both fabrics
containing the port WWNs of the devices to be shared. Although an LSAN is managed using the same
tools as any other zone on the edge fabric, two behaviors distinguish an LSAN from a conventional zone:
A required naming convention. The name of an LSAN begins with the prefix “LSAN_”. The LSAN name
is case-insensitive; for example,
lsan_
is equivalent to
LSAN_
,
Lsan_
, and so on.
Members must be identified by their port WWN because port IDs are not necessarily unique across
fabrics. The names of the zones need not be explicitly the same, and membership lists of the zones
need not be in the same order.
To enable device sharing across multiple fabrics, you must create LSAN zones on the edge fabrics (and
optionally on the backbone fabric, as well), using normal zoning operations to create zones with names
that begin with the special prefix “LSAN_”, and adding host and target port WWNs from both local and
remote fabrics to each local zone as desired. Zones on the backbone and on multiple edge fabrics that
share a common set of devices will be recognized as constituting a single multi-fabric LSAN zone, and the
devices that they have in common will be able to communicate with each other across fabric boundaries.
LSAN zones and fabric-to-fabric communications
Zoning is enforced by all involved fabrics, any communication from one fabric to another must be allowed
by the zoning setup on both fabrics. If the SANs are under separate administrative control, then separate
administrators maintain access control.
NOTE:
If you are managing other switches in a fabric, it is recommended that you run the
defZone
--show
command on your Fabric OS 5.1.0 and later switches as a precaution. Default zoning behavior in
Fabric OS 5.1.0 and later operates differently compared to earlier versions of Fabric OS (2.x, 3.x v4.x and
5.0.1).
For example, if you issue the
defZone
--
noaccess
command on a Fabric OS 5.1.0 or later switch,
then default zoning configurations will be created on each switch in the fabric (2.x, 3.x, 4.x or v.0.1
switches). Fabric OS 5.1.0 and later switches do not indicate that a default configuration is enabled
when you use the
cfgShow
or
cfgActvShow
commands. For more information about default zoning,
refer to ”
Administering Advanced Zoning
” on page 389.
The following example procedure illustrates how LSANs control which devices can communicate with each
other. The example procedure shows the creation of two LSANs (called
lsan_zone_fabric75
and
lsan_zone_fabric2
), which involve the following devices:
Switch1 and the host in fabric75.
Switch2, Target A, and Target B in fabric2.
Switch1 is connected to the 4/256 SAN Director or DC Director with an FR4-18i blade using an
EX_Port or VEX_Port.
Switch2 is connected to the 4/256 SAN Director or DC Director with an FR4-18i blade using another
EX_Port or VEX_Port.
Host has WWN 10:00:00:00:c9:2b:c9:0c (connected to switch1).
Target A has WWN 50:05:07:61:00:5b:62:ed (connected to switch2).