Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 195)

Zone merging scenarios: Default access mode (Continued) TABLE 36
Description Switch A Switch B Expected results
Enabled zone
configuration. No enabled configuration.
default zone = All Access
enabled: cfg2
default zone: All Access or No
Access
Clean merge. Enabled zone configuration and
default zone mode from Switch B propagates to
fabric.
Enabled zone
configuration. No enabled configuration.
default zone = No Access
enabled: cfg2
default zone: All Access
Fabric segments because Switch A has a
hidden zone configuration (No Access) activated
and Switch B has an explicit zone configuration
activated.
Enable zone configuration. enabled: cfg1
default zone: No Access
No enabled configuration.
default zone: No Access
Clean merge. Enabled zone configuration from
Switch A propagates to fabric.
Enable zone configuration. enabled: cfg1
default zone: All Access
No enabled configuration.
default zone: No Access
Fabric segments. You can resolve the zone
conflict by changing the default zone to No
Access on Switch A.
Configuring LSAN zones — device sharing example
The following example shows LSANs sharing devices in separate fabrics. The procedure illustrates the
creation of two LSAN zones (called lsan_zone_fabric_02 and lsan_zone_fabric_01), which involve the
following devices and connections:
• RBridge1 and the host in a Network OS fabric named fabric_01.
• Switch2, Target A, and Target B in a Fabric OS fabric named fabric_02.
• RBridge1 is connected by one of its FC_Ports to an EX_Port on the FC router.
• Switch2 is connected to the FC router using another EX_Port or VEX_Port.
• Host has WWN 10:00:00:00:c9:2b:c9:0c (connected to RBridge1).
• Target A has WWN 50:05:07:61:00:5b:62:ed (connected to switch2).
• Target B has WWN 50:05:07:61:00:49:20:b4 (connected to switch2).
The following illustration shows the connectivity.
Configuring LSAN zones — device sharing example
Network OS Administrator’s Guide 195
53-1003225-04