Filter
Top Products
Fabric OS Administrator’s Guide 163
53-1001763-02
Policy database distribution
7
Matching fabric-wide consistency policies
This section describes the interaction between the databases with active SCC and DCC policies
and combinations of fabric-wide consistency policy settings when fabrics are merged.
For example: Fabric A with SCC:S;DCC (strict SCC and tolerant DCC) joins Fabric B with SCC:S;DCC
(strict SCC and tolerant DCC), the fabrics can merge as long as the SCC policies match, including
the order SCC:S;DCC and if both are set to strict.
Table 38 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 described in Table 39 and Table 40 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 39 on page 164 shows merges that are not supported.
TABLE 38 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 secPolicyActivate 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.