Testing Juniper switches: they've managed to create an L2 loop *internally*, dhcpd 100% CPU, and LACP is fail. Are they really this crap?
-
... and it works after rebooting. Guess what,
@JuniperNetworks? Rebooting to make config changes work isn't acceptable. Vendor disqualified.
*Both* stacking *and* LACP badly misbehaved until I rebooted both switches. This is seriously broken.
-
-
Hmmm it's like any system with "Switch" in it's name is a gigantic disaster
-
Nintendo "Switch" begs to differ.
- Show replies
New conversation -
-
-
Ugh, it wasn't rebooting that fixed it. Turns out if the slave switch boots first and becomes master, then slave again, the problem happens.
-
So simply disconnecting the stack link and reconnecting it is enough to reproduce. And whether it happens on cold boot depends on boot time.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.