HP StorageWorks 8/8 HP StorageWorks Fabric OS 5.2.x administrator guide (5697- - Page 115
Matching fabric-wide consistency policies
View all HP StorageWorks 8/8 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 115 highlights
disabled. If the strict SCC and DCC fabric-wide consistency policies match, the corresponding SCC and DCC ACL policies are compared. The enforcement of fabric-wide consistency policy involves comparison of only the Active policy set.If the ACL polices match, the switch joins the fabric successfully. If the ACL policies are absent either on the switch or on the fabric, the switch joins the fabric successfully, and the ACL policies are copied automatically from where they are present to where they are absent. The Active policy set where it is present overwrites the Active and Defined policy set where it is absent. If the ACL policies do not match, the switch cannot join the fabric and the neighboring E_ports will be disabled. Use the fddcfg -fabwideset command on either this switch or the fabric to set a matching strict SCC or DCC 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 applies to joining two fabrics. In this context, the joining switch in the above descriptions becomes a joining fabric. NOTE: The existing SCC policy in the adjacent or joining switch are enforced before the fabric-wide consistency policy is applied. The next sections describe the interaction between the databases with active SCC and DCC policies and combinations of fabric-wide consistency policy settings when fabrics are merged. Matching fabric-wide consistency policies 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 (both are strict). Table 31 describes the impact of merging fabrics with the same fabric-wide consistency policy that have SCC and/or DCC policies. Table 31 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 Tolerant None None None None SCC/DCC None SCC/DCC None SCC/DCC SCC/DCC Succeeds Succeeds Succeeds Succeeds Succeeds 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 don't match, a warning displays and policy commands are disabled1. Strict None None Succeeds No ACL policies copied. None Matching SCC/DCC SCC/DCC Matching SCC/DCC Succeeds Succeeds ACL policies are copied from B to A. No ACL policies copied. Different Different Fails SCC/DCC SCC/DCC policies policies 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. Fabric OS 5.2.x administrator guide 115