Not to hijack the thread, but I wanted to add -- Just because the fiber
jumpers are new, does not mean they are clean.
I had a 40 gig link that started taking errors. Moreso when it was under
load. I personally cleaned everything. Still had issues. Replaced the
optics, no change. New, cleaned jumper. No change.
Eventually had our fiber techs look at it. When they scoped the jumpers,
they were awful. They cleaned them (one-click, and wipe style cleaner),
still bad. After a serious wet clean they finally pronounced them good.
Circuit has been fibe ever since.
On Mon, Feb 12, 2024 at 3:24 AM Saku Ytti via cisco-nsp <
cisco-nsp@puck.nether.net> wrote:
> On Mon, 12 Feb 2024 at 09:44, james list wrote:
>
> > I'd like to test with LACP slow, then can see if physical interface
> still flaps...
>
> I don't think that's good idea, like what would we know? Would we have
> to wait 30 times longer, so month-3months, to hit what ever it is,
> before we have confidence?
>
> I would suggest
> - turn on debugging, to see cisco emitting LACP PDU, and juniper
> receiving LACP PDU
> - do packet capture, if at all reasonable, ideally tap, but in
> absence of tap mirror
> - turn off LACP distributed handling on junos
> - ping on the link, ideally 0.2-0.5s interval, to record how ping
> stops in relation to first syslog emitted about LACP going down
> - wait for 4days
>
>
> --
> ++ytti
> ___
> cisco-nsp mailing list cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
