Configuring and Managing Zones
Local Database
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.
Configuring Zone Merge Control Policies
You can configure merge control policies.
Procedure
Step 1
Step 2
Step 3
Step 4
OL-30895-01
Adjacent Database
Empty.
◦ 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.
Command or Action
configure terminal
Example:
switch# configure terminal
switch(config)#
zone merge-control restrict vsan vsan-id
Example:
switch(config)# zone merge-control restrict
vsan 24
no zone merge-control restrict vsan vsan-id
Example:
switch(config)# no zone merge-control
restrict vsan 33
zone commit vsan vsan-id
Example:
switch(config)# zone commit vsan 20
Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 7.x
Merge Status
Results of the Merge
Successful.
The local database
information populates the
adjacent database.
Purpose
Enters global configuration mode.
Configures a restricted merge control
setting for this VSAN.
Defaults to using the allow merge control
setting for this VSAN.
Commits the changes made to the
specified VSAN.
Enhanced Zoning
151