Reference Guide

FCR 1 has the following zones:
FID 1: LSAN_A_RFID_2: dev1 dev2
FID 1: LSAN_B_RFID_4: dev1 dev4
FID 2: LSAN_RFID_1_A: dev2 dev1
FID 4: LSAN_A_RFID_1: dev4 dev1
FID 4: LSAN_B_RFID_3: dev3 dev4
FID 3: LSAN_B_RFID_4: dev3 dev4
FCR 2 has the following zones:
FID 2: LSAN_RFID_1_A: dev2 dev1
FID 2: LSAN_RFID_3_B: dev2 dev3
FID 1: LSAN_A_RFID_2: dev1 dev2
FID 1: LSAN_B_RFID_4: dev1 dev4
FID 4: LSAN_A_RFID_1: dev4 dev1
FID 4: LSAN_B_RFID_3: dev3 dev4
FID 3: LSAN_RFID_2_A: dev3 dev2
FID 3: LSAN_RFID_4_B: dev3 dev4
FCR 3 has the following zones:
FID 3: LSAN_RFID_2_A: dev3 dev2
FID 3: LSAN_RFID_4_B: dev3 dev4
FID 2: LSAN_RFID_3_B: dev2 dev3
FID 4: LSAN_A_RFID_1: dev4 dev1
FID 4: LSAN_B_RFID_3: dev3 dev4
FID 1: LSAN_B_RFID_4: dev1 dev4
Migrating LSAN zones to location embedded LSAN zones in the edge fabric
You must identify a set of LSAN zones for which you want to embed the location. For such LSAN zones, you must reconfigure the
LSAN zones in the edge fabric by completing the following steps. Using this procedure, you can scale beyond the maximum limits in the
metaSAN.
1. In the FC router running a release prior to Fabric OS 7.4.0, use the lsanZoneShow –d –f <fid> command to find the remote
fabric ID from which devices are imported for each LSAN zone per configured edge fabric.
2. Rename the LSAN zone name by appending the special _RFID_”imported FID” tag.
3. If the LSAN zone has the devices that are imported from more than one edge fabric, split them into multiple LSAN zones
based on the number of imported fabrics in RFID_”imported FID” tag format and ensure that all newly created LSAN zones
have only those imported device pairs.
4. Once all the LSAN zones are converted into RFID_imported FID format, enable the zone configuration.
5. Repeat the previous steps in all the edge fabrics.
LSAN zones that are not configured with location information will operate as per legacy FC router behavior.
Limitations of location embedded LSAN zones
∙ Each FC router has different LSAN zones based on the location embedded in the LSAN zone name. If each FC router has
5000 LSANs, after firmware downgrade to a pre-7.4.0 version, any disruptive action in the metaSAN triggers import or export
issues because the pre-7.4.0 FC router accepts only the first 5000 LSAN zones. In such an FC router, you will notice the RAS
log FCR-1020 indicates that the FC router LSAN zones are exhausted. Also, the filter will apply depending on where the
pre-7.4.0 switch is in the backbone fabric.
∙ The location embedded LSAN zone feature is not applicable for backbone-to-edge fabric LSAN zones. If you configure an
RFID in a backbone fabric LSAN zone, it will not impact anything on resource utilization.
∙ The entries of fcrProxyDevShow –a, fcrPhyDevShow –a, and lsanZoneShow may not be same across FC routers in the
backbone fabric.
Using FC-FC Routing to Connect Fabrics
Brocade Fabric OS Administration Guide, 8.0.1
53-1004111-02 535