Re: [j-nsp] EX4550: LACP channels short lost after commit

Hi Olivier, thanks for your reply. At least it is something, that can be solved then ;-) I have two follow-up questions: - can I change it to periodic slow without any impact (because the other side is still on slow) or will that have to happen simultaneously because expecting fast does also

Re: [j-nsp] EX4550: LACP channels short lost after commit

You can have mixed config for slow/fast (but you want to have slow on each side) since "the transmitter honors the receiver’s rate" (juniper doc). If the link stays up but is no longer contiguous (a 10G wave over older transmission equipments, an L2VPN link...), you'll have a longer delay to

Re: [j-nsp] EX4550: LACP channels short lost after commit

Infamous LAG LACP flap... I think there are several factors: crappy Junos code, LACP is CPU managed (at least on EX), so a pike in CPU (or a latency in the dedicated process) can break LAGs (make them flap in fact). I had some similar issues with SRX code. Go for slow LACP rate (30 seconds

[j-nsp] EX4550: LACP channels short lost after commit

Hi everybody, yesterday we had a very small hickup on a bunch of EX4550 doing Layer2 only in a Virtual-Chassis. According to the logfiles, there were some LACP changes on multiple independent channels on various fpcs so I couldn't spot just one VC member as a source. Now, just 1 hour ago, I