Merging The Database; Configuring Zone Merge Control Policies - Cisco Nexus 6000 Series Configuration Manual

Enhanced Zoning

Merging the Database

The merge method depends on the fabric-wide merge control setting:
• Restrict—If the two databases are not identical, the ISLs between the switches are isolated.
• Allow—The two databases are merged using the merge rules specified in the following table.
Table 13: Database Zone Merge Status
Local Database
The databases contain zone sets with the same name.
In the enhanced zoning mode, the active zone set does
not have a name in interop mode 1. The zone set
names are only present for full zone sets but are
different zones, aliases, and attributes groups.
The databases contain a zone, zone alias, or zone
attribute group object with same name1 but different
members.
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.

Configuring Zone Merge Control Policies

You can configure merge control policies.
Cisco Nexus 6000 Series NX-OS SAN Switching Configuration Guide, Release 6.x
102
Adjacent Database
Contains data.
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.
Configuring and Managing Zones
Merge Status Results of the Merge
Successful. ISLs are isolated.
Failed. The adjacent database
information populates the
local database.
Successful. The merging of the local
and adjacent databases.
Successful. The local database
information populates the
adjacent database.
OL-27932-01