HP StorageWorks Fabric OS 6.x administrator guide (5697-0015, May 2009)

Fabric OS 6.x administrator guide 237
The fcrlsancount command assumes that all the FCRs in the same LSAN fabric matrix or backbone have
the same maximum LSAN count defined, to protect all the FCRs from running into indefinite state.
Asymmetric LSAN configurations due to different maximum LSAN counts could lead to different devices
being imported on different FCRs.
The following example shows the use of the fcrlsancount command that allows you to display the current
LSAN limit or to set the maximum LSAN Zone count:
To display the current LSAN limit:
switch:admin> fcrlsancount
LSAN Zone Limit 3000
To set the new LSAN zone limit:
switch:admin> fcrlsancount 5000
LSAN Zone Limit 5000
For information on how to display the new maximum LSAN count after it has been changed, see
”Monitoring resources” on page 239.
NOTE: Since the maximum number of LSANs is configured per switch, if there is a different maximum
LSAN count on the switches throughout the metaSAN, then the device import/export will not be identical
on the FCRs. You should enter the same maximum LSAN count for all the FCR switches 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 ”To set up LSAN zone binding:” on page 236. However, instead of configuring the LSAN in the
second edge fabric, configure the LSAN in the backbone fabric.
HA and downgrade considerations
• The LSAN zone matrix is synchronized to the standby CP.
• On a dual CP switch, both CPs need to have the 5.3.0 code 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 fail the HA synchronization.
• 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.
IPFC over FCR
IPFC over FCR supports IP device communication between edge-to-edge fabrics and edge-to-backbone
fabrics. For IPFC over FCR to work, the FC router must be able to receive and forward broadcast frames
from edge and backbone fabrics. To route broadcast frames to edge fabrics or the backbone fabric, FCR
maintains a link state database (LSDB) and broadcast tree per edge fabric. The LSDB is a database that
contains link state records (LSR) of all the switches in edge fabrics. Using data from the LSDB, the FC router
constructs a broadcast tree and routes the frame to the destination using the shortest path of the broadcast
tree. The IPFC over FCR feature does not require any additional licensing.
If switches in edge fabrics and the backbone fabric have Fabric OS v5.3.0 and later, a broadcast zone
must be configured to share IP devices. Only devices in the broadcast zone will be able to receive
broadcast frames. Broadcast zoning is supported only in 5.3.0 and later.
In 5.1.x and 5.2.x where broadcast zones are not implemented, all devices will be able to receive the
broadcast packet. If it is required to set up a broadcast zone, the broadcast zone must include the IP device
that exists in that edge or backbone fabric and the proxy device of the remote IP device.