Brocade Secure Fabric OS Administrator's Guide - Supporting Fabric OS v3.2.0, v4.4.0, v5.0.1, v5.1.0, 5.2.0, and 5.3.0 (53-1000244-02, June 2007)

Secure Fabric OS Administrator’s Guide 55

53-1000244-02

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 56 and “Activating Changes to Secure Fabric OS Policies” on page 56.

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.

You can create multiple sessions 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 saved in volatile memory only 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 56

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 56

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 56

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 57

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.

• “Deleting a Policy” on page 57

Delete an entire policy; however, keep in mind that doing so opens up that aspect of the fabric

to all access.

• “Aborting All Uncommitted Changes” on page 58

Abort all the changes to the Secure Fabric OS policies since the last time changes were saved

or activated.

• “Aborting a Secure Fabric OS Transaction” on page 58

From any switch in the fabric, abort a Secure Fabric OS-related transaction that has become

frozen (such as due to a failed host) and is preventing other Secure Fabric OS transactions.

Each of these tasks is described in the subsections that follow.