<!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:22" />
    <title>Creating Zone Sets and Adding Member Zones </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=1048;
  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="wp1076113"> </a><h1 class="pTitle">
Creating Zone Sets and Adding Member Zones

</h1>
<a name="wp1195491"> </a><p class="pBody">
The pWWN of the virtual target does not appear in the zoning end devices database in DCNM-SAN. 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 DCNM-SAN 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. <br />
<br />
For more information, see the <a href="zone28.html">&quot;Adding Zone Members&quot; topic</a>.

</p>
<a name="wp1185261"> </a><p class="pBody">
Set the device alias mode to <b class="cBold">enhanced</b> when using SDV (because the pWWN of a virtual device could 
change).<br />
<br />
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 will 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.<br />
<br />
Be sure you understand how device alias modes work before enabling them. Refer to <a href="ddas01.html">&quot;Distributing 
Device Alias Services&quot;</a> for details and requirements about device alias modes.

</p>
<a name="wp1195499"> </a><p class="pBodyAutonumNoRule">
<strong>Note	&nbsp;&nbsp;&nbsp;</strong> If one zone set is active and you activate another zone set, the currently active zone set is automatically 
deactivated.

</p>
<a name="wp1195500"> </a><p class="pBodyAutonumRel">
<strong>Tip	&nbsp;&nbsp;&nbsp;</strong> You do not have to <b style="font-weight: normal" class="cBold">copy</b><b class="cBold"> </b>the running configuration to the startup configuration to store the active zone 
set. However, you need to copy the running configuration to the startup configuration to explicitly store 
full zone sets. It is not available across switch resets.

</p>
<a name="wp1195501"> </a><p class="pCaution">
<table border="0">
<tr>
<td>
<strong>Caution	&nbsp;&nbsp;&nbsp;</strong>
</td>
<td>
<p>If you deactivate the active zone set in a VSAN that is also configured for IVR, the active IVR zone set 
(IVZS) is also deactivated and all IVR traffic to and from the switch is stopped. This deactivation can 
disrupt traffic in more than one VSAN. Before deactivating the active zone set, check the active zone 
analysis for the VSAN . To reactivate the IVZS, you must reactivate the regular zone set (refer to the 
<em class="cEmphasis">Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide</em>).
</p>
</td>
</tr>
</table>

</p>
<a name="wp1076165"> </a><p class="pCaution">
<table border="0">
<tr>
<td>
<strong>Caution	&nbsp;&nbsp;&nbsp;</strong>
</td>
<td>
<p>If the currently active zone set contains IVR zones, activating the zone set from a switch where IVR is 
not enabled disrupts IVR traffic to and from that VSAN. We strongly recommend that you always 
activate the zone set from an IVR-enabled switch to avoid disrupting IVR traffic.
</p>
</td>
</tr>
</table>

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

    </blockquote>

  </body>
</html>
