HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2 administrator guide (5697-0 - Page 147

Table 38 describes the impact of merging fabrics with the same fabric-wide consistency policy that have SCC, DCC, or both policies. 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 None SCC/DCC Succeeds No ACL policies copied 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 is displayed and policy commands are disabled1. Strict None None Succeeds No ACL policies copied. None SCC/DCC Succeeds ACL policies are copied from B to A. Matching SCC/DCC Different SCC/DCC policies Matching SCC/DCC Different SCC/DCC policies Succeeds No ACL policies copied. 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. 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 shows merges that are not supported. Table 39 Examples of strict fabric merges Fabric-wide consistency policy setting Expected behavior Polidy type Fabric A Fabric B Strict/Tolerant Strict/Absent SCC:S;DCC:S SCC;DCC:S SCC:S;DCC:S SCC;DCC:S SCC:S;DCC Ports connecting switches are disabled. Strict/Strict SCC:S DCC:S SCC:S DCC:S Table 40 shows a matrix of merging fabrics with tolerant and absent policies. Fabric OS 6.2 administrator guide 145