HP StorageWorks Secure Fabric OS 5.0.0 User Guide (AA-RW1UA-TE, May 2005)

83Secure Fabric OS 5.0.0 user guide
If neither of these commands is entered, the changes are lost when the session is logged
out. For more information about these commands, see ”Saving changes to Secure Fabric
OS policies” on page 84 and ”Activating changes to Secure Fabric OS policies” on
page 84.
For example, to create an SCC policy that allows switches that have domain IDs 2 and 4
to join the fabric:
Managing Secure Fabric OS policies
All Secure Fabric OS transactions must be performed through the primary FCS switch only,
except for the secTransAbort, secFCSFailover, secStatsReset, and
secStatsShow commands.
Multiple sessions can be created to the primary FCS switch from one or more hosts. However,
the software allows only one Secure Fabric OS transaction at a time. If a second Secure
Fabric OS transaction is started, it fails. The only secondary transaction that can succeed is
the secTransAbort command.
All policy modifications are only saved in volatile memory until the changes are saved or
activated.
The following functions can be performed on existing Secure Fabric OS policies:
• ”Saving changes to Secure Fabric OS policies” on page 84
Save changes to flash memory without actually implementing the changes within the
fabric. This saved but inactive information is known as the "defined policy set."
• ”Activating changes to Secure Fabric OS policies” on page 84
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 85
Add one or more members to a policy. The aspect of the fabric covered by each policy is
closed to access by all devices/switches that are not listed in that policy.
• ”Removing a member from a policy” on page 86
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. The last member of the FCS_POLICY
cannot be removed, because a primary FCS switch must be designated.
primaryfcs:admin> secpolicycreate "SCC_POLICY", “2;4”
SCC_POLICY has been created