Non-Matching Fabric-Wide Consistency Policies; Examples Of Strict Fabric Merges - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

Table 37 Merging fabrics with matching fabric-wide consistency policies (continued)
Fabric-wide
consistency policy
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 --fabwideset and secpolicy activate are blocked.

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 38

Examples of strict fabric merges

Fabric-wide consistency policy setting
Strict/Tolerant
Strict/Absent
Strict/Strict
Table 39 has a matrix of merging fabrics with tolerant and absent policies.
134 Configuring advanced security features
Fabric A Fabric B
ACL policies ACL policies
None None
None SCC/DCC
SCC/DCC SCC/DCC
None None
None SCC/DCC
Matching Matching
SCC/DCC SCC/DCC
Different Different
SCC/DCC SCC/DCC
policies 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 ACL policies are copied from
B to A.
Succeeds If A and B policies do not
match, a warning displays
and policy commands are
1
disabled .
Succeeds No ACL policies copied.
Succeeds ACL policies are copied from
B to A.
Succeeds No ACL policies copied.
Fails Ports are disabled.
Expected behavior
Ports connecting switches are
disabled.