HP StorageWorks 2.64 Core Switch - Manual (Page 38)

Zoning Concepts
38 Zoning Version 3.1.x/4.1.x User Guide
Merging Rules
■ If the local and adjacent zone database configurations are the same, they will
remain unchanged after the merge.
■ If there is an effective configuration between two switches, the zone
configuration in effect must be the same for the fabrics to merge.
■ If a zoning object has the same name in both the local and adjacent defined
configurations, the object types and member lists must also be the same.
When comparing member lists, the content and order of the members are
important.
■ 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 be small enough to fit in the
flash area allotted for the zone database.
■ If a local defined configuration is modified because of a merge, the new zone
database is propagated to other switches within the merge request.
Merging Two Fabrics
The simplest scenario for merging two fabrics is when both fabrics have identical
zones and the same configuration enabled, the two fabrics will join to make one
larger fabric. The same zone configuration will be in effect across this newly
created fabric.
If the two fabrics have different zone configurations, then the two sets of
information will be merged, or the ISL between the switches will be segmented if
the two fabrics cannot join. Refer to
Table 3 on page 40 for more information.
Merging with a V4.1 Fabric
If the user has a StorageWorks Core switch-based fabric, or other switches
running Fabric OS V4.1, the firmware can operate in the same fabric with
StorageWorks SAN switches running Fabric OS V3.0.1a or later firmware.
Switches running Fabric OS V4.1 firmware can operate in the same fabric with all
StorageWorks 1 Gb SAN switches running V2.6 or later. However, HP
recommends that each switch in the SAN run the latest supported firmware for
that switch.