I am using ESXi 6.0 with the Infrastructure Client and trying to determine whether I can team two NIC's for the uplink on a vSwitch.
With free Hyper-V 2012 R2 it was very easy setting up a LACP team, and with configuring the physical switch, I got a nice 2Gbit/s NIC.
Under ESXi I can add more then one NIC to the vSwitch, and with the ports on the physical switch still LACP enabled, I have no network problems. But I believe it's only load balancing, nothing else.
The documentation I dug up so far all speak about using vSphere for LACP, or creating EtherChannels, which is mainly Cisco it seems. Both of which I do not have.
I can set up static port groups on the physical switch, but I am uncertain how that works.
Before people start asking why I need this, I don't. I just like to create a two NIC uplink for the vSwitch for redundancy. That is the main thing. And if I can set it up for a 2Gbit/s team that would be cool.
Setting it up as a failover setup is easy of course
With free Hyper-V 2012 R2 it was very easy setting up a LACP team, and with configuring the physical switch, I got a nice 2Gbit/s NIC.
Under ESXi I can add more then one NIC to the vSwitch, and with the ports on the physical switch still LACP enabled, I have no network problems. But I believe it's only load balancing, nothing else.
The documentation I dug up so far all speak about using vSphere for LACP, or creating EtherChannels, which is mainly Cisco it seems. Both of which I do not have.
I can set up static port groups on the physical switch, but I am uncertain how that works.
Before people start asking why I need this, I don't. I just like to create a two NIC uplink for the vSwitch for redundancy. That is the main thing. And if I can set it up for a 2Gbit/s team that would be cool.
Setting it up as a failover setup is easy of course