Lsan Zone Configuration; Use Of Admin Domains With Lsan Zones And Fc-Fc Routing; Zone Definition And Naming - HP SN3000B Administrator's Manual

After initiation, the first port from the trunk group that comes online is designated as the master
port. The other ports that come online on the trunk group are considered the slave ports. Adding or
removing a slave port does not cause frame drop; however, removing a slave port causes the loss
of frames in transit.
The restrictions for EX_Port frame trunking are the same as for E_Ports—all the ports must be
adjacent to each other using the clearly marked groups on the front of the product.
ATTENTION
This feature should be enabled only if the entire configuration is running Fabric OS v5.2.0 or later.
If router port cost is used with EX_Port trunking, the master port and slave ports share the router
port cost of the master port.
For information about setting up E_Port trunking on an edge fabric, refer to
Trunking

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

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
not need to consider the zones in Edge SAN 2, and vice versa.
Fabric OS Administrator's Guide
53-1002446-01
Connections".
Chapter 17, "Managing Administrative
Figure 74 on page 471, when the zones for Edge SAN 1 are defined, you do
LSAN zone configuration
Chapter 22, "Managing
Domains".
24
485