CHAPTER
Send documentation comments to mdsfeedback-doc@cisco.com
28-1
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
28
Creating Dynamic VSANs
Port VSAN membership on the switch is assigned on a port-by-port basis. By default each port belongs
to the default VSAN.
You can dynamically assign VSAN membership to ports by assigning VSANs based on the device
WWN. This method is referred to as Dynamic Port VSAN Membership (DPVM). DPVM offers
flexibility and eliminates the need to reconfigure the port VSAN membership to maintain fabric
topology when a host or storage device connection is moved between two Cisco MDS switches or two
ports within a switch. It retains the configured VSAN regardless of where a device is connected or
moved. To assign VSANs statically, see Chapter 26, “Configuring and Managing VSANs.”
This chapter includes the following sections:
• DPVM, page 28-1
• DPVM Database Distribution, page 28-10
• Database Merge Guidelines, page 28-13
• Default Settings, page 28-15
DPVM
DPVM configurations are based on port world wide name (pWWN) and node world wide name (nWWN)
assignments. A DPVM database contains mapping information for each device pWWN/nWWN
assignment and the corresponding VSAN. The Cisco NX-OS software checks the database during a
device FLOGI and obtains the required VSAN details.
The pWWN identifies the host or device and the nWWN identifies a node consisting of multiple devices.
You can assign any one of these identifiers or any combination of these identifiers to configure DPVM
mapping. If you assign a combination, then preference is given to the pWWN.
DPVM uses the Cisco Fabric Services (CFS) infrastructure to allow efficient database management and
distribution. DPVM uses the application driven, coordinated distribution mode and the fabric-wide
distribution scope (see Chapter 13, “Using the CFS Infrastructure”).
Note DPVM does not cause any changes to device addressing. DPVM only pertains to the VSAN membership
of the device, ensuring that the host gets same VSAN membership on any port on the switch. For
example, if a port on the switch has a hardware failure, you can move the host connection to another port
on the switch and not need to update the VSAN membership manually.
To Next Page
Loading...
Need help?
General
