Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Configuring network load distribution for Fault Tolerance logging traffic (1011966)

Purpose

This article provides information on configuring NIC teaming for the purpose of load distribution for Fault Tolerance (FT) logging traffic.

 

Resolution

ESX supports NIC teaming with four different load distribution policies for outbound traffic:
  • Route based on originating virtual port ID
  • Route based on IP hash (using both source and destination IP addresses)
  • Route based on source MAC hash
  • Explicit failover
The default load balancing policy is Route based on originating virtual port ID. Because all FT logging traffic from a specific host originates from the same source port and MAC address, neither the default load balancing policy nor the Route based on source MAC hash policy distribute the traffic to multiple uplinks.
 
For traffic to be distributed, configure the virtual switch through which the logging traffic flows to use the Route based on IP hash policy. This policy uses both source and destination IP addresses of the traffic flow to determine the uplink. FT pairs between different ESX hosts use more than one source and destination address pair for the FT logging.
 
To use the Route based on IP hash policy, the ports on the physical switch must be configured in etherchannel mode. For more information about choosing the Route based on IP hash policy and about the configuration of the ports on the physical switch, see Sample configuration of EtherChannel / Link aggregation with ESX 3.x and Cisco /HP switches (1004048).

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 14 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 14 Ratings
Actions
KB: