Bug ID 1068837: When LLDP is enabled, rebooting one blade may cause traffic failure on another blade.

Last Modified: May 26, 2022

Bug Tracker

Affected Product:  See more info
F5OS Velos(all modules)

Opened: Dec 17, 2021
Severity: 1-Blocking


In a VELOS chassis with two or more blades installed, when LLDP is enabled globally or on any front panel link, rebooting the blade which hosts the LLDP daemon may cause one of the other blades in the chassis to loose traffic connectivity approximately one minute after the first blade is rebooted. The blade may drop all further non-management traffic until it is also rebooted.


Another blade in the chassis may loose all non-management network traffic until it is rebooted.


LLDP must be enabled in the partition CLI. The blade which is rebooted must be the blade which is currently hosting the lldpd daemon. The issue is intermittent upon blade reboot.


This issue is not present if LLDP is disabled in the partition CLI. Rebooting the degraded blade should recover it to an operational state, though it is possible to encounter the issue again, back-to-back.

Fix Information


Behavior Change