Results of the Merge
Merge Status
Adjacent Database
Local Database
The local database
information populates the
adjacent database.
Successful.
Empty.
Contains data.
The merge process operates as follows:
•
The software compares the protocol versions. If the protocol versions differ, the ISL is isolated.
•
If the protocol versions are the same, then the zone policies are compared. If the zone policies differ,
the ISL is isolated.
•
If the zone merge options are the same, the comparison is implemented based on the merge control
setting.
◦
If the setting is restrict, the active zone set and the full zone set should be identical. Otherwise, the
link is isolated.
◦
If the setting is allow, the merge rules are used to perform the merge.
Configuring Zone Merge Control Policies
You can configure merge control policies.
Procedure
Purpose
Command or Action
Enters global configuration mode.
configure terminal
Example:
switch# configure terminal
switch(config)#
Step 1
Configures a restricted merge control
setting for this VSAN.
zone merge-control restrict vsan vsan-id
Example:
switch(config)# zone merge-control restrict
vsan 24
Step 2
Defaults to using the allow merge control
setting for this VSAN.
no zone merge-control restrict vsan vsan-id
Example:
switch(config)# no zone merge-control
restrict vsan 33
Step 3
Commits the changes made to the
specified VSAN.
zone commit vsan vsan-id
Example:
switch(config)# zone commit vsan 20
Step 4
Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 7.x
OL-30895-01
151
Configuring and Managing Zones
Enhanced Zoning