Last Modified: Nov 25, 2025
Affected Product(s):
F5OS F5OS-A, F5OS-C
Known Affected Versions:
F5OS-C 1.8.2
Opened: Sep 30, 2025 Severity: 2-Critical
When neighbouring switches are configured with a low LLDP update timer (around 1 to 10 seconds) and LLDP is enabled on multiple interfaces (more than five), the LLDP details in F5OS ConfD may eventually either get wiped out or fail to update.
LLDP info will be lost and/or failed to update.
A low LLDP update timer (1 to 10 seconds) combined with LLDP being enabled on multiple interfaces.
Update the LLDP update timer on the neighboring switch to more than 30 seconds and wait for some time to allow the system to stabilize and return to normal. For an immediate resolution, delete the LLDP pod in the cluster using the following steps: [root@controller-1:Active ~]# kubectl get pods --all-namespaces | grep lldp partition-1 lldpd-7d7f465488-s7pw5 1/1 Running 0 17h [root@controller-1:Active ~]# kubectl delete pod lldpd-7d7f465488-s7pw5 -n partition-1 pod "lldpd-7d7f465488-s7pw5" deleted
None