Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 216)

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, refer to
Database distribution settings on page 239.
Database distributions may be initiated from only 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 can be manually
distributed across the fabric using the distribute -p command. 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 v6.2.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.
The FCS policy distribution is allowed to be distributed 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. To learn more about how to distribute policies, refer to
ACL policy distribution
to other switches on page 240.
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
configuration parameter controls whether the distribution of the policy is accepted or rejected on the
local switch. Setting the configuration parameter to accept indicates distribution of the policy will be
accepted and distribution may be initiated using the distribute -p command. Setting the configuration
parameter to reject indicates the policy distribution is rejected and the switch may not distribute the
policy.
The default value for the distribution configuration parameter is accept, which means the switch
accepts all database distributions and is able to initiate a distribute operation for all databases.
Distribution policy states TABLE 42
Fabric OS State
v6.2.0 and later configured to accept Target switch accepts distribution and fabric state change occurs.
v6.2.0 and later configured to reject Target switch explicitly rejects the distribution and the operation fails. The
entire transaction is aborted and no fabric state change occurs.
Device Connection Control policies
Multiple Device Connection Control (DCC) policies can be used to restrict which device ports can
connect to which switch ports. The devices can be initiators, targets, or intermediate devices such as
SCSI routers and loop hubs. By default, all device ports are allowed to connect to all switch ports; no
DCC policies exist until they are created. For information regarding DCC policies and F_Port trunking,
refer to the Access Gateway Administrator's Guide.
FCS policy distribution
216 Fabric OS Administrators Guide
53-1003130-01