HP StorageWorks Fabric OS 6.2 administrator guide (5697-0016, May 2009)

Fabric OS 6.2 administrator guide 119
and switches that are not listed in that policy. You can 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.
• ”Policy database distribution” on page 139 discusses the configuration of a switch to accept or reject
the distribution of polices.
• ”ACL policy distribution to other switches” on page 142 discusses the configuration of the distribution of
policies to switches within the fabric.
Displaying ACL policies
1. Connect to the switch and log in using an account assigned to the admin role.
2. Enter the secPolicyShow command:
switch:admin> secPolicyShow
____________________________________________________
ACTIVE POLICY SET
____________________________________________________
DEFINED POLICY SET
FCS policies
Fabric Configuration Server (FCS) policy in base Fabric OS may be performed on a local switch basis and
may be performed on any switch in the fabric with Fabric OS 6.0.0 or later. Any switch with a pre-5.3.0
version of Fabric OS cannot be included in the FCS list.
The FCS policy is not present by default, but must be created. When the FCS policy is created, the WWN
of the local switch is automatically included in the FCS list. Additional switches can be included in the FCS
list. The first switch in the list becomes the Primary FCS switch.
Only the Primary FCS switch is allowed to modify and distribute the database within the fabric. Automatic
distribution is supported, and you can either configure the switches in your fabric to accept the FCS policy
or manually distribute the FCS policy. Changes made to the FCS policy are saved to permanent memory
only after the changes have been saved or activated; they can be aborted later if you have set your fabric
to distribute the changes manually. Table 26 shows the characteristics of policy states.
The FCS policy is designed to accommodate mixed fabric environments that contain switches with
pre-5.3.0 and later versions of Fabric OS. By setting the configuration parameters to accept fabric
distribution, Fabric OS 6.0.0 and later switches may enforce FCS policy and perform database distribution
among 5.3.0 and 6.0.0 and later switches while still allowing pre-5.3.0 switches to join the fabric. The
following items describe distribution behavior for pre-5.3.0.
• Distribution to pre-5.3.0 switches with specific domain IDs
When specific domain IDs are given for the distribution, all domains must be on a switch with Fabric
OS 5.3.0 or later. If one of the domains is pre-5.3.0 the distribution operation will fail.
• Distribution to pre-5.3.0 switches using the wild card (*) character
When the wild card character is specified, distribution succeeds even if the fabric contains pre-5.3.0
switches. However, the FCS database is sent only to switches with a Fabric OS of 5.2.0 or later in the
Table 26 FCS policy states
Policy state Characteristics
No active policy Any switch can perform fabric-wide configuration changes.
Active policy with one entry A Primary FCS switch is designated (local switch), but there are no
backup FCS switches. If the Primary FCS switch becomes unavailable
for any reason, the fabric is left without an FCS switch.
Active policy with multiple
entries
A Primary FCS switch and one or more backup FCS switches are
designated. If the Primary FCS switch becomes unavailable, the next
switch in the list becomes the Primary FCS switch.