Technical data

13-26 Fabric OS Administrator’s Guide

Publication Number: 53-0000518-09

Managing Zoning Configurations in a Fabric

• Merging Two Fabrics

Both fabrics have identical zones and configurations enabled. The two fabrics will join to make one

larger fabric with the same zone configuration across the newly created fabric.

If the two fabrics have different zoning configurations, they will be merged. If the two fabrics

cannot join, the ISL between the switches will be segmented.

• Merge Conflicts

When a merge conflict is present, a merge will not take place and the ISL will segment. Use the

switchShow or errLogShow commands to obtain additional information about possible merge

conflicts, because many non-zone related configuration parameters can cause conflicts

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:

Objects in adjacent configurations If a zoning object appears in an adjacent defined

configuration, but not in the local defined configuration,

the zoning object is added to the local defined

configuration. The modified zone database must fit in the

nonvolatile memory area allotted for the zone database.

Local configuration modification If a local defined configuration is modified because of a

merge, the new zone database is propagated to other the

switches within the merge request.

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.

ote

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.