Users Guide

Fabric OS Administrator’s Guide 373
53-1002920-02
Zone merging
12
A merge is not possible if any of the following conditions exist:
- Configuration mismatch: Zoning is enabled in both fabrics and the zone configurations
that are enabled are different in each fabric.
- Type mismatch: The name of a zone object in one fabric is used for a different type of zone
object in the other fabric.
- Content mismatch: The definition of a zone object in one fabric is different from the
definition of the zone object with the same name in the other fabric.
- Zone database size: The zone database size exceeds the maximum limit of another switch.
NOTE
If the zone set members on two switches are not listed in the same order, the configuration is
considered a mismatch, resulting in the switches being segmented from the fabric. For
example,
cfg1 = z1; z2 is different from cfg1 = z2; z1, even though members of the
configuration are the same. If zone set members on two switches have the same names
defined in the configuration, make sure zone set members are listed in the same order.
Fabric segmentation and zoning
If the connections between two fabrics are no longer available, the fabric segments into two
separate fabrics. Each new fabric retains the same zone configuration.
If the connections between two fabrics are replaced and no changes have been made to the zone
configuration in either of the two fabrics, then the two fabrics merge back into one single fabric. If
any changes that cause a conflict have been made to either zone configuration, then the fabrics
may segment.
Zone merging scenarios
The following tables provide information on merging zones and the expected results:
• Table 64 on page 373: Defined and effective configurations
• Table 65 on page 374: Different content
• Table 66 on page 375: Different names
• Table 67 on page 375: TI zones
• Table 68 on page 376: Default access mode
• Table 69 on page 376: Mixed Fabric OS versions
TABLE 64 Zone merging scenarios: Defined and effective configurations
Description Switch A Switch B Expected results
Switch A has a defined configuration.
Switch B does not have a defined
configuration.
defined:
cfg1:
zone1: ali1; ali2
effective: none
defined: none
effective: none
Configuration from Switch A to propagate
throughout the fabric in an inactive state,
because the configuration is not enabled.
Switch A has a defined and effective
configuration.
Switch B has a defined configuration
but no effective configuration.
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
defined: cfg1
zone1: ali1; ali2
effective: none
Configuration from Switch A to propagate
throughout the fabric. The configuration is
enabled after the merge in the fabric.