
120 Configuring advanced security
Identifying policy members
Specify the FCS, DCC and SCC policy members by device port WWN, switch WWN, domain IDs, or
switch names, depending on the policy. The valid methods for specifying policy members are listed in
Table 30
.
Configuring ACL policies
All policy modifications are saved in volatile memory until those changes are saved or activated. You can
create multiple sessions to the switch from one or more hosts. However, Fabric OS allows only one ACL
transaction at a time. If a second ACL transaction is started, it fails.
The FCS, SCC and DCC policies in Secure Fabric OS are not interchangeable with Fabric OS FCS, SCC
and DCC policies. Uploading and saving a copy of the Fabric OS configuration after creating policies is
strongly recommended. Use the
configUpload
command to upload a copy of the configuration file. For
more information about this command, see the
Fabric OS Command Reference
.
NOTE:
All changes, including the creation of new policies, are saved and activated on the local switch
only—unless the switch is in a fabric that has a strict or tolerant fabric-wide consistency policy for the ACL
policy type for SCC or DCC. update See
“Distributing the policy database”
on page -142 for more
information on the database settings and fabric-wide consistency policy.
Use the instructions in the following sections to manage common settings between two or more of the DCC,
FCS, and SCC policies. For instructions relating to a specific policy, refer to the appropriate section.
•
“Displaying ACL policies”
on page 99
Displays a list of all active and defined ACL policies on the switch.
•
“Saving changes to ACL policies”
on page 107
Save changes to memory without actually implementing the changes within the fabric or to the switch.
This saved but inactive information is known as the “defined policy set.”
•
“Activating changes to ACL policies”
on page 107
Simultaneously save and implement all the policy changes made since the last time changes were
activated. The activated policies are known as the “active policy set.”
•
“Adding a member to an existing policy”
on page 107
Add one or more members to a policy. The aspect of the fabric covered by each policy is closed to
access by all devices and switches that are not listed in that policy.
•
“Removing a member from an ACL policy”
on page 108
Remove one or more members from a policy. If all members are removed from a policy, that aspect of
the fabric becomes closed to all access.
•
“Deleting an ACL policy”
on page 108
Delete an entire policy; deleting a policy opens up that aspect of the fabric to all access.
•
“Configuring the database distribution settings”
on page 123
Configure a switch to accept or reject the distribution of polices.
•
“Distributing ACL policies to other switches”
on page 124
Configure the distribution of policies to switches within the fabric.
Table 30
Valid methods for specifying policy members
Policy name
Device port
WWN
Switch
WWN
Domain ID Switch
name
FCS_POLICY
No
Yes
Yes
Yes
DCC_POLICY_
nnn
Yes
Yes
Yes
Yes
SCC_POLICY
No
Yes
Yes
Yes
Summary of Contents for AA979A - StorageWorks SAN Switch 2/8V
Page 1: ...HP StorageWorks Fabric OS 5 3 x administrator guide Part number 5697 0244 November 2009 ...
Page 16: ...16 ...
Page 20: ...18 ...
Page 24: ...24 Introducing Fabric OS CLI procedures ...
Page 116: ...118 Maintaining configurations ...
Page 170: ...172 Managing administrative domains ...
Page 200: ...202 Installing and maintaining firmware ...
Page 222: ...224 Routing traffic ...
Page 274: ...286 Administering FICON fabrics ...
Page 294: ...306 Working with diagnostic features ...
Page 350: ...362 Administering Extended Fabrics ...
Page 438: ...440 Configuring the PID format ...
Page 444: ...446 Configuring McData Open Fabric mode ...
Page 450: ...452 Understanding legacy password behaviour ...