LSAN zones-- Brocade 7500

An LSAN is a Logical Storage Area Network that spans multiple Physical fabrics and allows specified devices from these autonomous fabrics to communicate with each other without merging the physical fabrics.

In other word, A logical network that spans multiple physical fabrics. It allows specified devices from the autonomous fabric to communicate with each other using a FC router without merging the physical fabrics.

- A LSAN zone is a traditional zone with a special naming convention.
- Zone names must start with ¿LSAN_¿ or ¿lsan_¿ or ¿LSan_¿
- LSAN zones are architecturally comaptiable with FOS and M-EOS
- FC Router uses LSAN zones to determine which devices need to be exported/imported into which routed fabrics.
- LSAN zones must be configured in all fabrics where the shared physical devices exist.
- The router performs zoning enforcement for edge fabrics at the ingress Router EX Port.

LSAN Implementation Rules:

- LSAN zone members must be defined using the device Port WWN, Zone members, including aliases, need to be defined using WWPN.

- LSAN zone name on the routed fabrics do not need to be identical, but is recommended for

Administration and troubleshooting.

- LSAN zones in routed fabrics sharing devices are not required to have identical membership. Shared devices must exist in both fabrics LSAN zones.

Once the LSAN zones are enabled, you will be able to check status of LSAN zones and members from the FC Router using the command lsanzoneshow ¿s

Router:admin>lsanzoneshow ¿s
Fabric ID: 1 Zone Name: lsan_zone1
10:00:00:00:98:23:12:11 Exist
10:00:00:00:98:23:ab:cd Imported

Fabric ID: 2 Zone Name: lsan_zone1
10:00:00:00:98:23:12:11 Imported
10:00:00:00:98:23:ab:cd Exist

The output reveals what devices are ¿Exported (Exist) and Imported from all the routed fabrics.

Hope this helps.

hey KDBEWE,

Thanks a lot for ur help, i gave u the points, my question has been answered, but i have a quick question for you, you specified Imported and exported, what exactly those terms mean in this context?, and for eg. if i create a Lsan zone in one edge fabric, is there any need for me to create the same zone on other side i.e on the other edge fabric. I mean do we need to have same lsan zones on both the fabrics. if so why? and what about the configurations. Please help me in this regard.
Thanks in advance.

Exported device: A device that has been mapped between fabrics (a host or storage port in one edge fabric can be exported to any other fabric by using LSAN zoning).

LSAN again: A logical network that spans multiple fabrics. The path between devices in an LSAN can be local to an edge fabric or cross one or more Multiprotocol Routers and up to one intermediate backbone fabric. LSANs are administered through LSAN zones in each edge fabric.Logical Storage Area Network. Enables device and storage connectivity that spans two or more fabrics.

The mechanism by which LSANs are administered. A Multiprotocol Router
attached to two fabrics will "listen" for the creation of matching LSAN zones
on both fabrics. If this occurs, it will create phantom domains and FC-NAT
entries as appropriate, and insert entries for them into the name servers on
the fabrics. LSAN zones are compatible with standard zoning mechanisms.


LSAN device entry: the total number of port WWN entries for all devices defined in all active LSAN zones within a routed fabric.

For example, Fabric 1 has lsan_zone1 with device A & B and Fabric 2 has
lsan_zone 2 with device A & B. Four LSAN device entries are consumed

Hope the above answers your questions, other wise You may have to go for LSAN specific classes or given below the book...to understand it completely.

And there is this help too for further info
There is a very good book available to understand the MPRs and LSAN

Principles of SAN Design Book (2006 Edition) – Josh Judd & Dan Krueger

Available at Amazon and other stores.

Thanks & Regards

hey KD8EWE

yep, i am clear now,. thanks a lot for ur explanation..

Puppan one more tip

LSANs from configuration perspective procedure exactly looks like a zoning. Only difference from usual zones is they must to begin from ¿LSAN _¿ (case insensitive). You need to create such zones in the both fabrics.

FCIDs of devices in different fabrics can coincide. So LSAN zones membership is based only on WWNs and aliases.

Hope you are clear now.

Thanks for the points

Hi, Team. 

     I would like to ask regarding LSAN Configuration because the Virtual Fabric is enabled on SAN Environment.

FID125: DefaultSwitch

FID31: LogicalSwitch(For Host)

FID33: BaseSwitch(Base)

Kindly share please the configuration needed for each FID to ensure the LSAN will work?