Non-Matching Fabric-Wide Consistency Policies - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

Table 43 describes the impact of merging fabrics with the same fabric-wide consistency policy that have
SCC, DCC, or both policies.
Table 43 Merging fabrics with matching fabric-wide consistency policies
Fabric-wide
consistency
policy
None
Tolerant
Strict
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

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 44 Examples of strict fabric merges
Fabric-wide consistency policy setting
Strict/Tolerant
Strict/Absent
Strict/Strict
Fabric A Fabric B
ACL policies ACL policies
None None
None SCC/DCC
None None
None SCC/DCC
SCC/DCC SCC/DCC
None None
None SCC/DCC
Matching Matching
SCC/DCC SCC/DCC
Different Different
SCC/DCC policies SCC/DCC policies
Fabric A Fabric B
SCC:S;DCC:S SCC;DCC:S
SCC;DCC:S SCC:S;DCC
SCC:S;DCC:S
SCC:S
DCC:S
SCC:S DCC:S
Merge Database copied
results
Succeeds No ACL policies copied.
Succeeds No ACL policies copied.
Succeeds No ACL policies copied.
Succeeds ACL policies are copied from B
to A.
Succeeds If A and B policies do not
match, a warning displays and
policy commands are
disabled
Succeeds No ACL policies copied.
Succeeds ACL policies are copied from B
to A.
Succeeds No ACL policies copied.
Fails Ports are disabled.
--
fabwideset and secpolicy activate are blocked.
Expected behavior
Ports connecting switches are
disabled.
Fabric OS 5.3.0 administrator guide 147
1
.