The DPVM pending database is only available in the volatile directory and is subject to being discarded if
the switch is restarted.
Tip
To use administrative privileges and release a locked DPVM session, use the clear dpvm session command
in EXEC mode.
switch# clear dpvm session
Database Merge Guidelines
A database merge refers to a union of the configuration database and static (unlearned) entries in the active
DPVM database. For information about CFS merge support, refer to the Cisco MDS 9000 Family NX-OS
System Management Configuration Guide for detailed concepts.
When merging the DPVM database between two fabrics, follow these guidelines:
• Verify that the activation status and the auto-learn status is the same is both fabrics.
• Verify that the combined number of device entries in each database does not exceed 16 K.
If you do not follow these two conditions, the merge will fail. The next distribution will forcefully synchronize
the databases and the activation states in the fabric.
Caution
This section describes how to merge DPVM databases and includes the following topics:
About Copying DPVM Databases
The following circumstances may require the active DPVM database to be copied to the DPVM config
database:
• If the learned entries are only added to the active DPVM database.
• If the DPVM config database or entries in the DPVM config database are accidently deleted.
If you copy the DPVM database and fabric distribution is enabled, you must commit the changes.
Note
Copying DPVM Databases
To copy the currently active DPVM database to the DPVM config database, use the dpvm database copy
command.
switch# dpvm database
copy active
Legend: “+” New Entry, “-” Missing Entry, “*” Possible Conflict Entry
---------------------------------------------------------------------
- pwwn 12:33:56:78:90:12:34:56 vsan 100
- nwwn 14:21:30:12:63:39:72:81 vsan 101
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
29
Creating Dynamic VSANs
Database Merge Guidelines
To Next Page
Loading...
Need help?
General
