Bug ID 1696325: Unresolved VQF IMM watchdogs after system controller failover, VoQ Window Errors, and extensive disconnect to confd

Last Modified: Oct 19, 2025

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-C 1.8.1

Opened: Oct 14, 2024

Severity: 2-Critical

Symptoms

The VoQ IMM Enabled status in the fpga-tables vqf-voq-stats output from the CLI remains 0 indefinitely resulting in traffic loss between blades. Example: show fpga-tables vqf-voq-stats COS MEM COS WIN EMM IMM SMS FILL FULL HI COS LO SMS EMM IMM ERR SLOT NAME ENABLED ENABLED DRPLVL PKT CNT BYTE CNT DROP DROP DROP DROP DROP DROP DROP CNT -------------------------------------------------------------------------------------------------------------------------- 3 13.12 1 0 32767 1819895878 2330473381038 200121 0 0 86532 0 14 9 0 3 13.13 1 0 32767 1815815755 2322725261469 251277 0 0 58031 0 14 9 0 3 13.14 1 0 32767 1824204787 2337092078111 211707 0 0 1528 0 14 9 0 3 13.15 1 0 32767 1839939128 2357633747305 208636 0 0 0 0 14 9 0 3 13.4 1 0 32767 0 0 0 0 0 0 0 14 9 0 3 13.9 1 0 5427 0 0 0 0 0 0 0 14 9 0

Impact

Traffic loss from the blade reporting the zero values for IMM Enabled towards the destination blade. The destination blade is indicated by the first number in the decimal of the "NAME" column. For instance, if the IMM ENABLED values are 0 for "Slot 3 and NAME "13.12", this indicates that traffic from slot 3 towards slot 13 will be lost.

Conditions

A temporary loss of the dataplane links between the system controller and a blade on a system, followed by an extensive outage for that blade to the confD database.

Workaround

Reboot the blades reporting the IMM Enabled values of 0.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips