Last Modified: May 29, 2024
Affected Product(s):
F5OS F5OS
Known Affected Versions:
F5OS-A 1.1.1, F5OS-A 1.2.0
Fixed In:
F5OS-A 1.4.0, F5OS-A 1.3.0
Opened: Sep 30, 2022 Severity: 2-Critical
LACP and LLDP messages transmitted from an F5OS r2x00/r4x00 appliance to a peer switch have an incorrect length, and are ignored by some switches. This can result in LACP aggregate links configured between an F5OS appliance and peer switch to fail to establish. For example, Extreme Networks switches may produce a message similar to this: <Erro:LACP.RxPDUSizExcd> Slot-2: Received PDU LACP size exceeded. Incoming Port: 1:1 PDU size: 132 required size: 128 Juniper hardware may produce messages similar to this: kernel: xe-1/1/1: received pdu - length mismatch for lacp : len 128, pdu 124 like 1 LLDP packets sent from the F5OS device may not be accepted or correctly interpreted by the connected switch.
Unable to establish an LACP trunk between the F5OS r2600/r2800/r4600/r4800 and a network switch.
-- rSeries r2600/r2800/r4600/r4800-series appliance -- LACP trunk (aggregate link) configured (or) -- LLDP advertising enabled
Configure the LAG using a static configuration (that is, no LACP) on both sides, if possible.
Fixed code to trim extra 4 bytes going in the BPDUs.