Dcc Policies; Distribution Policy States; Dcc Policy States - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

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 (see
Table 28

Distribution policy states

Fabric OS
5.3.0 and later, configured to
accept
5.3.0 and later, configured to
reject
5.2.0 switch (not configured
as it does not support this)
Pre-5.2.0

DCC policies

Multiple 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, see the Access Gateway Administrator's Guide.
Each device port can be bound to one or more switch ports; the same device ports and switch ports may
be listed in multiple DCC policies. After a switch port is specified in a DCC policy, the policy permits
connections only from designated device ports. Device ports that are not specified in any DCC policies are
allowed to connect only to switch ports that are not specified in any DCC policies.
When a DCC violation occurs, the related port is automatically disabled and must be re-enabled using the
portEnable command.
Table 29 shows the possible DCC policy states.
Table 29

DCC policy states

Policy state
No policy
Policy with no entries
Policy with entries
Virtual Fabric considerations: The DCC policies that have entries for the ports that are being moved from
one Logical Switch to another will be considered stale and will not be enforced. You can choose to keep
State
Target switch accepts distribution and fabric state change occurs.
Target switch explicitly rejects the distribution and the operation fails. The
entire transaction is aborted and no fabric state change occurs.
Target switch receives distribution but ignores FCS policy database.
No distribution is initiated, as pre-5.2.0 versions do not support this
operation.
Characteristics
Any device can connect to any switch port in the fabric.
Any device can connect to any switch port in the fabric. An empty policy is the
same as no policy.
• If a device WWN is specified in a DCC policy, that device is
allowed access only to the switch if connected by a switch port listed
in the same policy.
• If a switch port is specified in a DCC policy, it permits connections
only from devices that are listed in the policy.
• Devices with WWNs that are not specified in a DCC policy are
allowed to connect to the switch at any switch ports that are not
specified in a DCC policy.
• Switch ports and device WWNs may exist in multiple DCC policies.
• Proxy devices are always granted full access and can connect to
any switch port in the fabric.
Table
Fabric OS 6.2 administrator guide 123
28).