HP A7533A HP StorageWorks Fabric OS 6.1.1 administrator guide (5697-0235, Dece - Page 135

Table 37 describes the effect of merging fabrics with the same fabric-wide consistency policy that have SCC, DCC, or both policies. Table 37 Merging fabrics with matching fabric-wide consistency policies Fabric-wide Fabric A consistency policy 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 disabled1. 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 secpolicy activate are blocked. Non-matching fabric-wide consistency policies You may encounter one of the following two scenarios described in Table 38 and Table 39: Merging a fabric with a strict policy to a fabric with an absent, tolerant, or non-matching strict policy. The merge fails and the ports are disabled. Table 38 shows merges that are not supported. Table 38 Examples of strict fabric merges Fabric-wide consistency policy setting Fabric A Fabric B Strict/Tolerant SCC:S;DCC:S SCC;DCC:S SCC;DCC:S SCC:S;DCC Strict/Absent SCC:S;DCC:S SCC:S DCC:S Strict/Strict SCC:S DCC:S Expected behavior Ports connecting switches are disabled. Table 39 has a matrix of merging fabrics with tolerant and absent policies. Fabric OS 6.1.1 administrator guide 135