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

Setting the fabric-wide consistency policy
1. Connect to the switch and log in using an account with admin permissions, or an account with OM
permissions for the FabricDistribution RBAC class of commands.
2. Enter the fddCfg --fabwideset command.
The following example shows how to set a strict SCC and tolerant DCC fabric-wide consistency
policy.
switch:admin> fddcfg --fabwideset "SCC:S;DCC"
switch:admin> fddcfg --showall
Local Switch Configuration for all Databases:-
DATABASE - Accept/Reject
---------------------------------
SCC - accept
DCC - accept
PWD - accept
FCS - accept
AUTH - accept
IPFILTER - accept
Fabric Wide Consistency Policy:- "SCC:S;DCC"
Notes on joining a switch to the fabric
When a switch is joined to a fabric with a tolerant SCC, DCC, or FCS fabric-wide consistency policy,
the joining switch must have a matching tolerant SCC, DCC, or FCS fabric-wide consistency policy. If
the tolerant SCC, DCC, or FCS fabric-wide consistency policies do not match, the switch can join the
fabric, but an error message flags the mismatch. If the tolerant SCC, DCC, and FCS fabric-wide
consistency policies match, the corresponding SCC, DCC, and FCS ACL policies are compared.
The enforcement of fabric-wide consistency policy involves comparison of the Active policy set. If the
ACL polices match, the switch joins the fabric successfully. If the ACL policies are absent either on the
switch or on the fabric, the switch joins the fabric successfully, and the ACL policies are copied
automatically from where they are present to where they are absent. The Active policy set where it is
present overwrites the Active and Defined policy set where it is absent. If the ACL policies do not
match, the switch cannot join the fabric and the neighboring E_Ports are disabled.
Use the fddCfg --fabwideset command on either this switch or the fabric to set a matching strict SCC,
DCC, or FCS fabric-wide consistency policy. Use ACL policy commands to delete the conflicting ACL
policy from one side to resolve ACL policy conflict. If neither the fabric nor the joining switch is
configured with a fabric-wide consistency policy, there are no ACL merge checks required. Under both
conflicting conditions, secPolicyActivate is blocked in the merged fabric. Use the distribute
command to explicitly resolve conflicting ACL policies.
The above descriptions also apply to joining two fabrics. In this context, the joining switch becomes a
joining fabric.
Matching fabric-wide consistency policies
This section describes the interaction between the databases with active SCC and DCC policies and
combinations of fabric-wide consistency policy settings when fabrics are merged.
For example: Fabric A with SCC:S;DCC (strict SCC and tolerant DCC) joins Fabric B with SCC:S;DCC
(strict SCC and tolerant DCC), the fabrics can merge as long as the SCC policies match, including the
order SCC:S;DCC and if both are set to strict.
Table 53 describes the impact of merging fabrics with the same fabric-wide consistency policy that
have SCC, DCC, or both policies.
Setting the fabric-wide consistency policy
242 Fabric OS Administrators Guide
53-1003130-01