HP Cisco MDS 9124 Cisco MDS 9000 Family Fabric Manager Configuration Guide, Re - Page 602

Zone Sets Chapter 30 Configuring and Managing Zones Send documentation comments to [email protected] Step 6 Click Yes in the confirmation dialog box to convert that member to pWWN-based membership. Note If one zone set is active and you activate another zone set, the currently active zone set is automatically deactivated. Tip You do not have to copy 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. Caution 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 (see the "Configuring IVR Zones and IVR Zone Sets" section on page 29-24). Caution 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. Note 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 "Adding Zone Members" section on page 30-14. Note 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. 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 Chapter 31, "Distributing Device Alias Services" for details and requirements about device alias modes. 30-24 Cisco MDS 9000 Family CLI Configuration Guide OL-16184-01, Cisco MDS SAN-OS Release 3.x