Releasing Zone Database Locks; Merging The Database - Cisco Nexus 5000 Series Configuration Manual

Enhanced Zoning
Command or Action
Step 5
switch(config)# no zone commit vsan vsan-id
force

Releasing Zone Database Locks

To release the session lock on the zoning database on the switches in a VSAN, use the no zone commit vsan
command from the switch where the database was initially locked.
switch# configuration terminal
switch(config)# no zone commit vsan 2
If session locks remain on remote switches after using the no zone commit vsan command, you can use the
clear zone lock vsan command on the remote switches.
switch# clear zone lock vsan 2
We recommend using the no zone commit vsan command first to release the session lock in the fabric.
Note
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 the following table.
Table 23: Database Zone Merge Status
Local Database
The databases contain zone sets with the same nameIn
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 different
zones, aliases, and attributes groups.
The databases contains a zone, zone alias, or zone
attribute group object with same name1 but different
members.
Empty.
Cisco Nexus 5000 Series NX-OS SAN Switching Configuration Guide
126
Purpose
Forcefully discards the changes to the enhanced zone database
and closes the session created by another user.
Adjacent Database Merge Status
Successful.
Failed.
Contains data. Successful.
Configuring and Managing Zones
Results of the Merge
ISLs are isolated.
The adjacent database
information populates the
local database.
The union of the local
and adjacent databases.
OL-xxxxx-xx