Linking A Virtual Device With A Physical Device - 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 27
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
Figure 27-8
Click Create to create the virtual target.
Step 10
Click the CFS icon to commit and distribute the configuration changes.
Step 11
The pWWN of the virtual target does not appear in the zoning end devices database in Fabric Manager.
If you want to zone the virtual device with a pWWN, you must enter it in the Add Member to Zone dialog
box when creating a zone. However, if the device alias is in enhanced mode, the virtual device names
appear in the device alias database in the Fabric Manager zoning window. In this case, users can choose
to select either the device alias name or enter the pWWN in the Add Member to Zone dialog box.
For more information, see the
Set the device alias mode to enhanced when using SDV (because the pWWN of a virtual device could
change).
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. 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"

Linking a Virtual Device with a Physical Device

After creating a virtual device and configuring it as part of a zone, you can define the primary device for
it using the link command, which is also used to fail over to the secondary device.
Note
When a link operation fails over to the secondary device, the virtual device is taken offline, and then
brought online.
As of MDS NX-OS Release 4.1(1a), the following conditions must be considered before linking a
device:
OL-17256-03, Cisco MDS NX-OS Release 4.x
Virtual Devices tab
If you link to the secondary device which is currently active because of failover, the primary tag is
moved to the secondary device and the secondary device becomes the primary device.
When the secondary device is active, if you link to a third device, and if the fallback attribute was
not configured, the third device becomes the primary device but the secondary device continues to
be the active device.
"Adding Zone Members" section on page
for details and requirements about device alias modes.
Cisco MDS 9000 Family Fabric Manager Configuration Guide
Configuring SDV
30-14.
Chapter 31,
27-7

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents