HP AE370A - Brocade 4Gb SAN Switch 4/12, Administrator'S Manual

Page: 364 / 447

364 Administering Advanced Zoning
• Merging rules
Observe these rules when merging zones:
• 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:
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.
Local and adjacent configurations If the local and adjacent zone database
configurations are the same, they will remain
unchanged after the merge.
Effective configurations If there is an effective configuration between two
switches, the zone configuration in effect match.
Zone object naming If a Zoning object has the same name in both the
local and adjacent defined configurations, the object
types and member lists must match. When comparing
member lists, the content and order of the members
are important.
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.