Fibre Channel HBA and VM Migration Guide for Hyper-V™ and System Center VMM2008 FC0054605-00 A
S Fibre Channel HBA and VM Migration Guide for Hyper-V™ and System Center VMM2008 Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice.
Table of Contents 1 Introduction Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microsoft Windows Server 2008 Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . N_Port ID Virtualization . . . . . . . . . . . . . .
Fibre Channel HBA and VM Migration Guide for Hyper-V™ and System Center VMM2008 A S Troubleshooting Troubleshooting System Center VMM2008 . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Windows Server 2008 Hyper-V and Virtual Machines . . . Troubleshooting QLogic Virtual Adapter (NPIV). . . . . . . . . . . . . . . . . . . . . . B Activity Flow Chart C Hyper-V Processor Virtualization Extensions System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Introduction Abstract This guide describes procedures and best practices for planning and deploying an N_Port ID Virtualization (NPIV) solution with QLogic Fibre Channel (FC) adapters in a Microsoft® Windows Server® 2008 Hyper-V™ and System Center Virtual Machine Manager (VMM) 2008 environment.
1 – Introduction Microsoft Windows Server 2008 Hyper-V S Microsoft Windows Server 2008 Hyper-V Microsoft Windows Server 2008 Hyper-V is the next-generation, hypervisor-based server virtualization technology. It maximizes server hardware investments by consolidating multiple server roles as separate Virtual Machines (VMs) running on a single physical machine.
A 1 – Introduction QLogic FC Adapter NPIV Solution NPIV allows end users to effectively virtualize the Fibre Channel adapter functionality such that each Virtual Machine (VM) running on a server can share a pool of adapters, yet have independent access to its own protected storage.
1 – Introduction How this Guide is Organized S For a detailed discussion of NPIV benefits, see the QLogic White Paper HBA Virtualization Technologies for Windows OS Environments. This white paper is available at the following web page: www.qlogic.com/EducationAndResources/WhitePapersResourcelibrarySan.aspx How this Guide is Organized This step-by-step guide is organized as a set of procedures: Step 1: NPIV Deployment Requirements (Section 2).
A 1 – Introduction How this Guide is Organized Appendix A. Troubleshooting Appendix B. Activity Flow Chart Appendix C. Hyper-V Processor Virtualization Extensions. This appendix lists the requirements for the Intel®-VT and AMD®-V extensions.
1 – Introduction How this Guide is Organized S Notes 1-6 FC0054605-00 A
2 NPIV Deployment Requirements The following sections list the hardware and software requirements that must be met before deploying a QLogic NPIV solution on Microsoft Windows Server 2008 Hyper-V. Hardware Requirements NPIV Enabled FC Adapter. QLogic 2400 series (4Gb) or 2500 series (8Gb) Fibre Channel adapter. NPIV Enabled FC Switch.
2 – NPIV Deployment Requirements Software Requirements 2-2 S QLogic SANsurfer FC HBA Manager GUI (or SANsurfer FC HBA CLI) and Agent. Version 5.0.1 Build 37 or higher Multipathing I/O (MPIO). Latest available version of the MPIO software from your storage array vendor. One example is EMC® PowerPath® for EMC storage arrays.
3 Sample Configuration and Topology Figure 3-1 is an example of an NPIV configuration that uses all of the system elements from Section 2. A real-life data center is a more complex version of the same configuration. Figure 3-1. NPIV Configuration Example In Figure 3-1, Server A and Server B are called the host servers, which host the Virtual Machines and QLogic FC adapters. These servers are connected to the SAN via an NPIV-enabled switch.
3 – Sample Configuration and Topology S Figure 3-2 shows the NPIV topology (how all the logical components of the virtualization solution are connected to each other). Figure 3-2.
4 Configuring the Host and VMM Servers This section describes, at a high level, how to configure the host (Windows Server 2008 Hyper-V) and VMM (System Center VMM2008) servers. Detailed documentation for each of these steps can be found at: www.microsoft.com/windowsserver2008/en/us/virtualization-consolidation.aspx and www.microsoft.com/systemcenter/virtualmachinemanager/ Initial Configuration of the VMM Server To initially configure the Virtual Machine Manager (VMM) server: 1.
4 – Configuring the Host and VMM Servers Adding Hosts to the VMM Server S 5. Install the QLogic SANsurfer FC HBA Manager agent (qlremote) or SANsurfer FC HBA CLI. 6. Install the storage vendor’s MPIO solution software (for example, EMC PowerPath). 7. Install Microsoft Virtual Disk service. 8. Configure the QLogic Fibre Channel switch so that the physical FC adapters on both host servers have access to the same storage array. The switch is configured by creating the appropriate zones.
A 4 – Configuring the Host and VMM Servers Configuring QLogic SANsurfer FC HBA Manager on the VMM Server Configuring QLogic SANsurfer FC HBA Manager on the VMM Server This section describes how to configure the QLogic SANsurfer FC HBA Manager GUI on the VMM server to allow QLogic FC adapters that reside on host servers to be managed via the VMM server. Alternately, you can use QLogic’s SANsurfer FC HBA CLI to achieve the tasks below.
S 4 – Configuring the Host and VMM Servers Configuring QLogic SANsurfer FC HBA Manager on the VMM Server 4. When all the servers have been connected, the final screen will be similar to Figure 4-3. Figure 4-3.
5 Virtual Adapter (NPIV) Port Creation and Verification This section describes how to set up virtual ports and verify that they have been created successfully. Create Virtual Adapter Ports Use QLogic’s SANsurfer FC HBA Manager (or SANsurfer FC HBA CLI) to create virtual adapter ports. Perform the following steps on the VMM server to create a virtual port on a host server. 1. In the SANsurfer tree view (left pane), select the host server where you want to create a virtual port (see Figure 5-1).
S 5 – Virtual Adapter (NPIV) Port Creation and Verification Create Virtual Adapter Ports 2. In the right pane, click the Virtual tab. 3. Right-click the QLogic FC adapter image and click Create vPort (see Figure 5-2). Figure 5-2. SANsurfer FC HBA Manager —Create vPort 4. The vPort WWPN Generation dialogue box displays (see Figure 5-3). Do one of the following: Click OK to accept the automatically generated WWPN. Click Generate. SANsurfer FC HBA Manager generates another WWPN.
A 5 – Virtual Adapter (NPIV) Port Creation and Verification Verify Virtual Adapter Port Login to FC Switch 5. A dialog box displays, prompting for a password. Type the password previously set for SANsurfer FC HBA Manager. If the default password has not been changed, type config. 6. If the vPorts have been created successfully, the final SANsurfer FC HBA Manager screen will be similar to Figure 5-4. Figure 5-4.
S 5 – Virtual Adapter (NPIV) Port Creation and Verification Verify Virtual Adapter Port Login to FC Switch Before Virtual Port Creation Figure 5-5 shows what the switch ports look like before the virtual adapter is created. As shown in Figure 5-5, physical port 16 of the switch has one entry for a QLogic Corporation FC adapter. This is the entry of the physical FC adapter port that resides on the host server connected to port 16 of this FC switch. Figure 5-5.
A 5 – Virtual Adapter (NPIV) Port Creation and Verification Verify Virtual Adapter Port Login to FC Switch After Virtual Adapter Port Creation Figure 5-6 shows what the switch port looks like after the virtual adapter is created. As shown in Figure 5-6, physical port 16 of the switch has two entries for QLogic Corporation FC adapters.
5 – Virtual Adapter (NPIV) Port Creation and Verification Verify Virtual Adapter Port Login to FC Switch S Notes 5-6 FC0054605-00 A
6 Presentation of LUNs to a Virtual Adapter Port This section describes, at a high level, how to present LUNs to a virtual adapter port. For detailed step-by-step instructions, please refer to documentation from your storage array vendor. The following example uses the EMC CX3-20 Fibre Channel storage array managed via EMC Navisphere®. 1. Check the zoning on the Fibre Channel switch to ensure that the newly created virtual port has access to the storage array. 2.
6 – Presentation of LUNs to a Virtual Adapter Port S 3. Register this virtual adapter port as a QLogic initiator, which is installed in a host physically connected to the storage array via the Fibre Channel switch. 4. Determine the size and number of LUNs needed based on the disk size a Virtual Machine hosted on this LUN would need. Factor in additional LUNs based on the needs of the application running inside the Virtual Machine. 5.
7 Creating a Virtual Machine Microsoft Hyper-V enables the creation of Virtual Machines on top of a host computer running Microsoft Windows Server 2008 x64. Microsoft System Center VMM allows the use of Microsoft Hyper-V software to create Virtual Machines with configurations based on user requirements. For a detailed description on how to create Virtual Machines via VMM, refer to the appropriate Microsoft documentation.
S 7 – Creating a Virtual Machine 6. Click Next. The Select Virtual Machine Host dialogue box displays. Verify that Transfer type column has a SAN entry for the host you want to select. Check the SAN Explanation tab to ensure that there are no warnings other than for iSCSI. Figure 7-1.
A 7 – Creating a Virtual Machine 7. Click Next. The Select Path dialog box displays (see Figure 7-2). By default, a path on the local hard drive of the host server is shown. The path specified in this box determines where the Virtual Hard Drive that contains the operating system image of the Virtual Machine resides. Figure 7-2.
7 – Creating a Virtual Machine 8. S Click Browse and select the destination folder as a Network Drive that is a LUN that was formatted as an NTFS partition as described in Section 6. By providing for the destination folder, a SAN LUN that is visible to other host servers in the SAN ensures that a SAN-based Virtual Machine migration is possible. VMM automatically marks a volume that is capable of SAN migration as Migration Capable, as shown in Figure 7-3. Figure 7-3. Migration Capable Volume 7-4 9.
8 Migrating Virtual Machines and Virtual Ports Microsoft System Center VMM2008 allows you to quickly migrate Virtual Machines from one host to another. Migration allows administrators to perform maintenance on physical servers and easily move Virtual Machines to other servers with minimal downtime. VMM2008 allows for two types of migrations: LAN Transfer/Migration of Virtual Machines.
8 – Migrating Virtual Machines and Virtual Ports Performing SAN Transfers S The LUN must be configured as a basic/fixed disk. A SAN transfer will not work with volumes that are mapped to dynamic disks. See the Microsoft documentation on the difference between basic and dynamic disks. A single volume must be created on the basic disk. LUNs that contain multiple volumes cannot be migrated via a SAN transfer. A single Virtual Machine and all its associated files must be placed on this volume.
A 8 – Migrating Virtual Machines and Virtual Ports Performing SAN Transfers 2. The Migrate Virtual Machine Wizard dialog box displays. Choose the destination host for the Virtual Machine migration. 3. When all the requirements of SAN transfer have been met for the selected destination host, the screen displays “This host is available for SAN migrations” in the SAN Explanation tab, as shown in Figure 8-2. Figure 8-2.
8 – Migrating Virtual Machines and Virtual Ports Performing SAN Transfers 6. S Monitor the migration status through the Jobs windows by clicking the Jobs tab in the left pane of VMM. Once the job completes, the Jobs screen will be similar to Figure 8-3. Figure 8-3. VMM—Migration Complete 8-4 7. Verify that the virtual adapter port associated with the Virtual Machine has been migrated to the destination host.
A Troubleshooting Troubleshooting System Center VMM2008 Resources are available on the System Center Virtual Machine Manager TechCenter page: http://technet.microsoft.com/en-us/scvmm/default.aspx Troubleshooting Windows Server 2008 Hyper-V and Virtual Machines See the troubleshooting sections at the Microsoft website: For Windows Server 2008, go to: http://technet.microsoft.com/en-us/library/cc753935.aspx For Hyper-V, go to: http://technet.microsoft.com/en-us/library/cc742454.
S A – Troubleshooting Troubleshooting QLogic Virtual Adapter (NPIV) Issue Possible Cause Solution When trying to create a virtual adapter port, SANsurfer FC HBA Manager reports an “Unable to Create vPort” error. The creation of the virtual adapter port has failed; there are multiple reasons why this happens. Ensure that the physical FC adapter port is connected to an NPIV-capable switch. Ensure that the physical FC adapter port is in a point-to-point connection.
B Activity Flow Chart The flow chart in Figure B-1outlines the steps required to create a virtualized network that includes creating virtual adapter ports using NPIV, creating Virtual Machines using VMM, and assigning LUNs using the storage array vendor’s management tool. Figure B-1.
B – Activity Flow Chart S Notes B-2 FC0054605-00 A
C Hyper-V Processor Virtualization Extensions System Requirements Hyper-V requires that processor virtualization extensions (Intel-VT and AMD-V) be enabled along with the No-Execute (NX) feature. For AMD systems, the CPU must be one of the following: Revision F3 or greater or Revision F2 with additional BIOS support (most (but not all) of the server OEMs have the additional BIOS support).
S C – Hyper-V Processor Virtualization Extensions Enabling VT and AMD Virtualization in the System BIOS Enabling VT and AMD Virtualization in the System BIOS Both Intel and AMD platforms have BIOS options to enable and disable virtualization extensions. Most systems ship with the extensions disabled. To enable these virtualization extensions, go into the BIOS utility in the pre-boot environment. Look for tags similar to Virtualization/VT/EM64T/AMD-V/SVM etc. and set their value enable them.
D Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 Europe Headquarters QLogic (UK) LTD. Quatro House Lyon Way, Frimley Camberley Surrey, GU16 7ER UK www.qlogic.com +44 (0) 1276 804 670 © 2008 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic, the QLogic logo, SANbox, and SANsurfer are trademarks or registered trademarks of QLogic Corporation.
