Skip to main content

6 Messages

 • 

120 Points

Mon, Sep 16, 2019 11:46 AM

load balancing mode of a LAG

I need to check the load balancing mode of the lags on the physical switches (ICX6610, 08.0.30t) facing our esxi cluster. On the cluster side, at the virtual switches, the balancing mode is currently "Source and destination IP address". The manual is a bit vague of the modes and I can't seem to find a command to modify the mode in the physical switch.

The manual says (a snippet...):

Layer 2 Bridged TCP/UDP: Source and destination MAC addresses, source and destination IP addresses, and source and destination TCP/UDP ports.
...
Layer 2 Bridged IPv4 TCP/UDP  Source and destination IP addresses, and source and destination TCP/UDP ports.

So what is the difference here with "bridged tcp/udp" and "bridged ipv4 tcp/udp"? And are those different, selectable modes?

Eg "src & dst ip address and tcp/udp port" is one of the possible selections on the cluster side. Would that be a better combination for icx?









Responses

Employee

 • 

100 Messages

 • 

2.1K Points

a year ago

Hi

LAG load balancing is fixed and cannot be changed, the method used depends on the traffic type (this is described in the L2 config guide). Symmetric load balancing can be enabled if required (some firewalls need this) but it does not alter the traffic distribution across the links.

6 Messages

 • 

120 Points

Simon, thanks for your prompt response.

What you would see what is the correct or most proper setting then on the cluster side?

And would you please open the difference btw "bridged tcp/udp" and "bridged ipv4 tcp/udp"?

Employee

 • 

100 Messages

 • 

2.1K Points

Hi, I think this could be a documentation error, I will need to check and will get back to you ASAP.
 

Employee

 • 

100 Messages

 • 

2.1K Points

I can confirm that this is an error in the documentation and the entry for "Layer 2 Bridged TCP/UDP" will be removed from the next version of the L2 config guide.

The entries for "bridged ipv4 tcp/udp" and "bridged ipvd tcp/udp" describe the hashing for TCP/UDP traffic.

6 Messages

 • 

120 Points

Simon, thanks for this. It really clarifies a bit.

So, if the mode in the switch is fixed to "Source and destination IP addresses, and source and destination TCP/UDP ports" and the modes available on the vsphere are (amogst others) "src and dst ip address", "src and dst ip address and tcp/udp port" or "src and dst tcp/udp port" would you think that "src and dst ip address and tcp/udp port" is the closest match? It may be obvious but I'm baffled with nuances here. Also how crucial are the actual effects of (slightly) wrong selection?


Employee

 • 

100 Messages

 • 

2.1K Points

Hi

I'm afraid I can't comment on the vsphere config. with any confidence as it's not something that I have any experience with, but from what you have described "src and dst ip address and tcp/udp port" looks like the best match to the ICX behavior. The only way to be certain with be to perform some testing which is not something that we would be able to do.

Hopefully someone else on here has some relevant experience and can share some real-world insights.

6 Messages

 • 

120 Points

a year ago

Vu, Thanks for you informative input. Really appreciate it. I think i get it now.