About Dpvm Databases - HP Cisco MDS 9216 - Fabric Switch Configuration Manual

Chapter 28 Creating Dynamic VSANs
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Figure 28-1
You see the Select Master Switch page.
Step 2 Click the switch you want to be the master switch. This switch controls the distribution of the DPVM
database to other switches in the fabric.
Step 3 Click Next.
You see the AutoLearn Current End Devices page.
Step 4 Optionally, click the Create Configuration From Currently Logged In End Devices check box if you
want to turn on autolearning.
Step 5 Click Next.
You see the Edit and Activate Configuration page.
Step 6 Verify the current or autolearned configuration. Optionally, click Insert to add more entries into the
DPVM config database.
Step 7 Click Finish to update the DPVM config database, distribute the changes using CFS, and activate the
database, or click Cancel to exit the DPVM Setup Wizard without saving changes.

About DPVM Databases

The DPVM database consists of a series of device mapping entries. Each entry consists of a device
pWWN/nWWN assignment along with the dynamic VSAN to be assigned. You can configure a
maximum of 16,000 DPVM entries in the DPVM database. This database is global to the whole switch
(and fabric) and is not maintained for each VSAN.
The DPVM feature uses three databases to accept and implement configurations.
•
•
•
Changes to the DPVM config database are not reflected in the active DPVM database until you activate
the DPVM config database. Changes to the DPVM pending database are not reflected in the
config/active DPVM database until you commit the DPVM pending database. This database structure
allows you to create multiple entries, review changes, and let the DPVM config and pending databases
take effect.
Figure 28-2
OL-16184-01, Cisco MDS SAN-OS Release 3.x
DPVM Wizard Icon
Configuration (config) database—All configuration changes are stored in the configuration database
when distribution is disabled.
Active database—The database currently enforced by the fabric.
Pending database—All configuration changes are stored in the DPVM pending database when
distribution is enabled (see the
shows an example of the DPVM databases in the Information pane in Fabric Manager.
"DPVM Database Distribution" section on page
Cisco MDS 9000 Family CLI Configuration Guide
DPVM
28-8).
28-3