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
The following terms are used throughout this chapter:
SDV is a distributed service and uses CFS (Cisco Fabric Services) distribution to synchronize the
databases. When you configure SDV it starts a CFS session and locks the fabric. When a fabric is locked,
Cisco SAN-OS software does not allow any configuration changes from a switch–other than the switch
holding the lock–and issues a message to inform users about the locked status. Configuration changes
are held in a pending database for the application. You must perform a commit operation to make the
configuration active and to release the lock for all switches. You can discard or stop changes from being
distributed by issuing the abort/clear command.
When you enable SDV, CFS distribution is also enabled; CFS distribution cannot be disabled for SDV.
The following sections describe how to configure SDV:
Configuring a Virtual Device
A virtual device is identified by an alphanumeric name of up to 32 characters and defines all the real
devices (one primary and one or more secondary) that it represents. Upon the successful creation of a
virtual device, the virtual device name is internally registered as the device alias name with the device
alias database; the pWWN is automatically assigned by the system using Cisco OUI (Organizational
Unique Identifier). A virtual device appears as a real, physical device. You can enumerate up to 128
devices for a virtual device. There is a limit of 4095 on the number of virtual devices that you can create
in a single VSAN.
For Cisco MDS SAN-OS Release 3.1(2) and later, SDV has been tested to work with up to 1024 virtual
devices per VSAN.
Cisco MDS 9000 Family CLI Configuration Guide
The virtualized or proxy representation of the real device, which is registered with the name server
and has a pWWN and FC ID. A virtual device exists as long as its real (physical) counterpart is
online. The virtual device pWWN and FC ID must be unique and cannot clash with any real device
pWWNs and FC IDs.
Reserved by SDV to assign FC IDs to virtual devices. If the switch that reserved the domain goes
down, another switch takes over its role using the same domain.
Chapter 6, "Using the CFS Infrastructure"
Configuring a Virtual Device, page 20-4
Configuring a Zone for a Virtual Device, page 20-6
Linking a Virtual Device with a Physical Device, page 20-8
Configuring LUN Zone Members for SDV Devices, page 20-8
Resolving Fabric Merge Conflicts, page 20-9
for more details about CFS,
OL-16184-01, Cisco MDS SAN-OS Release 3.x
SAN Device Virtualization