About Dpvm Databases; Configuring Dpvm Config And Pending Databases - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Fabric manager configuration guide, release 4.x
Hide thumbs Also See for AP775A - Nexus Converged Network Switch 5010:
Table of Contents

Advertisement

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
Click Finish to update the DPVM config database, distribute the changes using CFS, and activate the
Step 13
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 or 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 or
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-5
Figure 28-5

Configuring DPVM Config and Pending Databases

To create and populate the config and pending databases using Fabric Manager, follow these steps:
Expand Fabricxx> All VSANs and then select DPVM in the Logical Attributes pane.
Step 1
You see the DPVM configuration in the Information pane.
Click the CFS tab and select a master switch by checking a check box in the Master column.
Step 2
OL-17256-03, Cisco MDS NX-OS Release 4.x
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 Configuration in Fabric Manager
"DPVM Database Distribution" section on page
Cisco MDS 9000 Family Fabric Manager Configuration Guide
DPVM
28-10).
28-5

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents