HP StorageWorks Fabric OS 5.3.x administrator guide (5697-0244, November 2009)

Fabric OS 5.3.0 administrator guide 147
Table 43 describes the impact of merging fabrics with the same fabric-wide consistency policy that have
SCC, DCC, or both policies.
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 44 shows merges that are not supported.
Table 43 Merging fabrics with matching fabric-wide consistency policies
Fabric-wide
consistency
policy
Fabric A
ACL policies
Fabric B
ACL policies
Merge
results
Database copied
None None None Succeeds No ACL policies copied.
None SCC/DCC Succeeds No ACL policies copied.
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
.
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.
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.
Table 44 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