Just in case someone has the same problem and finds this thread, the
solution was to reboot the switch.
That was it - no other changes required.
On 09/06/2017 04:07, Lyndon Nerenberg wrote:
> The first step is to have the switch display its idea of the LACP
> configuration and status. I haven't a clue how a TP-LINK does that, but on
> our Junipers it's 'show lacp interfaces'.
So I finally found my serial cable
TL-SG3424#show lacp
On 10/06/2017 19:15, Lyndon Nerenberg wrote:
> Not really, other than running tcpdump on the two interfaces and
> examining the LACP protocol packets to try to discover why the
> negotiation is acting the way it is.
OK, that sounds like an even deeper rabbit-hole.
> Also, if you don't have the en
On 09/06/2017 04:07, Lyndon Nerenberg wrote:
> The first step is to have the switch display its idea of the LACP
> configuration and status.
That's turning into a bit of a mission
Seems TP-LINK don't set an enable password by default so I can't get
what I need via ssh until I've set that. To
I'm trying to get LACP working over 2 ports (em0, em1). I've done this
successfully with FreeBSD and 4 ports on the same switch so I know it
can be done, I just can't get it working with OpenBSD. I'm hoping I've
just botched the config somewhere.
The switch is a TP-LINK TL-SG3424, latest firmware
5 matches
Mail list logo
