SAN Device Virtualization
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
switch# show zoneset
switch# config t
switch(config)# zoneset activate name zs1
switch# show zoneset active vsan 1
Set the device alias mode to enhanced when using SDV (because the pWWN of a virtual device could
For example, SDV is enabled on a switch and a virtual device is defined. SDV assigns a pWWN for the
virtual device, and it is zoned based on the pWWN in a zone. If you later disable SDV, this configuration
is lost. If you reenable SDV and create the virtual device using the same name, there is no guarantee that
it will get the same pWWN again. Hence, you would have to rezone the pWWN-based zone. However,
if you perform zoning based on the device-alias name, there are no configuration changes required if or
when the pWWN changes.
Be sure you understand how device alias modes work before enabling them. Refer to
"Distributing Device Alias Services"
Configuring a Virtual Device with a Static FC ID
Typically, the FC ID for the virtual device is assigned by the system. There is a virtual domain reserved
and advertised for SDV devices and it is used when allocating the FC ID. The FC ID is registered with
the name server and has the same FC4 properties as the primary device it represents.
When a fabric containing a virtual device configuration reboots, the virtual device's domain or FC ID
may change; there is no guarantee that the virtual device FC ID will remain the same because it is not a
part of the configuration. You can define the FC ID for a virtual device to be static. Configuring a device
to have a static FC ID ensures that the same FC ID is used for the virtual device configuration across
SAN-OS reboots, and it also provides the following benefits:
This procedure is optional, but we recommend it. You can also configure a static domain ID. Only the
domain part of the FC ID is static; other values are system-assigned.
If you are using SDV to virtualize devices for either AIX or HP-UX platforms, we recommend you create
a static FC ID.
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Makes it easier for SAN administrators to plan and design the SAN (for example, administrators can
assign virtual domains and FC IDs to be used by virtual devices).
Improves monitoring and troubleshooting because the same FC ID is assigned to a virtual device on
Displays the zone sets configured for the VSAN,
vsan 1, in step 4, as well as the primary and
Enters configuration mode.
Activates the new zone, zs1 for the VSAN, vsan1.
Exits all modes.
Displays the active zone for the VSAN, vsan1.
Confirms the zone set and zone names.
for details and requirements about device alias modes.
Cisco MDS 9000 Family CLI Configuration Guide