HP StorageWorks Fabric OS 6.1.x administrator guide (5697-0234, November 2009)

302 Using the FC-FC Routing Service
4. Enter the interopMode command and verify that Brocade switch interoperability with switches from
other manufacturers is disabled.
switch:admin> interopmode
InteropMode: Off
Usage: InteropMode 0|1
0: to turn it off
1: to turn it on
5. Enter the msPlatShow command to verify that Management Server Platform database is disabled in
the backbone fabric.
switch:admin_06> msplatshow
*MS Platform Management Service is NOT enabled.
If any of the items listed in the prior steps are enabled, you can see the Fabric OS Command Reference for
information on how to disable the option. For information about security, see ”Configuring standard
security features” on page 69 and ”Configuring advanced security features” on page 105.
When it is in strict mode, ACL cannot support Fibre Channel routing in the fabric. Before connecting an
edge fabric to an FC router and before setting up the FC router in the BB, verify that the Fabric Wide
Consistency Policy is not in ‘strict’ mode by issuing the fddCfg
--showall command.
switch:admin> fddcfg --showall
Local Switch Configuration for all Databases:-
DATABASE - Accept/Reject
---------------------------------------
SCC - accept
DCC - accept
PWD - accept
Fabric-Wide Consistency Policy :- "SCC:S;DCC"
If the Fabric Wide Consistency Policy has the ‘S’ letter in it in the edge fabric or the BB fabric, do not
connect the edge fabric or the BB to the FC router. See the Fabric OS Command Reference for details.
Assigning backbone fabric IDs
If your configuration has only one backbone fabric, then this task is not required because the backbone
fabric ID in this situation defaults to a value of 1.
All switches in a backbone fabric must have the same backbone fabric ID. You can configure the backbone
fabric ID using the fcrConfigure command. The backbone fabric ID is required to be unique from the
perspective of every attached edge fabric. Fabric ID changes made on a switch are not propagated to
other switches in the backbone fabric. Rather, the backbone fabric administrator is responsible for making
sure that all switches in the backbone have the same fabric ID. Because fabric IDs are used heavily by the
routing protocol between the Fibre Channel routers, using the wrong fabric ID can affect both
edge-to-edge and backbone-to-edge routing.
In addition to ensuring that the backbone fabric IDs are the same within the same backbone, you need to
make sure that when two different backbones are connected to the same edge fabric, the backbone fabric
IDs are different, but the edge fabric ID should be the same. Configuration of two backbones with the same
backbone fabric ID that are connected to the same edge is invalid. In this configuration, a RASLog
message displays a warning about fabric ID overlap. However, when two backbone fabrics are not
connected to the same edge, they can have the same backbone fabric ID.
IMPORTANT: In a multi-switch backbone fabric, modification of FID within the backbone fabric will cause
disruption to local traffic.