LSAN again: A logical network that spans multiple fabrics. The output reveals what devices are ❾xported (Exist) and Imported from all the routed fabrics.Įxported 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). 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 Shared devices must exist in both fabrics LSAN zones. LSAN zones in routed fabrics sharing devices are not required to have identical membership. LSAN zone name on the routed fabrics do not need to be identical, but is recommended for LSAN zone members must be defined using the device Port WWN, Zone members, including aliases, need to be defined using WWPN. The router performs zoning enforcement for edge fabrics at the ingress Router EX Port. LSAN zones must be configured in all fabrics where the shared physical devices exist. FC Router uses LSAN zones to determine which devices need to be exported/imported into which routed fabrics. LSAN zones are architecturally comaptiable with FOS and M-EOS Zone names must start with ¿LSAN_¿ or ¿lsan_¿ or ¿LSan_¿ A LSAN zone is a traditional zone with a special naming convention. It allows specified devices from the autonomous fabric to communicate with each other using a FC router without merging the physical fabrics. In other word, A logical network that spans multiple physical fabrics. Puppan Please remember to give points if I answered your queriesĪn 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. For ex if u want to share the tape drive to hosts in DC2-F2 and DC3-F1 If u have a 3 DC solution like I have, you will have to create seperate LSAN's to share the same resource to 2 fabrics. Ideally have only one initiator and one target and not more, but there is no restriction.ģ. An LSAN should have atleast one initiator and one target. Naming convention shd follow LSAN_FabricName_InitiatorName_FabricName_TargetNameĢ. LSAN's ideally should be named the same (not compulsary). To share a target (ex: tape drive) in Fabric 1 in DC1 to a server (initiator) in Fabric 2 in DC2, you need to create a LSAN in both fabrics.
![brocade san switch create zone cli brocade san switch create zone cli](https://exchangeengine.files.wordpress.com/2011/05/cfgshow.png)
You have to designate a port on the MPR as EX, and once u do this, although data frames can pass via the MPR, the RSCN's responsible for fabric merge are suppressed. MPR's restrict the type of RSCN's propgated, with the help of special port EX. If you do this, you are actually merging the 2 fabrics.
![brocade san switch create zone cli brocade san switch create zone cli](https://www.bujarra.com/wp-content/uploads/2009/07/fcsw23.jpg)
Just to make it more clear, the other option to scale out, is to connect the 2 switches in either fabrics. You need a MPR or a FR4-18i blade in the 48K to be able to connect the 2 fabrics - yet keep them unmerged.