Microsoft® Hyper-V™ Server 2008 for Dell™ PowerEdge™ Systems Networking Solutions Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this document is subject to change without notice. © 2008–2009 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Documentation . 2 The Virtual Network Architecture for Hyper-V Server 2008 . . . . . . . . Virtual Network Adapters . Virtual Switches . 3 . . . . . . . . . . . . . . . . . . . . . . 7 7 9 . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . 11 Supported Hardware and Software Settings for the Network Adapter . . . . . . . . . . . . . . . . . . .
Determining a Virtual Network Implementation . . . . . . . . . . . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . . . . 18 Private Virtual Network Advantages Internal Virtual Network . Advantages . . . . . . . . . . . . . . . . 18 . . . . . . . . . . . . . . . . . . . . . 19 External Virtual Network Disadvantages . . . . . . . . . . . . . . . . 19 . . . . . . . . . . . . . . . . . . . 20 Dedicated Virtual Network Advantages . . . . . . . .
Setting Up the VM and Configuring the Guest Operating System. . . . . . . . . . . . . . . . . . . . . . . 39 . . . . . . . . . 40 . . . . . . . . . . . . . . . . . . . . . . . 41 Setting up the VM Network Environment Setting Up the Network Driver for the Guest Operating System . . . A Appendix A 39 Best Practices for Administering Network Adapter Drivers . . . . . . . . . . . . . . . . 41 . . . . . . . . 41 . . . . . . . . . . . . . 41 B Appendix B . . . . . . . . . . . . . . . . . . . . .
Contents
Overview The introduction of Microsoft® Hyper-V® Server 2008 has changed the way a virtual machine (VM) interacts with the host operating system and network resources. Unlike other Microsoft virtualization software like Virtual Server and Virtual PC, the virtualization technology of Hyper-V is integrated into the Microsoft Windows Server® 2008 x64 operating system. This facilitates better performance and increases integration of the virtualization layer (hypervisor) with other Microsoft Windows® components.
Overview
The Virtual Network Architecture for Hyper-V Server 2008 In Microsoft® Hyper-V® Server 2008, the parent partition manages the I/O devices instead of the hypervisor. To provide virtual machines (VMs) with access to the I/O devices, Hyper-V supports a high-speed interconnect called the VMBus. Virtual devices for each VM, such as network and storage adapters, communicate with the parent partition through the VMBus.
Figure 2-1 illustrates the Hyper-V architecture. Figure 2-1. Hyper-V Architecture Guest operating systems require specialized drivers (VSCs) provided by Microsoft to access the VMBus. The drivers are specific to the type of device that is presented to the guest operating system through the VM configuration. They are installed as a part of the Integration Services available for the Hyper-V supported guest operating systems.
Virtual Network Adapters VMs can be presented with two types of virtual network adapters: Legacy (or emulated) and Synthetic. • Legacy devices emulate a physical network adapter in software. Although this process provides networking services to a VM, it requires additional host processing resources. • Synthetic devices are comparable to proxy devices that present themselves as network devices, but only pass bundles of data along the VMBus to other networking resources.
Virtual Network Architecture for Hyper-V
Supported Hardware and Software Settings for the Network Adapter NOTE: It is recommended to use the latest network adapter drivers for your Dell™ PowerEdge™ system running Microsoft® Hyper-V® Server 2008 downloaded from the Dell Support website at support.dell.com. NOTE: Dell does not support drivers obtained from third-party vendors. These applications can be used to configure physical network adapters that are not connected to the virtual networks.
Stateless Offload (LSO and CSO) The adapters provide the LSO and CSO capabilities if both the network adapters and drivers support them. If the network adapters or the drivers do not support these features, then these capabilities are still available, but performed by the operating system. It is recommended to use adapters with LSO and CSO capabilities as some overhead is incurred when the operating system provides these capabilities.
Table 3-1. Physical NIC Support Features Matrix for Hyper-V Virtual Networks Stateless Features (Supported) Stateful Features (Not Supported) LSO 802.1p (QoS) CSO Receive-Side Scaling (RSS) VLAN Tagging (within Hyper-V) Flow Control Teaming with one primary and one standby adapter Jumbo Frames Wake-On-LAN TOE VLAN Tagging (within third-party software) Network MAC Address NOTE: For configuring NIC team and VLAN, the minimum supported driver version for the Broadcom NIC is 12.
Supported Hardware and Software Settings
Determining a Virtual Network Implementation As mentioned in earlier sections, the virtual switch, or vSwitch, forms the core of all the Microsoft® Hyper-V® Server 2008 virtual networks. NOTE: The virtual switch never appears as an entity or icon in the Microsoft® Windows Server® 2008 parent partitions, including the Network Connection window. It is a logical representation. Four virtual network options are available in Hyper-V.
Advantages • The private virtual network offers complete isolation from the parent partition and the external network. NOTE: The private virtual network is not recommended for environments utilizing Failover Clustering because the private network is localized to each host. Figure 4-1 shows the logical representation of the private network configuration. It additionally shows VMs connected to the virtual switch. Figure 4-1.
Advantages • The internal virtual network enables isolation of VMs from the external network. NOTE: The internal virtual network is not recommended for environments utilizing failover clustering because the internal network is localized to each host. Figure 4-2 shows the logical representation of the internal virtual network configuration. It additionally shows two VMs and the parent partition connected to the virtual switch. Figure 4-2.
3 The parent partition virtual network adapter is connected to the virtual switch. 4 The virtual switch is connected to the physical network adapter that you enabled for external network access. Disadvantages • The second adapter in the parent partition can cause host connectivity issues. These issues include multiple DNS entries, delayed or incomplete NetBIOS resolution, and routing confusion.
Dedicated Virtual Network The dedicated virtual network is a modified form of the external virtual network offered by Hyper-V. This virtual network allows VMs to communicate with other VMs on the same system and to VMs on other systems. The VMs can also access the external network.The VMs have access to the parent partition through the external network if the parent partition virtual network adapter is connected to the virtual switch.
Figure 4-4.
Configuring the Virtual Network This section offers guidance with the hardware and software setup, and best practice recommendations for configuring virtual machines (VMs). The information presented here builds on the virtual network types and usage models discussed in previous sections. Hardware Setup This section helps in determining how many network adapters are required to support various implementations of the Microsoft® Hyper-V® Server 2008 operating system.
• One network adapter is dedicated for parent partition management including remote desktop access and name resolution (DNS/NetBIOS). This adapter is used for public network access in the failover clustering configuration. • Failover cluster configurations use separate network adapters for cluster public and private traffic. NOTE: The cluster public adapter may be shared with the parent partition management network adapter.
Table 5-4. Port Layout with iSCSI and Failover Clustering Parent Partition/ Virtual Network iSCSI Network Cluster Public Adapter Adapter Network Adapter Cluster Private Network Adapter 5 Ports (minimum) Port 1 Port 2 Ports 3 & 4 Port 5 6 Ports (as needed) Port 1 Ports 2 & 3 Ports 4 & 5 Port 6 Recommendations • Functional areas with more than one connection must be spread across adapters to help maintain redundant connectivity in the event of a device or port failure.
Software Setup These configuration steps assume the following: • A fresh installation of Microsoft® Windows Server® 2008 (with Hyper-V). • You have applied the latest updates, including the Hyper-V RTM update, to the operating system. For instructions to download the RTM Hyper-V update, see "Appendix B" on page 43.
Initial Setup 1 In the Network Connections window of the Windows Server 2008 installation, label each LAN on Motherboard (LOM) port for your system. It is recommended to use LOM Port #1 for these LOMs. Label the first LOM PP Mgmt #1 for Parent Partition Management #1. NOTE: The enumeration of these ports may NOT be correctly shown in the Windows Server 2008 Network Connections window.
• VM networks (as needed) • VLANs or separate network fabrics must be used to segregate network traffic NOTE: Unlike other Windows Server 2008 clustered applications, clustered VMs do not utilize the public IP address; instead, they maintain their own addresses for each virtual network adapter in each guest operating system. The public address is used to manage the cluster.
The following steps modify the default configuration of the Windows Server 2008 parent partition network settings. You need to perform these steps because an additional virtual network adapter is added to the parent partition when the internal virtual network is implemented. These changes include: • Modifying the adapter binding order so that the dedicated parent partition physical network adapter is preferred.
Configuring the Virtual Network 1 On the Create Virtual Networks screen, enable the Hyper-V role when prompted, but do not select any network adapters. Continue with the installation, rebooting as required. You require multiple reboots. The installation continues when you login. 2 Launch the Hyper-V Manager by navigating to Administrative Tools→ Hyper-V Manager, and select your system. 3 Under Actions on the right pane, select Virtual Network Manager. In the Name field, enter a name for the virtual switch.
4 Go to Network Connection→ Hyper-V PP NIC #1 properties→ IP v4 properties→ IP settings→ Advanced→ IP Settings. Set the metric for Hyper-V PP NIC #1 to 9999. This setting ensures that the parent partition traffic does not prefer the new Hyper-V virtual network adapter to the dedicated physical parent network adapter. A value of 9999 assigns the virtual network adapter the highest user-assignable link cost.
• Modifying the adapter metric values to ensure that the dedicated physical network adapter is the preferred route. • Disabling auto-negotiate, and setting port duplex and speed. • Modifying DNS resolution and the NetBIOS setting to ensure proper name registration. • Creating a static DNS entry for secondary network adapter of parent partition (optional). • Disabling any unused network adapters. Figure 5-2.
Configuring the External Virtual Network Any settings assigned to the physical network adapter prior to the virtual switch creation are transferred to the new virtual network adapter. Additionally, the physical network adapter is exclusively bound to the Microsoft Virtual Network Switch Protocol after the virtual switch creation. All other bindings are removed. 1 On the Create Virtual Networks screen, enable the Hyper-V role when prompted, but do not select any network adapters.
Configuring the Network 1 Open Network Connections. NOTE: The LOM selected in the Virtual Network Manager has changed to an Enabled status. This indicates that the network adapter is now connected to a virtual switch, vSwitch #1 (External) as shown in the Device Name field. Also notice that a new network adapter has been added to the parent partition to replace the network adapter now connected to the virtual switch. 2 Re-name the new parent partition virtual network adapter to Hyper-V PP NIC #1.
6 In the Advanced TCP/IP window, click the DNS tab. unselect Register this connection's addresses in DNS. This prevents the system from registering this connection in DNS. Only the PP Mgmt NIC #1 network adapter must be allowed to register in DNS to further prevent this network adapter from handling any traffic besides VM traffic. 7 Click the WINS tab of the Advanced TCP/IP Settings window. Select Disable NetBIOS over TCP/IP, and unselect Enable LMHOSTS lookup. 8 Disable any unused network adapters.
• Disabling the new virtual network adapter in the parent partition. This disabled network adapter is referred to as a Stub adapter because it is present, but disabled by design. • Disabling any unused network adapters. Figure 5-3. Implementation of Dedicated Network (Two Adapter System) Configuring the Dedicated Virtual Network Any settings assigned to the physical network adapter prior to the virtual switch creation is transferred to the new virtual network adapter.
3 Under Actions on the right, select Virtual Network Manager. In the Name field, enter a name for the virtual switch, vSwitch #1 (Dedicated) for this example. 4 Ensure External is selected, and click Add. Select the physical network adapter or LOM to be connected to the virtual switch. For example, the second LOM is selected and modified as needed based on the hardware available. NOTE: While configuring the new virtual network, you may configure a parent partition VLAN.
3 Make the following changes to the physical network adapter providing external connectivity to the virtual switch LOM #2: – Re-name this network adapter to vSwitch #1 to External Network Connection. – Disable power management for this network adapter by unselecting Allow the computer to turn off this device to save power (Network Adapter Properties→ Configure→ Power Management). – Set the speed and duplex for this network adapter. Select the speed to match the speed of your network.
Setting Up the VM and Configuring the Guest Operating System. The following represent Dell's best practices for setting up and configuring VMs in a Hyper-V environment while running on Dell systems. The recommendations presented here assume the host Hyper-V environment has already been configured using the best practice recommendations mentioned earlier in this document.
Setting Up the Network Driver for the Guest Operating System As mentioned earlier, Hyper-V offers a Legacy Network Adapter and a Synthetic Network Adapter for VMs. The legacy network adapter is an emulated Intel® 21140-based PCI Fast Ethernet Adapter device. This legacy device has a device driver in most supported guest operating systems. A device driver for the synthetic NIC is installed as part of the Integration Services installation.
Appendix A Best Practices for Administering Network Adapter Drivers This section provides instructions to install or upgrade the network adapter driver of a system running Microsoft® Hyper-V® Server 2008. Installing Network Adapter Drivers NOTE: It is recommended to use the latest drivers for your Dell™ PowerEdge™ system by downloading them from the Dell Support website at support.dell.com.
After you re-install the network adapter driver, follow the steps below to reconnect the virtual switch to the external network: 1 Select the virtual network in the Virtual Network Manager. 2 Change the connection type to External. 3 Select a valid physical network adapter or the physical network adapter that was previously connected to the virtual network.
Appendix B References • Dell Solutions for Windows Server 2008 Hyper-V available from the Dell and Microsoft- Virtualization Solutions for Today and Tomorrow website at dell.
• Hyper-V Functional Specification from http://www.microsoft.com/downloads/details.aspx?FamilyID=91e2e518c62c-4ff2-8e50-3a37ea4100f5&displaylang=en • WinHEC 2006 Presentation Slides from http://blogs.technet.com/virtualization/archive/2006/06/14/WinHEC2006-Slides.aspx • Dell High Availability Solutions Guide for Microsoft Hyper-V from support.dell.com.
Glossary CHILD PARTITION — Any partitian (VM) that is created by the root partition. DEVICE VIRTUALIZATION — A mechanism that lets a hardware resource be abstracted and shared among multiple consumers. EMULATED DEVICE — A virtualized device that mimics an actual physical hardware device so that guests can use the typical drivers for that hardware device. ENLIGHTENMENT — An optimization to a guest operating system to make it aware of VM environments and tune its behavior for VMs.
Glossary
Index B N Broadcom Advanced Control Suite, 14 NetBIOS, 20 F failover clustering, 19 Network Adapter Drivers reinstall, 42 uninstall, 41 upgrade, 41 Failover Clustering support, 23 Network Connections Manager, 26 G S gateways, 41 stateful, 13 stateless, 13 H hypervisor, 7, 9 stateless features, 13 Stub adapter, 36 subnet masks, 41 Switch-based tagging, 28 I Synthetic devices, 11 I/O Acceleration Technology, 13 Integration Services, 10 iSCSI support, 23 L Legacy devices, 11 T TCP offload eng
U upgrade drivers, 41 V Virtual Network Manager, 42 virtual service providers, 9 VLAN tagging, 14, 28 vSwitch, 17 W Windows Management Instrumentation, 21 Index 48
