topic Re: lacp neg failed for sec then came up in General Topics

lacp neg failed for sec then came up

MP18 — Sun, 03 Mar 2019 18:06:54 GMT

got email alert

SYSTEM ALERT : critical : LACP interface ethernet1/21 moved out of AE-group ae1. Selection state Selected

system log shows

( severity neq informational ) and ( eventid eq nego-fail ) and ( description contains 'LACP interface ethernet1/21 moved out of AE-group ae1. Selection state Selected' ) and ( receive_time leq '2019/03/01 11:50:57' )

( receive_time leq '2019/03/01 11:50:57' ) and ( description contains 'LACP interface ethernet1/21 moved into AE-group ae1.' ) and ( eventid eq lacp-up ) and ( subtype eq lacp )

I check the switch logs all is good.

is there anything i can check on the PA side to know the cause of lap neo fail?

Re: lacp neg failed for sec then came up

jeremy.larsen — Mon, 04 Mar 2019 15:21:51 GMT

Have you verified Layer 1? I would check your cabling first. That's a pretty fast flicker if I'm reading your logs correctly. Also, are you using "lacp fast" or "lacp slow" timers? You could be mismatched.

Re: lacp neg failed for sec then came up

MP18 — Mon, 04 Mar 2019 17:19:00 GMT

Layer 1 is good.

My side is slow.

Re: lacp neg failed for sec then came up

MP18 — Mon, 04 Mar 2019 17:20:33 GMT

switch side is fast

Re: lacp neg failed for sec then came up

jeremy.larsen — Mon, 04 Mar 2019 17:26:10 GMT

I would match those then. Fast/Fast or Slow/Slow. Those decide the timers on each side of the LACP aggregate and they really should match.

Re: lacp neg failed for sec then came up

MP18 — Mon, 11 Mar 2019 16:00:47 GMT

can anyone please confirm this?

Fast/Fast or Slow/Slow. LACP timers should match?

Re: lacp neg failed for sec then came up

KasperT — Tue, 05 Apr 2022 14:25:09 GMT

Timers do not have to match. If devices have different transmission rates, each uses the rate of its peer.