Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 563)

FC routers in the same backbone that support this feature. Verify the configured maximum limit
against the LSANs configured using the fcrResourceShow command.
HA and downgrade considerations for LSAN zones
Be aware of how LSAN zones impact high availability and firmware downgrades:
• The LSAN zone matrix is synchronized to the standby CP.
• On a dual CP switch, both CPs must have Fabric OS v5.3.0 or later.
• If the feature is enabled on the active CP, introducing a CP with an earlier version of Fabric OS as a
standby will cause HA synchronization to fail.
• If the feature is enabled, before downgrading to an earlier Fabric OS version, you will be asked to go
back to the default mode.
• This feature does not have any impact on current HA functionality. LSANs will be synchronized as
usual after the limit is increased and new LSANs are created.
LSAN zone policies using LSAN tagging
You can create tags for LSAN zones to give them a special meaning.
LSAN zones are zones with names that start with the "lsan_" prefix. You can specify a tag to append to
this prefix that causes the LSAN zone to be treated differently.
You can specify two types of tags:
• Enforce tag - Specifies which LSANs are to be enforced in an FC router.
• Speed tag - Specifies which LSANs are to be imported or exported faster than other LSANs.
The LSAN tags are persistently saved and support configupload and configdownload .
Enforce tag
Use the Enforce tag to achieve better scalability in the FC router by limiting the number of LSAN zones
that are enforced in that FC router.
The Enforce tag reduces the resources used in an FC router by limiting the number of LSAN zones that
will be enforced in that FC router. Use the Enforce tag to achieve better scalability in the FC router.
The Enforce tag is useful in the following scenarios:
• Multiple FC routers are connected to the same edge fabric.
• The backbone fabric contains multiple FC routers with multiple edge fabrics.
In these scenarios, often an FC router does not need to know about all edge fabrics and their respective
LSAN zones. You can use the Enforce tag to indicate which LSAN zones are imported by which FC
routers. Without the Enforce tag, all FC routers import all LSAN zones, even those that are not needed.
For example, the following figure shows a metaSAN with three FC routers in the backbone, and each
FC router has one edge fabric connected to it. In this scenario, LSAN zones communicate between
edge fabric 1 and edge fabric 2, and between edge fabric 2 and edge fabric 3. There is no
communication between edge fabric 1 and edge fabric 3.
HA and downgrade considerations for LSAN zones
Fabric OS Administrators Guide 563
53-1003130-01