HP StorageWorks Fabric OS 5.2.x administrator guide (5697-0014, November 2009)

116 Configuring advanced security
Non-matching fabric-wide consistency policies
You may encounter one of the following two scenarios:
• Merging a fabric with a strict policy to a fabric with an absent, tolerant, or non-matching strict policy.
The merge fails and the ports are disabled.
Table 32 shows merges that are not supported:
• Merging fabrics with tolerant and absent policies. See Table 33 for examples:
Table 32 Examples of strict fabric merges
Fabric-wide consistency policy setting Expected behavior
Fabric A Fabric B
Strict/Tolerant SCC:S;DCC:S SCC;DCC:S Ports connecting switches are disabled.
SCC;DCC:S SCC:S;DCC
Strict/Absent SCC:S;DCC:S
SCC:S
DCC:S
Strict/Strict SCC:S DCC:S
Table 33 Fabric merges with tolerant/absent combinations
Fabric-wide consistency policysetting Expected behavior
Fabric A Fabric B
Tolerant/Absent SCC;DCC Error message logged.
Run fddCfg --fabwideset
“<policy_ID>” from any switch
with the desired configuration to fix
the conflict. The
secPolicyActivate command
is blocked until conflict is resolved.
DCC
SCC;DCC SCC
DCC SCC