Operating System - VMware
1752805 Members
5682 Online
108789 Solutions
New Discussion юеВ

Re: NIC teaming on different switches

 
SOLVED
Go to solution
Antonio_73
Advisor

NIC teaming on different switches

I'm planning to setup a redundant and reliable environment, using more servers and more switches, all based on vmware sphere, hp servers, storages and switches.
Currently I have two DL585 G2 with eight 1GB ports for each server, and two Procurve 2810-24G switches. I want each server to have access to two switches, for every connection.
About iSCSI, I'm planning to use multipathing on dedicated single NICs, so usage of different switches is ok.
Problem arises with NIC teaming for all remaining connections, as vmware states it can be done only on single or stacked switches.
Is the Procurve 2810-24g stacking suitable for this operation or does vmware means another kind of stacking?
Is there anyone wich solved already this problem, having the network always on despite of switch hangs?
Thanks
5 REPLIES 5
Uwe Zessin
Honored Contributor
Solution

Re: NIC teaming on different switches

You can do NIC teaming on non-stacked switches as long as you don't select an incompatible load balancing mode that sends the same MAC address across multiple pNICs (route based on IP hash).
.
Antonio_73
Advisor

Re: NIC teaming on different switches

I tried setting a fixed failover order in the teaming (port1-sw1, port2-sw1, port3-sw2,port4-sw2), but after disabling ports on the switch sw1 all hangs.

Uwe Zessin
Honored Contributor

Re: NIC teaming on different switches

Please define "disabling ports" - did it drop the link?
.
Antonio_73
Advisor

Re: NIC teaming on different switches

I disabled ports on the swicth, so they were 'disconnected' on the vmware side.
Antonio_73
Advisor

Re: NIC teaming on different switches

All is working as wanted, in double switch redundant configuration.

Setting IP hash on vmware side, and trunking on switch side (each switch has his own trunk) works well.

The hang was caused by an apparently inoffensive unmanaged switch, linked to both 2810 switches, which instead was managed and caused spanning tree to exclude the second 2810.

Thanks for previous answers.