Cisco Nexus 5000 Series Switch CLI Software Configuration Guide, NX-OS 4.0(1a)N1 (OL-16597-01, January 2009)

Send feedback to [e-mail]
38-22
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 38 Configuring and Managing Zones
Enhanced Zoning
Note We recommend using the no zone commit vsan command first to release the session lock in the fabric.
If that fails, use the clear zone lock vsan command on the remote switches where the session is still
locked.
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 Table 38-5.
The merge process operates as follows:
1. The software compares the protocol versions. If the protocol versions differ, then the ISL is isolated.
2. If the protocol versions are the same, then the zone policies are compared. If the zone policies differ,
then the ISL is isolated.
3. If the zone merge options are the same, then the comparison is implemented based on the merge
control setting.
a. If the setting is restrict, the active zone set and the full zone set should be identical. Otherwise,
the link is isolated.
b. If the setting is allow, then the merge rules are used to perform the merge.
Table 38-5 Database Zone Merge Status
Local Database Adjacent Database Merge Status Results of the Merge
The databases contain zone sets with the same name
1
but
different zones, aliases, and attributes groups.
1. 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.
Successful. The union of the local and
adjacent databases.
The databases contains a zone, zone alias, or zone
attribute group object with same name
1
but different
members.
Failed. ISLs are isolated.
Empty. Contains data. Successful. The adjacent database
information populates the
local database.
Contains data. Empty. Successful. The local database
information populates the
adjacent database.