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

134 Configuring advanced security features
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 38 shows merges that are not supported.
Table 39 has a matrix of merging fabrics with tolerant and absent policies.
Tolerant None None Succeeds No ACL policies copied.
None SCC/DCC Succeeds ACL policies are copied from
B to A.
SCC/DCC SCC/DCC Succeeds If A and B policies do not
match, a warning displays
and policy commands are
disabled
1
.
Strict None None Succeeds No ACL policies copied.
None SCC/DCC Succeeds ACL policies are copied from
B to A.
Matching
SCC/DCC
Matching
SCC/DCC
Succeeds No ACL policies copied.
Different
SCC/DCC
policies
Different
SCC/DCC
policies
Fails Ports are disabled.
1. To resolve the policy conflict, manually distribute the database you want to use to the switch with the mismatched
database. Until the conflict is resolved commands such as fddcfg --fabwideset and secpolicy activate are blocked.
Table 37 Merging fabrics with matching fabric-wide consistency policies (continued)
Fabric-wide
consistency policy
Fabric A
ACL policies
Fabric B
ACL policies
Merge
results
Database copied
Table 38 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