Fabric OS Administrator's Guide v7.0.0 (53-1002148-02, June 2011)

Fabric OS Administrator’s Guide 167
53-1002148-02
Policy database distribution
7
Use the fddCfg –-fabwideset command on either this switch or the fabric to set a matching strict
SCC, DCC, or FCS fabric-wide consistency policy. Use ACL policy commands to delete the conflicting
ACL policy from one side to resolve ACL policy conflict. If neither the fabric nor the joining switch is
configured with a fabric-wide consistency policy, there are no ACL merge checks required.
The descriptions above also apply to joining two fabrics. In this context, the joining switch becomes
a joining fabric.
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 40 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 41 and Table 42 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 41 on page 168 shows merges that are not supported.
TABLE 40 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.