Table of Contents
Advertisement
Enhanced Zoning
Step 5
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# configure 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 22: 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.
Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 7.x
150
Command or Action
no zone commit vsan vsan-id force
Example:
switch(config)# no zone commit vsan 34
force
Adjacent Database
Contains data.
Configuring and Managing Zones
Purpose
Forcefully discards the changes to the enhanced
zone database and closes the session created by
another user.
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.
OL-30895-01
Advertisement
Table of Contents
