Fabric OS 6.2 administrator guide 243
Figure 31
Broadcast zones and Admin Domains
The dotted box represents the consolidated broadcast zone, which contains all of the devices that can
receive broadcast packets. The actual delivery of broadcast packets is also controlled by the Admin
Domain and zone enforcement logic. The consolidated broadcast zone is not an actual zone, but is just an
abstraction used for explaining the behavior.
•
The broadcast zone for AD1 includes member devices
1,1
,
3,1
and
5,1
; however,
3,1
and
5,1
are
not members of AD1. Consequently, from the AD1 broadcast zone, only
1,1
is added to the
consolidated broadcast zone.
•
The broadcast zone for AD2 includes member devices
2,1
,
3,1
, and
4,1
. Even though
2,1
is a
member of AD1, it is not a member of AD2 and so is not added to the consolidated broadcast zone.
•
Device
3,1
is added to the consolidated broadcast zone because of its membership in the AD2
broadcast zone.
When a switch receives a broadcast packet it forwards the packet only to those devices which are zoned
with the sender and are also part of the consolidated broadcast zone.
You can check whether a broadcast zone has any invalid members that cannot be enforced in the current
AD context. See ”
Validating a zone
” on page 249 for complete instructions.
Broadcast zones and FC-FC routing
If you create broadcast zones in a metaSAN consisting of multiple fabrics connected through an FC router,
the broadcast zone must include the IP device that exists in the edge or backbone fabric as well as the
proxy device in the remote fabric. See Chapter 16, ”
Optimizing fabric behavior
” on page 339 for
information about proxy devices and the FC router.
Upgrade and downgrade considerations for broadcast zones
If you upgrade from a Fabric OS version earlier than 5.3.0 to Fabric OS 5.3.0 or later, you must rename
any existing zones named
broadcast
before you upgrade. The firmware download fails if a pre-5.3.x
switch has a zone with the name of
broadcast
in the effective configuration.
When downgrading to a firmware version earlier than Fabric OS 5.3.0, you must remove or disable the
broadcast zone. The firmware downgrade fails if a zone with the name
broadcast
is part of the effective
configuration.
High availability considerations with broadcast zones
If a switch has broadcast zone-capable firmware on the active CP (Fabric OS 5.3.x or later) and broadcast
zone-incapable firmware on the standby CP (Fabric OS version earlier than 5.3.0), you cannot create a
broadcast zone because the zoning behavior would not be the same across an HA failover. If the switch
failed over, the broadcast zone would lose its special significance and would be treated as a regular zone.
broadcast
"1,1; 3,1; 5,1"
"1,1"
"2,1"
broadcast
"2,1; 3,1; 4,1"
"3,1"
"4,1"
"5,1"
broadcast
"1,1; 3,1; 4,1"
"1,1"
"3,1; 4,1"
AD1
AD2
Summary of Contents for A7533A - Brocade 4Gb SAN Switch Base
Page 1: ...HP StorageWorks Fabric OS 6 2 administrator guide Part number 5697 0016 Edition May 2009 ...
Page 24: ...24 ...
Page 99: ...Fabric OS 6 2 administrator guide 99 ...
Page 100: ...100 Managing user accounts ...
Page 118: ...116 Configuring standard security features ...
Page 164: ...162 Configuring advanced security features ...
Page 234: ...232 Installing and maintaining firmware ...
Page 268: ...266 Administering advanced zoning ...
Page 284: ...282 Configuring Enterprise class platforms ...
Page 292: ...290 Routing traffic ...
Page 294: ...292 Interoperability for merged SANs ...
Page 302: ...300 Configuring the Distributed Management Server ...
Page 334: ...332 iSCSI gateway service ...
Page 340: ...338 Administering NPIV ...
Page 407: ...Fabric OS 6 2 administrator guide 405 ...
Page 408: ...406 Using the FC FC routing service ...
Page 438: ...434 Administering extended fabrics ...
Page 460: ...456 Administering ISL trunking ...
Page 516: ...512 FICON fabrics ...
Page 526: ...522 Configuring and monitoring FICON Extension Services ...
Page 540: ...536 Configuring the PID format ...
Page 544: ...540 Understanding legacy password behavior ...
Page 546: ...542 Mixed fabric configurations for non merge SANs ...
Page 550: ...546 Migrating from an MP Router to a 400 MP Router ...
Page 558: ...554 Inband Management ...
Page 572: ...568 ...