HP Fabric OS 7.1.0, Administrator'S Manual

Page: 590 / 666

590 Fabric OS Administrator’s Guide
53-1002745-02
LSAN zone configuration
24
For information about setting up E_Port trunking on an edge fabric, refer to Chapter 22, “Managing
Trunking Connections” .
LSAN zone configuration
An LSAN consists of zones in two or more edge or backbone fabrics that contain the same devices.
LSANs provide selective device connectivity between fabrics without forcing you to merge those
fabrics. FC routers provide multiple mechanisms to manage inter-fabric device connectivity through
extensions to existing switch management interfaces. You can define and manage LSANs using
Brocade Advanced Zoning.
NOTE
For performance reasons, Brocade recommends that you do not configure LSANs for device sharing
between Fabric OS fabrics until after you activate the Integrated Routing license.
Use of Admin Domains with LSAN zones and FC-FC routing
You can create LSAN zones as a physical fabric administrator or as an individual Admin Domain
(AD) administrator. The LSAN zone can be part of the root zone database or the AD zone database.
FCR harvests the LSAN zones from all administrative domains. If both edge fabrics have the
matching LSAN zones and both devices are online, FCR triggers a device import. To support legacy
applications, WWNs are reported based on the Admin Domain context. As a result, you must not
use the network address authority (NAA) field in the WWN to detect an FC router. LSAN zone
enforcement in the local fabric occurs only if the Admin Domain member list contains both of the
devices (local and imported device) specified in the LSAN zone.
For more information, refer to Chapter 17, “Managing Administrative Domains” .
Zone definition and naming
Zones are defined locally on a switch or Backbone. 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 575, 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 must 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 not case-sensitive; 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.