HP A7533A - Brocade 4Gb SAN Switch Base, Administrator'S Manual

Page: 379 / 576

Fabric OS 6.2 administrator guide 377
5. Enter the
interopMode
command and verify that Fabric OS switch interoperability with switches from
other manufacturers is disabled.
switch:admin> interopmode
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 interoperability mode is turned on, enter the
interopMode 0
command to turn it off.
6. 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 the MS platform database is enabled, enter the
msPlMgmtDeactivate
command to deactivate it.
7. 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 or the backbone 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 4, ” Configuring advanced security features ” on
page 117 for information about configuring the fabric-wide consistency policy.
Backbone FIDs
If your configuration has only one backbone fabric, this task is not required because the backbone FID in
this situation defaults to a value of 1.
All switches in a backbone fabric must have the same backbone FID. You can configure the backbone FID
using the
fcrConfigure
command. The backbone FID must be unique from the perspective of every
attached edge fabric. FID 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 FID. Because FIDs are used heavily by the routing protocol between the
Fibre Channel routers, using the wrong FID can affect both edge-to-edge and backbone-to-edge routing.
In addition to ensuring that the backbone FIDs 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 FIDs are
different, but the edge FID should be the same. Configuration of two backbones with the same backbone
FID that are connected to the same edge is invalid. In this configuration, a RASLog message displays a
warning about FID overlap. When two backbone fabrics are not connected to the same edge, they can
have the same backbone FID.