LACP supports works with 2 switches, but if you wish to aggregate all links - you need
switch support (high-end hardware).
Best Regards,
Strahil NikolovOn Aug 6, 2019 18:08, Vincent Royer <vincent(a)epicenergy.ca> wrote:
I also am spanned over two switches. You can use bonding, you just can't use 802.3
mode.
I have MGMT bonded to two gig switches and storage bonded to two 10g switches for
Gluster. Each switch has its own fw/router in HA. So we can lose either switch, either
router, or any single interface or cable without interruption.
On Tue, Aug 6, 2019, 12:33 AM Mitja Pirih <mitja(a)pirih.si> wrote:
>
> On 05. 08. 2019 21:20, Vincent Royer wrote:
> > I tried deployment of 4.3.5.1 using teams and it didn't work. I did
> > get into the engine using the temp url on the host, but the teams
> > showed up as individual nics. Any changes made, like assigning a new
> > logical network to the nic, failed and I lost connectivity.
> >
> > Setup as a bond instead of team before deployment worked as expected,
> > and the bonds showed up properly in the engine.
> >
> > ymmv
> >
>
> I can't use bonding, spanned over two switches.
> Maybe there is another way to do it, but I am burned out, anybody with
> an idea?
>
> The server has 4x 10Gbps nics. I need up to 20Gbps throughput in HA mode.
>
>
> Thanks.
>
>
>
> Br,
> Mitja