HP A7533A - Brocade 4Gb SAN Switch Base, Administrator'S Manual

Page: 124 / 576

122 Configuring advanced security features
For example, to move a backup FCS switch from position 2 to position 3 in the FCS list, using
interactive mode:
primaryfcs:admin> secpolicyfcsmove
PosPrimary WWN DIdswName.
=================================================
1 Yes 10:00:00:60:69:10:02:181switch5.
2 No 10:00:00:60:69:00:00:5a2switch60.
3 No 10:00:00:60:69:00:00:133switch73.
Please enter position you’d like to move from : (1..3) [1] 2
Please enter position you’d like to move to : (1..3) [1] 3
____________________________________________________
DEFINED POLICY SET
FCS_POLICY
PosPrimaryWWN DIdswName
__________________________________________________
1 Yes 10:00:00:60:69:10:02:181switch5.
2 No 10:00:00:60:69:00:00:133switch73.
3 No 10:00:00:60:69:00:00:5a2switch60.
____________________________________________________
4. Enter the
secPolicyActivate
command to activate and save the new order.
FCS policy distribution
The FCS policy can be automatically distributed using the
fddCfg
--
fabwideset
command or it can
be manually distributed to the switches using the
distribute -p
command. Each switch that receives
the FCS policy must be configured to receive the policy. To configure the switch to accept distribution of the
FCS policy, see ” Database distribution settings ” on page 140.
Switches in the fabric are designated as either a Primary FCS, backup FCS, or non-FCS switch. Database
distributions may be initiated only from the Primary FCS switch. FCS policy configuration and management
is performed using the command line or a manageability interface.
Only the Primary FCS switch is allowed to distribute the database. The FCS policy may need to be
manually distributed across the fabric using the
distribute -p
command if there is no support for
automatic distribution in a mixed environment with 5.3.0 and pre-5.3.0 switches. Since this policy is
distributed manually, the command
fddCfg –-fabwideset
is used to distribute a fabric-wide
consistency policy for FCS policy in an environment consisting of only Fabric OS 6.0.0 and later switches.
FCS enforcement for the
distribute
command is handled differently for FCS and other databases in an
FCS fabric:
• For an FCS database, the enforcement allows any switch to initiate the distribution. This is to support
FCS policy creation specifying a remote switch as Primary.
• For other database distributions, only the Primary FCS switch can initiate the distribution.
There is an FCS enforcement at the receiving switch, so the switch will verify whether the distribution is
coming from the Primary FCS switch before accepting it. Distribution is accepted only if it is coming from a
Primary FCS switch. Distribution of FCS policy can still be accepted from a backup FCS switch if the
Primary is not reachable or from a non-FCS switch if the Primary FCS and none of the backup FCS switches
are reachable. To learn more about how to distribute policies, see ” ACL policy distribution to other
switches ” on page 142.
NOTE: The FCS policy distribution is allowed from a switch in the FCS list. However, if none of the FCS
switches in the existing FCS list are reachable, receiving switches accept distribution from any switch in the
fabric.
Local switch configuration parameters are needed to control whether a switch accepts or rejects
distributions of FCS policy and whether the switch is allowed to initiate distribution of an FCS policy. A