Documentos de Académico
Documentos de Profesional
Documentos de Cultura
8/10/12
Scenarios for using live migration without the required network con figuration
When your environment does not have the full set of network configuration requirements, the following list identifies some additional scenarios for using live migration: You plan to deploy Hyper-V in a production environment, and you would prefer to first test how the live migration feature works using your existing hardware. You would like to understand the network requirements for live migration before you acquire the hardware necessary for optimal performance. You have several blade servers in your enterprise environment, which, in general, do not include as many network adapters as other servers. You would like to use the live migration feature of Hyper-V, so that the virtual machines do not experience any downtime because your servers are updated and load balanced.
Storage
Usually, dedicated and High Access storage through iSCSI or Fibre Channel (Fibre private access. bandwidth and Channel does not need a network adapter). Refer to your low latency. storage vendor for guidelines. Public access which could be teamed for link aggregation or to fail over the cluster. Public access, which could be teamed to fail over the cluster.
Workloads running on virtual machines usually require external network connectivity to service client Varies requests.
Managing the Hyper-V management operating Low Management system. This network is used by Hyper-V Manager or bandwidth System Center Virtual Machine Manager (VMM).
Preferred network used by the cluster for communications to maintain cluster health. Also, used by Cluster Shared Volumes to send data Usually low Cluster and between owner and non-owner nodes. If storage bandwidth and access is interrupted, this network is used to access Cluster low latency. the Cluster Shared Volumes or to maintain and back Shared Occasionally, Private access
technet.microsoft.com/en-us/library /ff428137(d=printer,v =w s.10)
8/10/12
Volumes
up the Cluster Shared Volumes. The cluster should have access to more than one network for communication to ensure the cluster is highly available.
high bandwidth.
Live migration
8/10/12
The following table details the recommended, supported, and not recommended network configurations for live migration, and is organized in the order in which each network configuration is commonly used. Before reviewing the table, note the following: When a network adapter is connected to a virtual switch, it is referred to as a virtual network adapter. Network access for virtual machines can be on either a public or private network. To allow virtual machines access to computers on the physical network, they must be on a public network. The requirements for virtual machine access vary depending on network I/O needs and the number of virtual machines you are running on a single physical server. In addition to the preferred network for the cluster and the Cluster Shared Volumes, a cluster can utilize at least one additional network for communication. This increases the high availability of the cluster. The cluster should also be on a private network. If a network configuration is listed as not recommended in the following table, it should not be used because the performance of live migrations declines and cluster nodes might crash. Add another network adapter to separate traffic between live migration and Cluster Shared Volumes.
Host configuration
Management
Live migration
Comments
Virtual Network adapter Network network 2 adapter 3 adapter 1 Virtual network adapter 1 with bandwidth capped at 10%
3 network adapters Virtual with 1 Gbps; 2 adapters network are teamed for link adapter 1 aggregation (private)
Virtual network Virtual adapter 1 with network bandwidth adapter 1 capped at 10% Virtual network Virtual adapter 1 with network bandwidth adapter 1 capped at 1%
Network adapter 2
Network adapter 2
2 network adapters Virtual Network with 10 Gbps; 1 network Network adapter adapter 3 network adapter with 1 adapter 1 2 (1 Gbps) (10 Gbps) Gbps (10 Gbps) 2 network adapters Virtual
8/10/12
network Network adapter Network adapter 1 2 (1 Gbps) adapter 3 (10 Gbps) (1 Gbps)
3 network adapters Virtual with 1 Gbps; 2 adapters network are teamed for link adapter 1 aggregation (public)
Virtual network Virtual adapter 1 with network bandwidth adapter 1 capped at 10% Virtual network adapter 1 with bandwidth capped at 10%
Network adapter 2
Virtual 1 network adapter with network 10 Gbps; 1 network adapter 1 adapter with 1 Gbps (10 Gbps)
*This configuration is considered recommended if your configuration has a redundant network path available for Cluster and Cluster Shared Volumes communication.
8/10/12
the throttle rate to outbound traffic, regardless of the source port number of the traffic. 9. Under Specify the destination port number:, select To this destination port number or range, and then specify 6600 as the port number. This applies the throttle rate that you specified only to traffic with the destination port number or range you specify. You can configure a QoS policy to limit the network traffic for the IP address used by the management operating system. This ensures that network traffic outbound from the specified IP address does not exceed the limit you set. Use the procedure below to create a QoS policy to do this.
To create a QoS policy to limit network traffic for the IP address o n the management operating system
2. In IP Addresses, under This QoS policy applies to:, select Only for the following source IP address or prefix:, and then type the IP address for the management operating system. This applies the throttle rate that you specified to outbound traffic from a source IP address that you specify.
1. Follow Steps 1 through 5 in the procedure To create a QoS policy to limit live migration traffic.
Links Table
1http://go.microsoft.com/fwlink/?LinkId=164729 2http://go.microsoft.com/fwlink/?LinkId=182153 3http://technet.microsoft.com/en-us/library/47666237-c938-4fa7-9cb5-
b098f7884c3b(v=ws.10)#BKMK_manageCSVnetworks
4http://go.microsoft.com/fwlink/?LinkID=161361 5http://go.microsoft.com/fwlink/?LinkID=131362
Community Content
QoS on the Management port to help with backup bursts
Possible workaround for you Brian: you can use the same QoS principles listed to reserve a small % for the management. While this doesn't alter your initial point that backups could flood bandwidth, it does help in the usability department by ensuring you can always communicate with the server even during a backup.
1/13/2012 Justin.King
8/10/12