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

You can define and manage LSANs using the same zone management tools as for regular zones. The
FC router makes LSAN zoning possible by importing devices in effective zones. For example, consider
two devices:
• 11:22:33:44:55:66:77:99 is connected to a switch in a Brocade VCS Fabric cluster.
• 11:22:33:44:55:66:77:88 is connected to a switch in a Fabric OS fabric.
The FC-FC routing service on the FC router that connects the two fabrics presents
11:22:33:44:55:66:77:88 as a phantom device to the Brocade VCS Fabric and also presents
11:22:33:44:55:66:77:99 as a phantom device to the Fabric OS fabric. You can then use the regular
zone management tools on the Brocade VCS Fabric cluster to incorporate 11:22:33:44:55:66:77:99
into an LSAN zone on the Brocade VCS Fabric. Similarly, you can use the regular zone management
tools in Fabric OS to incorporate 11:22:33:44:55:66:77:88 into an LSAN zone in the Fabric OS fabric.
Once both the Brocade VCS Fabric zone and the Fabric OS zone are enabled, the FC router imports
devices common to both zones and makes them available to the zones in each fabric.
LSAN naming
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 WWNs of the devices to be shared. Although you manage an LSAN zone by using the
same tools as any other zone on the edge fabric, two behaviors distinguish an LSAN zone from a
conventional zone:
• A required naming convention. The name of an LSAN zone begins with the prefix "LSAN_". The
LSAN name is case-insensitive; for example, lsan_ is equivalent to LSAN_, Lsan_, and so on.
• LSAN zone members in all fabrics must be identified by their WWN. You cannot use the port IDs
that are supported only in Fabric OS fabrics.
NOTE
The "LSAN_" prefix must appear at the beginning of the zone name.
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.
Managing domain IDs
FCoE connectivity across the Fibre Channel link between Brocade VCS Fabric clusters and FC
routers uses domain IDs to identify switches. Within a Brocade VCS Fabric cluster, a domain ID is the
same as a routing bridge ID. When you connect to a Fibre Channel router, the FC Fabric Fibre
Channel router service emulates virtual phantom FC domains in the FCoE fabric. Each FCR-enabled
switch emulates a single "front" phantom domain and each FC fabric is represented by a translate
phantom domain.
It is important to ensure that front domain IDs and translate domain IDs presented by the FC router do
not overlap routing bridge IDs in the FCoE fabric; otherwise, the connectivity will fail and the Network
OS switch with the overlapping routing bridge ID becomes isolated from the fabric. To prevent
potential overlap, use the portCfgExport -d Fabric OS command on the FC router to apply a unique
front domain ID — one that will not be used in the FCoE fabric. Similarly, use the fcrXlateConfig
importedFID exportedFID preferredDomainID Fabric OS command to set the translate domain ID to a
unique value that is also not used as a routing bridge ID.
LSAN naming
170 Network OS Administrator’s Guide
53-1003225-04