HP StorageWorks 4/32 HP StorageWorks Fabric OS 5.2.x administrator guide (5697 - Page 114
Notes on joining a switch to the fabric, To set the fabric-wide consistency policy
View all HP StorageWorks 4/32 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 114 highlights
The following example shows a not defined fabric-wide consistency policy. switch:admin> fddcfg --showall Local Switch Configuration for all Databases:- DATABASE - Accept/Reject SCC - accept DCC - accept PWD - accept Fabric Wide Consistency Policy:- "" To set the fabric-wide consistency policy 1. Connect to the switch and log in. 2. Enter the following command: fddCfg --fabwideset "" Where policy_ID is a semicolon-separated list database_setting;database_setting equal to null Exclude the database ID from the list to set the policy to absent. database_id Sets a tolerant policy for a database. The database ID is either SCC or DCC. database_id:S Sets the policy to strict. The database ID is either SCC or DCC. The following examples show how to set a strict SCC and tolerant DCC fabric-wide consistency policy. switch:admin> fddcfg --fabwideset "SCC:S;DCC" switch:admin> fddcfg --showall Local Switch Configuration for all Databases:- DATABASE - Accept/Reject SCC - accept DCC - accept PWD - accept Fabric Wide Consistency Policy:- "SCC:S;DCC" Notes on joining a switch to the fabric When a switch is joined to a fabric with a tolerant SCC or DCC fabric-wide consistency policy, the joining switch must have a matching tolerant SCC or DCC fabric-wide consistency policy. If the tolerant SCC or DCC fabric-wide consistency policies do not match, the switch can join the fabric, but an error message flags the mismatch. If the tolerant 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 policies match, the switch joins the fabric successfully. If the ACL policies are absent 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 side to where they are absent. The Active policies set where they are present overwrite the Active and Defined policies set where they are absent. If the ACL policies do not match, the switch can join the fabric, but an error message flags the mismatch. Under both conflicting conditions, secPolicyActivate is blocked in the merged fabric. Use fddcfg -fabwideset command to resolve the fabric-wide consistency policy conflicts. Use the distribute command to explicitly resolve conflicting ACL policies. When a switch is joined to a fabric with a strict SCC or DCC fabric-wide consistency policy, the joining switch must have a matching fabric-wide consistency policy. If the strict SCC or DCC fabric-wide consistency policies do not match, the switch cannot join the fabric and the neighboring E_ports will be 114 Configuring advanced security