Fabric OS Administrator's Guide v7.0.0 (53-1002148-02, June 2011)

Fabric OS Administrator’s Guide 481
53-1002148-02
LSAN zone configuration
23
Zone definition and naming
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 76 on page 466, 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.
NOTE
The "LSAN_" prefix must appear at the beginning of the zone name. LSAN zones may not be
combined with QoS zones. See “QoS zones” on page 418 for more information about the naming
convention for QoS zones.
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.
Controlling device communication with the LSAN
The following procedure illustrates how LSANs control which devices can communicate with each
other. The procedure shows the creation of two LSANs (called lsan_zone_fabric75 and
lsan_zone_fabric2), which involve the following devices and connections:
• Switch1 and the host in fabric75.
• Switch2, Target A, and Target B in fabric2.
• Switch1 is connected to the FC router using an EX_Port or VEX_Port.
• 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 switch1).
• 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).