HP StorageWorks Fabric OS 6.1.1 administrator guide (5697-0235, December 2009)

Fabric OS 6.1.x administrator guide 319
5. Issue 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, issue the interopMode 0 command to turn it off.
6. Issue 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, issue 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 ”Configuring advanced security features” on page 107
for information about configuring the fabric-wide consistency policy.
Assigning backbone fabric IDs
If your configuration has only one backbone fabric, 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.