asked on
Nic teaming with vmware and HP Procurve won't work.
I am setting up a vmware 6.7 host with 6 nic's in a team connected to a HP procurve switch. To my best knowledge the vmware virtual switch should be configured with "route based on IP-hash" for load balancing in the "Nic teaming"-settings. The relevant HP procurve ports should be configured as " Trk1 Trunk"
I've done this before on earlier vmware editions, but this time it won't work. When I enable trunking in the switch, i can ping the management ip for a minute longer, and then it stops. I tried to restart the management network to no avail. What's strange is that the management network gets an IP from the DHCP, but it's still unreachable with ping, and the gui webpage does not answer. When removing the trunk settings on the switch I can contact the management network again.
Any clues people?
I've done this before on earlier vmware editions, but this time it won't work. When I enable trunking in the switch, i can ping the management ip for a minute longer, and then it stops. I tried to restart the management network to no avail. What's strange is that the management network gets an IP from the DHCP, but it's still unreachable with ping, and the gui webpage does not answer. When removing the trunk settings on the switch I can contact the management network again.
Any clues people?
Switches / HubsNetworkingVMware
Last Comment
MrWhy
ASKER
Static trunks.
All uplinks active and set as trunk.
6 Uplinks. I got them. Might as well use them.
Not sure what you mean by "link status-only", but all leds are green.
Notify switches is on
I had failback set to Yes. I changed it, and it seemed to work for a while, but after 5 minutes, it stopped responding to ping. Just as before.
All uplinks active and set as trunk.
6 Uplinks. I got them. Might as well use them.
Not sure what you mean by "link status-only", but all leds are green.
Notify switches is on
I had failback set to Yes. I changed it, and it seemed to work for a while, but after 5 minutes, it stopped responding to ping. Just as before.
ASKER
Yep. Link status only. (Found it)
Were the correct VLAN settings applied to the Trunk as well? (trk != its constuent interfaces).
ASKER
No VLAN set on either side. Only Untagged Trunk group Trk2. This used to work with vmware 4.5 back in the days.
Besides, when activating the trunking on the switch, it works for five minutes before it dies. Wrong vlan should prevent it from working altogether or?
Restarting switch does not help. Removing trunk works, but then I guess teaming will not work or?
Besides, when activating the trunking on the switch, it works for five minutes before it dies. Wrong vlan should prevent it from working altogether or?
Restarting switch does not help. Removing trunk works, but then I guess teaming will not work or?
Teaming option needs to match, so you could select Route based on ID et
test etc
test etc
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you Sebastian Talmon.
That was it. I enabled NIC Teaming based on IP hash specifically on the management portgroup, and now it works like a charm. It would have taken me ages to figure that one out myself.
That was it. I enabled NIC Teaming based on IP hash specifically on the management portgroup, and now it works like a charm. It would have taken me ages to figure that one out myself.
All uplinks are active, and in he same channel mode (e.g. trunk)
Link Status - only
Notify Switches - Yes
Failback - No
6 Uplinks ? 1Gbe - is that not too many ? e.g. do you need that many ?
What you describe does sound very much like teaming is broken.