<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<!-- saved from url=(0014)about:internet -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <meta http-equiv="Content-Style-Type" content="text/css" />
    <meta name="GENERATOR" content="Quadralay WebWorks AutoMap 2003 Platinum Edition Client for FrameMaker 8.6.6597.0" />
    <meta name="TEMPLATEBASE" content="emwebh8-1-17" />
    <meta name="LASTUPDATED" content="08/01/13 14:47:30" />
    <title>SDV Requirements and Guidelines </title>
    <!-- Copyright 2010-2013, Cisco Systems, Inc. All rights reserved. -->

    <link rel="StyleSheet" href="document.css" type="text/css" />
    <link rel="StyleSheet" href="catalog.css" type="text/css" />


<script> 
    var is_chrome = navigator.userAgent.toLowerCase().indexOf('chrome') > -1; 
   
    if(is_chrome){document.domain=document.domain}
   </script>
    <script type="text/javascript" language="JavaScript1.2" src="expand.js"></script>
    <script type="text/javascript" language="JavaScript1.2" src="page.js"></script>

    <script type="text/javascript" language="JavaScript1.2">
     <!--
      function  WWNoOp() {}
      function  WWNoValue() { return ""; }

      var  VarDropDown;

      if (typeof(HTMLHelp_Object) != "undefined")
      {
        VarDropDown = new WWDropDown_Object();
      }
      else
      {
        VarDropDown = new Object();
        VarDropDown.fAnchorOpen  = WWNoOp;
        VarDropDown.fAnchorClose = WWNoOp;
        VarDropDown.fDIVOpen  = WWNoOp;
        VarDropDown.fDIVClose = WWNoOp;
      }
     // -->
    </script>

  
<SCRIPT language="javascript">
<!--
  self.document.write("<link href='"+top.relPath+"shared/style.css' rel='stylesheet' type='text/css'>");
  myid=1200;
  self.document.write("<script type='text/javascript' language='JavaScript' src='"+top.relPath+"shared/con_utils.js'></scr"+"ipt>");
//-->
</SCRIPT>
</head>

  <body onload="highlightSearchTerms();" bgcolor="#ffffff">

    
    <blockquote>
    <a name="top"></a>

    
    


<a name="wp1074013"> </a><h1 class="pTitle">
SDV Requirements and Guidelines

</h1>
<a name="wp1074014"> </a><p class="pBody">
Be aware of the following requirements and guidelines as you plan and configure SDV:

</p>
<div class="pSmartList1"><ul class="pSmartList1">
<a name="wp1074015"> </a><li class="pSmartList1">SDV should be enabled on switches where devices that are part of SDV zones are connected. 
</li>
<a name="wp1074016"> </a><li class="pSmartList1">SDV does not work for devices connected to non-MDS switches.
</li>
<a name="wp1074017"> </a><li class="pSmartList1">Broadcast zoning is not supported for a zone with a virtual device.
</li>
<a name="wp1074019"> </a><li class="pSmartList1">IVR and SDV cannot be used for the same device. A SDV-virtualized device cannot be part of an 
IVR zone or zoneset.
</li>
<a name="wp1074020"> </a><li class="pSmartList1">Virtual device names should be unique across VSANs because they are registered with the device 
alias server, which is unaware of VSANs. For example, if you have enabled SDV and have registered 
a name, vt1 in both VSAN 1 and VSAN 2, then the device alias server cannot store both entries 
because they have the same name.
</li>
<a name="wp1074021"> </a><li class="pSmartList1">You cannot specify the same primary device for different virtual devices.
</li>
<a name="wp1074022"> </a><li class="pSmartList1">SDV does not work with soft zoning (<em class="cEmphasis">Soft zoning</em> means that zoning restrictions are applied only 
during interaction between the name server and the end device). If an end device somehow knows 
the FC ID of a device outside its zone, it can access that device; it does not work with the <b class="cBold">zone 
default-zone permit vsan </b>operation (which would otherwise permit or deny traffic to members in 
the default zone).
</li>
<a name="wp1074023"> </a><li class="pSmartList1">If devices are not already zoned with the initiators, then you can configure SDV virtual device zones 
with no negative impact. If they are already zoned, then zoning changes are required.
</li>
<a name="wp1074024"> </a><li class="pSmartList1">The real device-virtual device zone cannot coexist with the real device-real device zone. If the real 
devices are not already zoned together, then you can configure the real device-virtual device zone 
with no negative impact. If these devices are already zoned, then adding the real device-virtual 
device zone may cause the zone activation to fail. If this occurs, then you must delete one of the 
zones before activation.
</li>
<a name="wp1074025"> </a><p class="pListBodyLevel1">
For example, a user attempts to create a configuration with zone A, which consists of I, the initiator, 
and T, the target (I,T), and zone B, which consists of a virtual initiator, VI, and real target, T (zone 
VI, T). Such a configuration would fail. Likewise, an attempt to configure zone C, which consists 
of an initiator, I, and target T, with zone D, which consists of an initiator, I, and virtual target, VT 
(zone I, VT), would also fail.

</p>
<a name="wp1074026"> </a><p class="pCaution">
<table border="0">
<tr>
<td>
<strong>Caution	&nbsp;&nbsp;&nbsp;</strong>
</td>
<td>
<p>There must be at least one SDV-enabled switch that is <span style="font-style: italic">not</span> a Cisco MDS 9124 Switch between the server 
and the device that are being virtualized. SDV does not work when initiators and primary devices are 
connected to the same Cisco MDS 9124 Switch.
</p>
</td>
</tr>
</table>

</p>
</ul></div>
<hr /><br><p class="pBody">Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.</p> 

    </blockquote>

  </body>
</html>
