Fabric OS Administrator's Guide v7.0.0 (53-1002148-02, June 2011)

Fabric OS Administrator’s Guide 267
53-1002148-02
Zone merging
11
• Merge conflicts
When a merge conflict is present, a merge will not take place and the ISL will segment. Use the
switchShow or errDump commands to obtain additional information about possible merge
conflicts, because many non-zone related configuration parameters can cause conflicts. See
the Fabric OS Command Reference for detailed information about these commands.
If the fabrics have different zone configuration data, the system attempts to merge the two
sets of zone configuration data. If the zones cannot merge, the ISL will be segmented.
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 zone object with the same name in the other fabric.
- Zone Database Size: If the zone database size exceeds the maximum limit of another
switch.
NOTE
If the zoneset 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 zoneset members on two switches have the same names
defined in the configuration, make sure zoneset 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
might segment.
Zone merging scenarios
The following tables provide information on merging zones and the expected results.
• Table 52 on page 268: Defined and effective configurations
• Table 53 on page 269: Different content
• Table 54 on page 269: Different names
• Table 55 on page 269: TI zones
• Table 56 on page 270: Default access mode
• Table 57 on page 270: Mixed Fabric OS versions