HP Cisco MDS 9120 Cisco MDS 9000 Family Fabric Manager Configuration Guide - R - Page 345

Chapter 14 Configuring FlexAttach Virtual pWWN Difference Between San Device Virtualization and FlexAttach Port Virtualization Send documentation comments to [email protected] Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 In the Replace Server wizard, click the With Spare Server on a Different NPV switch radio button. Click Next. The Failed Server Port window is displayed. (Figure 14-19) In the Failed Server Port selection window, from the Select a Switch drop-down list, select the switch. From the list of interfaces displayed, select the port from which the server needs to be detached. Click Next. The New Port window is displayed. (Figure 14-16) In the New Port selection window, select the switch and the port on which the spare server is connected. Click Next. The Server WWN window is displayed. (Figure 14-21) In the Server WWN window displayed, enter the existing FlexAttach server virtual port WWN to be replaced, and the new server physical port WWN. Check the Allow wizard to change from "pWWN to vPWWN" mapping to "interface to vPWWN" mapping check box to remove the pWWN to vPWWN entry from the CFS Region mapping table, and configure the mapping only at the interface. Click Finish to complete the FlexAttach configuration for the spare server. Difference Between San Device Virtualization and FlexAttach Port Virtualization Table 14-2 describes the difference between SAN device virtualization (SDV) and FlexAttach port virtualization. Table 14-2 Difference Between SDV and FlexAttach Virtualization SAN Device Virtualization (SDV) FlexAttach Virtualization Facilitates target and disk management, and only Facilitates server management and has no facilitates disk and data migration. restriction on the end devices used. WWN NAT and Fibre Channel ID (FC-ID) are WWN and Network Address Transport (NAT) is allocated on the virtual device, both primary and allocated to host bus adapter (HBA). secondary. FC-ID rewrite on the switch indicates a rewrite-capable switch on the path. No rewrite requirements. Configuration is distributed. This allows programming rewrites and connectivity anywhere. Configuration distribution is not required for any of the interface-based configurations. Configuration is secured to device alias. Does not require device alias for virtual pWWN. Does not allow automapping to the secondary device. Allows automapping to the new HBA. Mapping process is manual for NPIV. OL-17256-03, Cisco MDS NX-OS Release 4.x Cisco MDS 9000 Family Fabric Manager Configuration Guide 14-23