HP A7533A - Brocade 4Gb SAN Switch Base, Administrator'S Manual

Page: 392 / 576

390 Using the FC-FC routing service
For information on how to display the maximum allowed and currently used LSAN zones and devices, see
” Resource monitoring ” on page 399.
NOTE: Since the maximum number of LSANs is configured for each switch, if there is a different
maximum LSAN count on the switches throughout the metaSAN, the device import/export will not be
identical on the FC routers. You should enter the same maximum LSAN count for all the FC routers in the
same backbone that support this feature. Verify the configured maximum limit against the LSANs
configured using the
fcrResourceShow
command.
Configuring backbone fabrics for interconnectivity
If you want devices in backbone fabrics to communicate with devices in edge fabrics, follow the steps in
the section ” Setting up LSAN zone binding ” on page 397. However, instead of configuring the LSAN in
the second edge fabric, configure the LSAN in the backbone fabric.
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 5.3.0 or later to enable the feature.
• 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
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. This is useful when multiple FC routers are
connected to the same edge fabric. Without the Enforce tag, all FC routers import all LSAN zones, even
those that are not needed.
Normally the FC router automatically accepts all zones with names that start with lsan_. You can specify
an Enforce tag to indicate that a particular FC router should accept only zones that start with the prefix
lsan_tag. For example, if you specify an Enforce tag of abc, the FC router accepts only those LSAN zones
that start with lsan_abc and does not import or export any other LSAN zones.
The Enforce tag can be up to 8 characters long and can contain only letters and numbers. The Enforce tag
is case-insensitive; for example, the tag abc is equivalent to ABC and Abc.
If you specify abc, xyz, and fab1 as Enforce tags, the FC router accepts only those LSAN zones with
names that start with any of the following: