78 
3.  After the merge process initiated by Switch A is complete, Switch B initiates a merge process to all 
its neighbors. This synchronizes Switch B's local database changes resulting from the merge to the 
entire fabric. 
4.  Two 1-way merge processes can ensure data consistency between Switch A and Switch B. 
 
  NOTE: 
Consistent active zone sets among switches can be achieved by a merge. Consistent zone databases 
achieved after a merge, however, require all participating switches to be confi
ured with complete mer
e.
 
Zone merge rules 
Table 5 Zone merge rules 
Local database  Nei
hbor database
Mer
e status
Mer
e result 
The zone databases contain zone sets with the same 
name, but zones in these zone sets have different 
names. 
Successful 
The union of the local database 
and neighbor database. Zone sets 
with the same name are merged. 
The zone databases contain zone sets with different 
names. 
Successful 
The union of the local database 
and neighbor database. All zone 
sets with different names are 
retained. 
The zone databases contain zones or zone aliases 
with different names. 
Successful 
The union of the local database 
and neighbor database. All zone 
sets or zone aliases with different 
names are retained. 
The zone databases contain zones or zone aliases 
with the same name, but one or more of these zones 
or zone aliases have one or more different zone 
members. 
Failed 
Both databases remain 
unchanged. 
Empty Contain data Successful 
The neighbor database overwrites 
the local database. 
Contain data  Empty  Successful 
The local database overwrites the 
neighbor database. 
 
  NOTE: 
•  If two active zone sets have different names, the larger name obtained by  string comparison acts as the
name of the active zone set after merging. 
•  If the active zone sets on two switches fail to merge, the two switches isolate their connecting link by 
bringing down the relevant ports in the VSAN, in addition to keepin
 their zone databases unchan
ed.
 
Zone merge in enhanced zoning mode 
Enhanced zoning has the following differences from basic zoning in zone merge: 
•  Enhanced zoning always performs complete merges, regardless of the merge type. 
•  The MR request has the hard zoning status and a merge flag field in addition to the active zone set 
and zone database. 
The merge flag field includes the merge control mode and default zone policy.