Configuring Backbone Fabrics For Interconnectivity; Ha And Downgrade Considerations; Ipfc Over Fcr; Broadcast Configuration - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

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
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 v5.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.
• If the active CP is running v5.3.0 and the standby CP is running v5.2.0 or earlier, you will not be
allowed to increase the maximum LSAN count above 3000. An error will be returned.
If the active CP is running v5.3.0 with the maximum LSAN count set to be more than 3000, and a
•
standby CP with v5.2.x/v5.1.x comes online, HA sync will not be established. A RASLog message will
be logged to indicate the reason for the HA being out of sync.
• If the active CP is running v5.3.0 with a 3000 maximum LSAN count and the standby CP is running
v5.1.0 that supports a 1000 maximum LSAN count, when the LSAN entries on the v5.3.0 active CP
reaches 1000, a RASLog warning will be logged to indicate that the standby CP with Fabric OS v5.1.0
does not support more than 1000 LSANs.

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, 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 v5.3.0.
In v5.1.x and v5.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.
In the FC router use the command fcrbcastconfig to prevent inter-fabric forwarding of broadcast
frames of edge or backbone fabrics.
Using the fcrbcastconfig command, you can disable or enable the broadcast frame forwarding
option per FID (edge fabric or backbone fabric).

Broadcast configuration

To enable broadcast frames across the FC router, the IP devices must be LSAN zoned. By default, the edge
fabrics and the backbone fabric of the FC router have the broadcast frame receiving and forwarding
option enabled. Users with Admin and switchAdmin permission can change the broadcast configuration
using the fcrbcastconfig command. Thus multi-protocol devices can be configured to send broadcast
frames to edge fabrics but not to others. For example, broadcast frames can be routed or prevented to
route from edge-to-edge, backbone-to-edge, and edge-to-backbone fabrics.
Broadcast zoning can be used in an edge fabric to share IP devices. Only edge fabrics in the broadcast
zone will be able to receive broadcast frames. In v5.1.x and v5.2.x where broadcast zones are not
implemented, all the devices will be able to receive the broadcast packet. You can use the
250 Using the FC-FC routing service
binding, page 253. However, instead of configuring the LSAN in the