System Center Virtual Machine Manager TechCenter >
System Center Virtual Machine Manager Forums
>
Virtual Machine Manager – General
>
SCVMM / Hyper-V - Networking/Teaming
SCVMM / Hyper-V - Networking/Teaming
- Hi all,
I need some ping pong on the subject matter.
Currently we are running some clusters, all HP servers with 2xQuad port NIC's. (Intel based) These are running in Load balance with Fault tolerance - in order to optimize bandwith while still having some failover.
However Im pondering a bit about the Teaming Non supported statement, on how then everyone else is then running their setup?
I mean if you cant team your NIC's your looking at multiple IP's instead which will turn out to be a real mess..
Any input is appriciated as we are currently seeing some funny things and basically dont trust our SCVMM at all because either:
1: Its too slow on updates.
2: States host not responding periodically.
Im interested in anything that would relate to the network around Hyper-V, SCVMM. Experience, How to, Best Practice - you got it, let me know ;)
Thanks in advance.
All Replies
- Hi jesper,
Microsoft KB for teaming
http://support.microsoft.com/kb/254101
The use of teaming on the private interconnect of a server cluster is not supported because of delays that could possibly occur in the transmission and receipt of heartbeat packets between the nodes. For best results when you want redundancy for the private interconnect, disable teaming and use the available ports to form a second private interconnect. This achieves the same end result and provides dual, robust communication paths for the nodes to communicate over.
Using teaming on the public or client networks is acceptable. However, if problems or issues seem to be related to teaming, Microsoft Product Support Services will require that teaming be disabled. If this resolves the problem or issue, you must seek assistance from the hardware manufacturer. For more information, see the online documentation about hardware compatibility tests on the Microsoft Web site.
Note In Windows Server 2008 and Windows Server 2008 R2, there are no restrictions that are associated with NIC Teaming and the Failover Clustering feature. In Windows Server 2008, the new Microsoft Failover Cluster Virtual Adapter is compatible with NIC Teaming and allows it to be used on any network interface in a Failover Cluster.
Teaming is a hardware related thing, Microsoft does not have teaming software and not supported means that (However, if problems or issues seem to be related to teaming, Microsoft Product Support Services will require that teaming be disabled. If this resolves the problem or issue, you must seek assistance from the hardware manufacturer. )
So, We are using teaming in our implementation for VMM and Hyper-V but we know that if we faced problem with that teaming we will do it our self as it is not Microsoft part.
For the rest of the problems
1: Its too slow on updates.
2: States host not responding periodically.
I have been working with VMM since it was beta and it is fine, Can you please send the detailed errors for those for more digging.
Regards,
If this post is helpful, please mark it as such. - Hiya,
thanks for the most excellent answer!
In releation to my problems:
1: How many virtual machines are you running on your cluster(how many nodes) that SCVMM is managing?
how long does it take for SCVMM to detect the virtual machine has move from node A to node B, if you move it from Failover Cluster Manager?
The reason I ask, is our development environment is running smooth without any problems. However thats only 4 machines and 2 nodes.
Our production is running 4 nodes with 58 Virtual Machines.
cluster node is HP DL580 128GB mem, 4xQuad Core 2.4 Xeon, 2xQuad Port Nic Teamed in loadbalance with faultolerance.
as far as I know this shouldnt be anything near a performance issue in terms of load, handle count or anything else. However we still experience that the SCVMM can take up to 5 mins before it discovers that a machine has been moved from one node to another... (if moved from failover cluster manager)
Regarding problem 2:
I'll see if I can set up some sort of tracing on this, however its close to impossible atm to predict when it happends... - We are running three node cluster for our testing. Some times You have to refresh VMM to detect the VMs after migration using Failover cluster. Have you tried to refresh it manually after migration ?
If this post is helpful, please mark it as such. - Hiya,
Yup - however the manual refresh does not pick it up.
Note: Manual detection on the 4 nodes takes 08mins 18 seconds... - Check this
http://technet.microsoft.com/en-us/library/dd221389.aspx
VM Light Refresher
Frequency: Every 2 minutes on each host.
Data updates:
- Checks the host status to determine whether the VMM agent is running and the status of the virtualization software on the host.
- Synchronizes the statuses of virtual machines deployed on the host.
- Places virtual machines with missing objects in a Missing state.
- Imports new virtual machines created outside VMM. When the refresher detects a new virtual machine, it imports the virtual machine into VMM and runs the VM Heavy Refresher to add virtual machine properties, resource pools, cluster information, and snapshots to the VMM database.
So I think the best way to do that for your hosts is to refresh the VM itself
Manual refreshes:
- VMM Administrator Console: Select the virtual machine, and click Refresh.
- Windows PowerShell – VMM: Refresh-VM.
If this post is helpful, please mark it as such. - Checks the host status to determine whether the VMM agent is running and the status of the virtualization software on the host.
