Thanks again for the post! It's only used when the page dirty rate of the VM's is faster then the ability to copy the pages to the destination host. SDPS only kicks in when a situation occurs that would mean a vMotion might otherwise fail. It's a failsafe mechanism. You may want to consider allowing more bandwidth for vMotion depending on the impact to particular applications you're seeing, or reducing the concurrency of vMotion operations by modifying some advanced settings.
Any changes should be tested. This should not be sufficient to notice any significant response time impact. If you have very latency sensitive applications then they may require special attention and tuning. Generally things just work, but for business critical applications and latency sensitive applications they do require a different approach and more care and attention.
Let me know what you find when you dig deeper and if necessary get VMware involved. I'd be keen to see what you come up with and exactly what the situation is. Great article. All other port groups, except management, all uplinks active, using route based on physical NIC load.
This reduces the chances of false isolation events a bit more. NIOC can still be used to control the quality of service.
I generally just use the normal, low, high shares without specifying specific values. It's all relative. As long as the important traffic types get the bulk of the shares for when there is congestion. That all makes sense. I really do envy your ability to test this stuff in that epic lab of yours. Good question Paul, and great answer Michael! Thank you for the very helpful information. I have been looking for an answer to this exact question for our VMware environment.
We have already gone to great lengths to setup our environment using the methods described in KB using NIC teaming. Aside from the additional configuration, is there any negatives to using this method versus the method you described above? Yes, you will in most cases not actually be able to use the aggregate bandwidth of multiple uplinks as any individual stream will be limited to the bandwidth of a single uplink. With multi-nic vMotion you can effectively use both NIC's all the time.
You are also now restricted to only using IP Hash as your load balancing algorithm, and all port groups on the vDS must be set to use it.
For this reason multi-nic vMotion and IP Hash load balancing a mutually exclusive. This won't be a problem if a single link is sufficient for vMotion traffic. You will need to ensure you use Network IO Control to prevent any one traffic type flooding out the others.
I'm wondering what the difference will be with a link failure between standby or Unused. If I have it set to standby and a link failure occurs during a vMotion, the vmkernel will get reassigned and the vMotion should complete successfully. But what about if it's set to unused? What will happen to the vMotion that is using that path during a link failure, will it timeout and fail?
Or will vMotion stop trying to use that VMK? If on your vmk vMotion port the other uplinks are set to unused and the active uplink fails the vmk port will loose network access. Switch skin Switch to the dark mode that's kinder on your eyes at night time. Switch to the light mode that's kinder on your eyes at day time. Latest Switch skin Switch to the dark mode that's kinder on your eyes at night time.
VMkernel properties. Create a second VMkernel port. Knowledge Sharing! But if your vMotion is configured with a single 1 Gb E adapter, it may take a considerable amount of time to complete vMotion operations. Hosts that have many running VMs, and especially those with higher guest memory allocations, will take longer to place a host into maintenance mode as guests are migrated to other hosts.
Reducing the time to enter maintenance mode can be an important factor to consider when you are applying ESXi patches, updating the physical host firmware, hardware or software upgrades, etc.
If you have the appropriate hardware , using 10 GbE will be much faster compared to 1 GbE. With either type, you can use two , or even more , adapters to improve the guest migration performance. Dedicate more physical adapters to vMotion and then c reate additional VMkernel interfaces for vMotion.
Below is an example of creating a vSwitch for vMotion that uses two adapters.
0コメント