ESXi

Hi

I am having some trouble setting up network load balancing in VMware - I am not quite sure which load balancing mode I should use.

I have an ESXi 5.5-host hooked up to an HP Procurve Switch which I have configured for 2 VLANs (40,41).

On the switch I created 2 trunks (Trk10, Trk20) which I tagged in both VLANs:

trunk 23,47 Trk10 Trunk

trunk 24,48 Trk20 Trunk

vlan 40

   name "Proces"

   untagged 1-22

   tagged 50,Trk10,Trk20

   no ip address

   exit

vlan 41

   name "PLC"

   untagged 25-46

   tagged Trk10,Trk20

   no ip address

   exit

Port 23 and 47 is going to ESXi-host1 and port 24,48 are going to ESXi-host2.

VLAN 40 is ment to have network 192.168.40.0/24.

VLAN 41 is ment to have network 192.168.41.0/24.

I created a virtual switch which has the 2 NICs in it, but how should the load balancing mode be set?

The virtual machine is slow on the internet right now and i suspect the packages going to the wrong VLAN.

(Right now the load balancing mode is set to "Route based on the originating virtual port ID").

Regards,

Soren

Let me know if you need more info.

You would need "Route based on IP hash" on your ESXi vSwitch and portgroups as the HP config. aggregates multiple links..(HP trunk)

Are there any specific needs for these trunks? If not I would ditch them on the HP side and go with the standard "Route based on the originating virtual port ID" unless this is a Distributed vSwitch..

/Rubeck

Hi again

I am not quite sure on why they were made in the first place, since it is a preconfigured switch I am working on.

I guess it was made for redundancy if one of the ports would malfunction.

I am not quite sure on what you mean - should i just have a cable in each VLAN (untagged), and then create 2 virtual switches instead?

Any chance you could share the entire HP switch config?  And a screen shot of the networking config on the ESXi box?

/Rubeck

Sure :smileyhappy:

I am not a master at VMware, so I dont know if its the smartest setup or if there is another way which would be better.

AspectServer1 has 2 NICs:

192.168.40.35 (VLAN 40)

192.168.41.35 (41)

ProcesDC1:

192.168.40.30 (40)

AspectServer2 is not configured yet.

Could you do a "show interface brief" and "show interface" on the HP switch and paste it here?

I would remove the trunks as I can't see why this is needed in your setup..

Verify that Route based on the originating virtual port ID is selected on vSwitch1 and on the two configured portgroups (PLC and Proces).

Remove the trunks on the HP switch and tag/untag required VLANs onto the individual ports which were used previously as a part of these trunks.. 

Quick config needed for the HP..

conf t

no trunk 23,47 Trk10 Trunk

no trunk 24,48 Trk10 Trunk

vlan 1

untagged 23,24,47,48

vlan 40

tagged 23,24,47,48

vlan 41

tagged 23,24,47,48

WARNING: You might have some network hickups when doing this..

What switch model do you use.. ?

/Rubeck

Your fix seems to work :smileywink:

I dont have the ability to test if the VLAN41 is working, but I expect it will.

Thank you,

Regards,

Soren

You're welcome, Soren....

Skriv endelig hvis der er noget der driller :smileywink:

/Rubeck

Haha det skal jeg nok :smileywink: