Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 243)

Merging fabrics with matching fabric-wide consistency policies TABLE 53
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.
10
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.
Non-matching fabric-wide consistency policies
You may encounter one of the following two scenarios described in Table 54 and Table 55 where you
are merging a fabric with a strict policy to a fabric with an absent, tolerant, or non-matching strict policy
and the merge fails and the ports are disabled.
Table 54 shows merges that are not supported.
Examples of strict fabric merges TABLE 54
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
SCC:S;DCC SCC:S
Strict/Absent SCC:S;DCC:S
SCC:S
10 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 secPolicyActivate are blocked.
Non-matching fabric-wide consistency policies
Fabric OS Administrators Guide 243
53-1003130-01