Zone merge rules, Access control, Fc zone configuration task list – H3C Technologies H3C S12500-X Series Switches User Manual
Page 94: Direct routes
85
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 configured with complete merge.
Zone merge rules
Table 3 Zone merge rules
Local database
Neighbor database
Merge status
Merge result
The 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 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 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 databases contain zones or zone aliases with the
same name but different member ports.
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 switches have active zone sets with different names, the larger name obtained by comparison of
strings serves 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 keeping their zone databases unchanged.
Access control
If a server wants to access a disk through the name service, the server needs to determine whether the
server and the disk are in one zone of the active zone set. Members in the same zone can access each
other. Otherwise, they cannot access each other.
FC zone configuration task list
Tasks at a glance
(Optional.)