Filter
Top Products
230 Fabric OS Administrator’s Guide
53-1002745-02
Policy database distribution
7
Non-matching fabric-wide consistency policies
You may encounter one of the following two scenarios described in Table 44 and Table 45 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 44 on page 230 shows merges that are not supported.
Table 45 has a matrix of merging fabrics with tolerant and absent policies.
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.
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.
TABLE 44 Examples of strict fabric merges
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
DCC:S
Strict/Strict SCC:S DCC:S
TABLE 45 Fabric merges with tolerant and absent combinations
Fabric-wide consistency policy setting Expected behavior
Fabric A Fabric B
Tolerant/Absent SCC;DCC Error message logged.
Run fddCfg --fabwideset “policy_ID” from any
switch with the desired configuration to fix the
conflict. The secPolicyActivate command is blocked
until conflict is resolved.
DCC
SCC;DCC SCC
DCC SCC
TABLE 43 Merging fabrics with matching fabric-wide consistency policies (Continued)
Fabric-wide
consistency policy
Fabric A
ACL policies
Fabric B
ACL policies
Merge
results
Database copied