HP StoreFabric SN6500B Administrator's Manual page 337

Adding a new fabric that has no zone configuration information to an existing fabric is very similar
to adding a new switch. All switches in the new fabric inherit the zone configuration data. If the
existing fabric has an effective zone configuration, then the same configuration becomes the
effective configuration for the new switches.
Before the new fabric can merge successfully, it must pass the following criteria:
•
•
•
Fabric OS Administrator's Guide
53-1002745-02
Before merging
To facilitate merging, check the following before merging switches or fabrics:
-
Default Zone: The switches must adhere to the default zone merge rules, as described in
"Zone merging scenarios"
-
Effective and defined zone configuration match: Ensure that the effective and defined
zone configurations match. If they do not match, and you merge with another switch, the
merge might be successful, but unpredictable zoning and routing behavior can occur.
Merging and segmentation
The fabric is checked for segmentation during power-up, when a switch is disabled or enabled,
or when a new switch is added.
The zone configuration database is stored in nonvolatile memory by the cfgSave command. All
switches in the fabric have a copy of this database. When a change is made to the defined
configuration, the switch where the changes were made must close its transaction for the
change to be propagated throughout the fabric.
If you have implemented default zoning you must set the switch you are adding into the fabric
to the same default zone mode setting as the rest of the fabric to avoid segmentation.
Merging rules
Observe these rules when merging zones:
-
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
effective zone configurations must 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.
-
TI zones: If there is an effective configuration between two switches and TI zones are
present on either switch, the TI zones are not automatically activated after the merge.
Check the TI zone enabled status using the zone --show command and if the status does
not match across switches, issue the cfgenable command.
on page 339.
11
Zone merging
337