466 Fabric OS Administrator’s Guide
53-1001763-02
Backbone fabric IDs
21
InteropMode: Off
usage: InteropMode [0|2|3 [-z McDataDefaultZone] [-s McDataSafeZone]]
0: to turn interopMode off
2: to turn McDATA Fabric mode on
Valid McDataDefaultZone: 0 (disabled), 1 (enabled)
Valid McDataSafeZone: 0 (disabled), 1 (enabled)
3: to turn McDATA Open Fabric mode on
If InteropMode is on, FC routing is not supported. To turn off interoperability mode, disable the
switch and enter the interopMode 0 command, as described in “Enabling Brocade Native
mode” on page 305.
5. Verify that the Fabric Wide Consistency Policy is not in ‘strict’ mode by issuing the fddCfg
--showall command. When it is in strict mode, ACL cannot support Fibre Channel routing in
the fabric.
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 letter “S” in it in the edge fabric or the backbone
fabric, do not connect the edge fabric to the FC router. The letter “S” (shown in the preceding
sample output) indicates the policy is strict. The fabric-wide policy must be tolerant before you
can connect fabrics to the FC router. See Chapter 7, “Configuring Security Policies” for
information about configuring the fabric-wide consistency policy.

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 128. The default backbone fabric ID is 1 if
Virtual Fabrics is disabled.
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 must 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
must 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. When two backbone
fabrics are not connected to the same edge, they can have the same backbone fabric ID.
ATTENTION
In a multi-switch backbone fabric, modification of FID within the backbone fabric will cause
disruption to local traffic.