Brocade Secure Fabric OS Administrator's Guide - Supporting Fabric OS v3.2.0, v4.4.0, v5.0.1, v5.1.0, 5.2.0, and 5.3.0 (53-1000244-02, June 2007)

70 Secure Fabric OS Administrator’s Guide
53-1000244-02
4
Adding Switches and Merging Fabrics with Secure Mode Enabled
To merge fabrics, both fabrics must be in secure mode and must have an identical FCS policies.
Any switches that do not have a matching FCS policy or are in a different state regarding secure
mode are segmented. See Table 18 for more information about moving switches between fabrics.
When fabrics are merged, the fabric that contains the desired configuration information must have
a nonzero version stamp, and all the other fabrics being merged must have zero version stamps.
The Security policy set, zoning configuration, password information, MUA information, and SNMP
community strings are overwritten by the fabric whose version stamp is nonzero. Before merging,
verify that the fabric that contains all the desired information has the nonzero version stamp
CAUTION
As an exception to the rule of secure fabric merges, when a non-FCS switch merges with a secure
fabric, the primary switch propagates its secure database to the non-FCS switch. Propagation from
the primary switch occurs even if the secure fabric has a zero version stamp and the non-FCS switch
has nonzero version stamp.
For general information about merging fabrics and instructions for merging fabrics that are not in
secure mode, refer to the Fabric OS Administrator’s Guide.
When MUAs are available, care is required when the fabric goes through a merge or changes occur
the primary FCS switch:
• In a fabric that starts with a Fabric v3.2.0, v4.4.0, v5.0.1, or v5.1.0 switch as the primary FCS
switch and MUAs are defined, if a Fabric OS v2.6.1, v3.1.x, v4.1.x, and v4.2.x backup switch
becomes the new primary without any version stamp changes, the remaining Fabric OS v3.2.x,
v4.4.x, v5.0.1, v5.1.0, and v5.2.0 switches delete their MUAs.
• In a fabric with a Fabric OS v2.6.1, v3.1.x, v4.1.x, or v4.2.x switch as the primary FCS switch,
when a Fabric OS v3.2.x, v4.4.x, v5.0.1, or v5.1.0 switch merges into the fabric not as a
primary and with a zero version stamp, the switch backs up and deletes its MUAs.
• In a fabric with a Fabric OS v2.6.1, v3.1.x, v4.1.x, or v4.2.x switch as the primary FCS switch,
when a Fabric OS v3.2.x, v4.4.x, v5.0.1, or v5.1.0 switch merges into the fabric as the new
primary and it has MUAs, all the Fabric OS v3.2.x, v4.4.x, v5.0.1, or v5.1.0 switches in the
fabric request a download of the MUA accounts even through their version stamp matches the
primary.