Skip to main content

vSphere Load Balancing policies

In this article let us see how vSphere Load Balancing policies permit you to specify how the network traffic distributed between physical network adapters and the way to re-route the traffic in case there is a network adapter failure.

There are five types of VMware load balancing options available, these VMware load balancing policies are available at vSwitch and dvSwitch is to control the Outgoing traffic.

vSphere Load Balancing policies

vSphere Load Balancing policies

VMware vSwitch Load Balancing Best Practice:

1. Route based on originating Virtual Port
2. Route based on Source MAC Hash
3. Route based on IP hash
4. Route based on Physical NIC load
5. Use Explicit failover ordervSphere Load Balancing policies

1. Route based on originating Virtual Port

In this particular load balancing policy, Virtual ports of the vSwitch are linked to the Physical network adapter. These physical network adapters are dependant on the virtual Port ID where the virtual machine is connected. Network traffic from that specific virtual machine’s virtual Ethernet adapter is actually sent only to the identical Ethernet adapter until and unless there’s a failure of that particular physical Ethernet adapter. Therefore, There’ll be a failover to an alternative physical adapter in the NIC team. This is the default load balancing policy.

Kemp Load Balancer Review
VMware VCSA 6.5 Backup and Restore

2. Route based on Source MAC Hash

In Route based on Source MAC Hash load balancing policy, Each and every Virtual machine outbound traffic is going to be mapped to particular physical NIC depending on the hash of Virtual Machine NIC’s MAC address. Traffic from the specific virtual NIC is actually sent to exactly the same uplink adapter unless there is a failure of these specific uplink adapter. Even replies are received on the same physical adapter.

3. Route based on IP hash

This vSphere Load Balancing policy technique require higher CPU overhead., Physical Nic for an outbound packet is chosen based on its source and destination IP address. Physical uplink will be selected based on the hash of the source and destination IP address of each packet sent through the VM.

Difference between NAS vs DAS vs SAN vs Cloud Storage
VMware Storage DRS Best Practices

4. Route based on Physical NIC load

This VMware vSwitch load balancing policy prefers a uplink depending on the current load of the physical network adapters. This load balancing policy work with an algorithm to execute a regular inspection of load on the Physical NICs every Thirty seconds. Once the usage of Particular physical uplink exceeds 75% over thirty seconds, the hypervisor will move VM’s traffic to another uplink adapter. This load balancing doesn’t require any extra configuration on the physical switch level. This load balancing policy is only available as a part of dvSwitch and which is unavailable in Standard switches.

5. Use Explicit failover order

This Explicit Failover Order always utilizes the largest order uplink through the listing of Active uplink adapters. In the instance of failover or both active uplink adapters failed, Standby adapters is going to be used. Move the adapters up and down depending on the requirement. uplinks adapters under Unused uplink is not going to use for the communication.

Leave a Reply

Your email address will not be published. Required fields are marked *