Last Modified: Dec 08, 2025
Affected Product(s):
F5OS Install/Upgrade, Velos
Known Affected Versions:
F5OS-C 1.8.2
Opened: Oct 28, 2025 Severity: 3-Major
1. Output of "show fpga-tables vqf-voq-stats" on a partition will show 0s in IMM_ENABLED column for affected destination blade. For example: partition-1# show fpga-tables vqf-voq-stats EMM IMM SMS SLOT NAME ENABLED ENABLED DRPLVL PKT CNT BYTE CNT ---------------------------------------------------------- 1 1.15 1 1 65535 212663 30410809 1 1.4 1 1 65535 106066 15170734 1 1.9 1 1 65535 122845 22230707 1 2.15 1 1 65535 416 67808 1 2.4 1 1 65535 110 23540 1 2.9 1 1 65535 0 0 1 3.15 1 1 65535 26772858 2222180494 1 3.4 1 1 65535 991 194844 1 3.9 1 1 65535 7 611 1 4.15 1 0 65535 0 0 <== 1 4.4 1 0 65535 0 0 <== 1 4.9 1 0 65535 0 0 <== 1 5.15 1 1 65535 415 67645 1 5.4 1 1 65535 12 1926 1 5.9 1 1 65535 2 170 IMM_ENABLED ?is 0 for 4.15,4.4 and 4.9, which means that blade1 will not send traffic to either of the blade4 ports including to tenants deployed on blade4. 2. Partition velos.log will have similar "Could not acquire lock" for voq-state component creation/deletion errors after trying to set EMM state or activation status of the peer blades (there can be number of similar occurrences along the log): fpgamgr[12]: nodename=blade-4(p1) priority="Info" version=1.0 msgid=0x305000000000005 msg="VoQ programmed" blade=2 port=4 module="EMM" state="enabled". fpgamgr[12]: nodename=blade-4(p1) priority="Info" version=1.0 msgid=0x305000000000005 msg="VoQ programmed" blade=2 port=9 module="EMM" state="enabled". fpgamgr[12]: nodename=blade-4(p1) priority="Info" version=1.0 msgid=0x305000000000005 msg="VoQ programmed" blade=2 port=15 module="EMM" state="enabled". fpgamgr[12]: nodename=blade-4(p1) priority="Err" version=1.0 msgid=0x302000000000009 msg="Failed to delete CDB component" COMPONENT="/voq-states/voq-state" ERROR="locked" LASTERR="Could not acquire lock" ERRNO=10. or fpgamgr[13]: nodename=blade-8(p1) priority="Info" version=1.0 msgid=0x305000000000023 msg="Enabling VQF synchronization with slot" slot=1. fpgamgr[13]: nodename=blade-8(p1) priority="Info" version=1.0 msgid=0x305000000000024 msg="Slot activation status updated in VQF" slot=1 status=1. fpgamgr[13]: nodename=blade-8(p1) priority="Err" version=1.0 msgid=0x302000000000003 msg="Failed to create CDB component" COMPONENT="/voq-states/voq-state{%d %d}" ERROR="locked" LASTERR="Could not acquire lock" ERRNO=10. fpgamgr[13]: nodename=blade-8(p1) priority="Info" version=1.0 msgid=0x305000000000023 msg="Enabling VQF synchronization with slot" slot=2. fpgamgr[13]: nodename=blade-8(p1) priority="Info" version=1.0 msgid=0x305000000000024 msg="Slot activation status updated in VQF" slot=2 status=1. fpgamgr[13]: nodename=blade-8(p1) priority="Err" version=1.0 msgid=0x302000000000003 msg="Failed to create CDB component" COMPONENT="/voq-states/voq-state{%d %d}" ERROR="locked" LASTERR="Could not acquire lock" ERRNO=10. fpgamgr[13]: nodename=blade-8(p1) priority="Info" version=1.0 msgid=0x305000000000023 msg="Enabling VQF synchronization with slot" slot=3. fpgamgr[13]: nodename=blade-8(p1) priority="Info" version=1.0 msgid=0x305000000000024 msg="Slot activation status updated in VQF" slot=3 status=1. fpgamgr[13]: nodename=blade-8(p1) priority="Err" version=1.0 msgid=0x302000000000003 msg="Failed to create CDB component" COMPONENT="/voq-states/voq-state{%d %d}" ERROR="locked" LASTERR="Could not acquire lock" ERRNO=10.
The impact will be related to inter-blade traffic. If imm_enabled is 0 for an affected destination blade, ingress traffic entering the chassis on one blade destined to the tenant deployed on the affected blade will not reach the tenant.
Multi-bladed chassis is rebooted after an upgrade to 1.8.2.
Reboot affected blade, on partition issue: cluster nodes node blade-X reboot X being the number of the affected blade.
None