HP AA979A - StorageWorks SAN Switch 2/8V, Administrator'S Manual, Page: 245 / 465

Fabric OS 5.3.0 administrator guide 247
Fabric ID: 75 Zone Name: lsan_zone_fabric75
10:00:00:00:c9:2b:c9:0c EXIST
50:05:07:61:00:5b:62:ed Imported
- fcrPhyDevShow shows the physical devices in the LSAN.
switch:admin> fcrphydevshow
Device WWN Physical
Exists PID
in Fabric
-----------------------------------------
75 10:00:00:00:c9:2b:c9:0c c70000
2 50:05:07:61:00:5b:62:ed 0100ef
2 50:05:07:61:00:5b:62:ed 0100e8
Total devices displayed: 3
- fcrProxyDevShow shows the proxy devices in the LSAN.
switch:admin> fcrproxydevshow
Proxy WWN Proxy Device Physical State
Created PID Exists PID
in Fabric in Fabric
----------------------------------------------------------------------------
75 50:05:07:61:00:5b:62:ed 01f001 2 0100e8 Imported
2 10:00:00:00:c9:2b:c9:0c 02f000 75 c70000 Imported
Total devices displayed: 2
On the 4/256 SAN Director with a B-Series MP Router blade, the host and Target A are imported,
because both are defined by lsan_zone_fabric2 and lsan_zone_fabric75 . However, target B defined by
lsan_zone_fabric75 is not imported because lsan_zone_fabric2 does not allow it.
When a PLOGI, PDISC, or ADISC arrives at the 4/256 SAN Director with a B-Series MP Router blade, the
SID and DID of the frame are checked. If they are LSAN-zoned at both SID and DID edge fabrics, the frame
will be forwarded to the DID. If they are not zoned, only the PLOGI is dropped; for the remaining frames
zoning enforcement takes place in the edge fabrics.
LSAN zone binding (optional)
By default, the Fibre Channel routers (FCR) in the backbone maintain the entire LSAN zone and device
state database. On Fibre Channel routers with Fabric OS 5.3.0 or later, the LSAN zone binding allows you
to specify pairs of edge fabrics that share devices, effectively creating an LSAN fabric matrix . The Fibre
Channel router uses this information to store only the LSAN zone entries of the remote edge fabrics that can
access its local edge fabrics and also to search and do a pair match only against the specified edge
fabrics. The advantage is that an individual Fibre Channel router may store fewer LSAN zone entries, and
the LSAN zone limit supported in the backbone will not be limited by the capability of one FCR. In
addition, the pair match calculation that establishes the devices import/export states will consume less
CPU time since the pair match will be done within the specified fabric boundaries and not against all the
edge fabrics in the backbone. If you choose not to implement this feature, the LSAN zone retains its default
behavior.
If you decide to implement LSAN zone binding, then the imported devices in the metaSAN is not limited by
the 10,000 LSAN device entries. Due to the lower LSAN count, the CPU consumption used by the Fibre
Channel router will be lower. If you configure the metaSAN such that the backbone has two groups of
FCRs such that there are no LSAN zone sharing and devices access between the two groups, the number
of Fibre Channel routers and devices supported in the backbone can be higher.
The command
fcrlsanmatrix
is used to specify pairs of edge fabric IDs that will share devices. Those
edge fabrics will have access only to the edge fabrics associated to them using this command. This LSAN
fabric matrix is saved persistently and referred to as static binding. The edge fabrics that were not specified
will have access to the rest of the other edge fabrics that were not specified. This association of the edge
fabric IDs is called default or dynamic binding, which is the default behavior. Using this information, the
FCR switch will maintain the remote LSAN Zone and the device state database only if it is associated to its
local edge fabrics.