Page MenuHomeFreeBSD

LACP w/ short timeout erroneously declares link-flapping

Authored by rpokala on Apr 26 2022, 6:20 PM.
Referenced Files
Unknown Object (File)
May 25 2024, 2:56 PM
Unknown Object (File)
May 19 2024, 7:32 PM
Unknown Object (File)
May 12 2024, 8:10 PM
Unknown Object (File)
May 7 2024, 2:29 PM
Unknown Object (File)
Apr 23 2024, 7:39 PM
Unknown Object (File)
Apr 19 2024, 1:58 AM
Unknown Object (File)
Apr 16 2024, 7:12 PM
Unknown Object (File)
Apr 16 2024, 6:52 PM



Panasas was seeing a higher-than-expected number of link-flap events. After joint debugging with the switch vendor, we determined there were problems on both sides; either of which might cause the occasional event, but together caused lots of them.

On the switch side, an internal queuing issue was causing LACP PDUs -- which should be sent every second, in short-timeout mode -- to sometimes be sent slightly later than they should have been. In some cases, two successive PDUs were late, but we never saw three late PDUs in a row.

On the FreeBSD side, we saw a link-flap event every time there were two late PDUs, while the spec says that it takes *three* seconds of downtime to trigger that event. It turns out that if a PDU was received shortly before the timer code was run, it would decrement less than a full second after the PDU arrived. Then two delayed PDUs would cause two additional decrements, causing it to reach zero less than three seconds after the most-recent on-time PDU.

The solution is to note the time a PDU arrives, and only decrement if at least a full second has elapsed since then.

Test Plan

Used in conjunction with buggy switch firmware, and also debug firmware which would delay PDUs on demand. One and two dropped or delayed PDUs did not result in a link-flap event, but three dropped or delayed PDUs did.

Diff Detail

rG FreeBSD src repository
Lint Not Applicable
Tests Not Applicable