VSAN and Teaming NIC
Posted: Mon Apr 15, 2019 1:30 pm
Hi,
We are considering using vsan free. Still we have a problem to understand what is the exact position of Starwind about network teaming. Let me explain.
We have 2 hosts hyper-v with 4 *10Gbit interfaces and 16 *1Gbit interfaces. We are planning to use the network like that:
1 teaming for ISCSI and Heartbeat => 2*10Gbit interfaces . LACP configured on switchs
1 teaming for Synchronisation => 2*10Gbit interfaces . LACP configured on switchs
1 teaming for management => 2*1Gbit interfaces . LACP configured on switchs
for the others interfaces available will assign them later to vms.
The purpose of this configuration should be to have the performance and failover ready for any case of problem.
I read VSAN doesn't support any kind of teaming. Is it still true? What would you recommend to have failover configuration and good performance?
Thank you
We are considering using vsan free. Still we have a problem to understand what is the exact position of Starwind about network teaming. Let me explain.
We have 2 hosts hyper-v with 4 *10Gbit interfaces and 16 *1Gbit interfaces. We are planning to use the network like that:
1 teaming for ISCSI and Heartbeat => 2*10Gbit interfaces . LACP configured on switchs
1 teaming for Synchronisation => 2*10Gbit interfaces . LACP configured on switchs
1 teaming for management => 2*1Gbit interfaces . LACP configured on switchs
for the others interfaces available will assign them later to vms.
The purpose of this configuration should be to have the performance and failover ready for any case of problem.
I read VSAN doesn't support any kind of teaming. Is it still true? What would you recommend to have failover configuration and good performance?
Thank you