Deployment Guide

LSAN information stored in FC routers, with and without LSAN zone binding (Continued)TABLE 94
Without LSAN zone binding With LSAN zone binding
LSAN 1
LSAN 2
LSAN 3
LSAN 4
LSAN 1
LSAN 2
LSAN 3
LSAN 4
LSAN 1
LSAN 2
LSAN 3
LSAN 4
LSAN 1
LSAN 2
LSAN 3
LSAN 4
LSAN 1
LSAN 2
LSAN 2 LSAN 3
LSAN 4
LSAN 4
LSAN zone binding considerations
• Without LSAN zone binding, the maximum number of LSAN devices is 10,000.
• With LSAN zone binding, the metaSAN can import more than 10,000 devices and the backbone
fabric can support more FC routers.
• With LSAN zone binding, CPU consumption by an FC router is lower.
How LSAN zone binding works
LSAN zone binding uses an FC router matrix, which specifies pairs of FC routers in the backbone
fabric that can access each other, and an LSAN fabric matrix, which specifies pairs of edge fabrics
that can access each other.
You set up LSAN zone binding using the fcrLsanMatrix command. This command has two options: -
fcr and -lsan. The -fcr option is for creating and updating the FC router matrix, and the -lsan option is
used for creating and updating the LSAN fabric matrix.
NOTE
Best practice: Use this feature in a backbone fabric in which all FC routers are running Fabric OS
v6.1.0 or later.
When you set up LSAN zone binding on the local FC router (running Fabric OS v6.1.0 or later), the
resultant matrix database is automatically distributed to all of the Fabric OS v6.1.0 or later FC routers
in the backbone fabric. You do not need to set up LSAN zone binding on the other FC routers unless
those FC routers are running Fabric OS versions earlier than v6.1.0.
If a new FC router joins the backbone fabric, the matrix database is automatically distributed to that FC
router unless it has a different LSAN fabric matrix or FC router matrix or both defined already.
Note the following for FC routers running a Fabric OS version earlier than 6.1.0:
• The matrix database is not automatically distributed from this FC router to other FC routers.
• You must manually configure the LSAN fabric matrix on these FC routers to match the other FC
routers in the backbone fabric.
If you have a dual backbone configuration, where two backbone fabrics share edge fabrics, the LSAN
fabric matrix and FC router matrix settings for the shared edge fabrics must be the same on both
backbone fabrics. The matrix databases are not automatically propagated from one backbone fabric to
another, so you must ensure that both backbone fabrics have the same matrix settings.
NOTE
You can use LSAN zone binding along with LSAN tagging to achieve better scalability and
performance. Refer to LSAN zone policies using LSAN tagging on page 563 for information about
using the Enforce LSAN tag.
LSAN zone binding considerations
570 Fabric OS Administrators Guide
53-1003130-01