Table 40 Merging Fabrics With Matching Fabric-Wide Consistency Policies - HP SN3000B Administrator's Manual

Use the fddCfg
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
have SCC, DCC, or both policies.
TABLE 40
Fabric-wide
consistency policy
None
Tolerant
Strict
1.
database. Until the conflict is resolved, commands such as fddCfg
blocked.
Non-matching fabric-wide consistency policies
You may encounter one of the following two scenarios described in
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
Fabric OS Administrator's Guide
53-1002446-01
fabwideset command on either this switch or the fabric to set a matching strict
–-
describes the impact of merging fabrics with the same fabric-wide consistency policy that
Merging fabrics with matching fabric-wide consistency policies
Fabric A
ACL policies
None
None
None
None
SCC/DCC
None
None
Matching SCC/DCC
Different SCC/DCC
policies
To resolve the policy conflict, manually distribute the database you want to use to the switch with the mismatched
on page 166 shows merges that are not supported.
Policy database distribution
Fabric B Merge
ACL policies results
None Succeeds
SCC/DCC Succeeds
None Succeeds
SCC/DCC Succeeds
SCC/DCC Succeeds
None Succeeds
SCC/DCC Succeeds
Matching SCC/DCC Succeeds
Different SCC/DCC Fails
policies
fabwideset and secPolicyActivate are
--
Database copied
No ACL policies copied.
No ACL policies copied.
No ACL policies copied.
ACL policies are copied from B to A.
If A and B policies do not match, a
warning displays and policy
1
commands are disabled .
No ACL policies copied.
ACL policies are copied from B to A.
No ACL policies copied.
Ports are disabled.
Table 41 and Table 42 where
7
165