Last Modified: Jan 29, 2026
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4, F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Jan 04, 2025 Severity: 2-Critical
This failure looks like an RQM lockup. An RQM lockup can show up as a DMA receive failure or a DMA transmit failure. Receive failure because the receive queue will not accept HBM memory writes. Transmit failure because loopback health check packets will back up and flow control the transmit data-path. - A partition's tenants may be unreachable while another partition is unaffected. - System health output (show system health) will report something similar to "blade-X overall-health = Unhealthy/Critical; other blades/controllers healthy." - A partition's blade will log its velos.log file occurrence(s) of ATSE register dumps and "ring hung", for example: <timestamp> ACTIVE dma-agent[13]: nodename=blade-1(p2) priority="Alert" version=1.0 msgid=0x4201000000000130 msg="Health monitor detected DM Tx Action ring hung." ATSE=0 DM=2 OQS=2. <timestamp> ACTIVE dma-agent[13]: nodename=blade-1(p2) priority="Info" version=1.0 msgid=0x4201000000000137 msg="Health monitor DM register dump complete." FILE="agent-dump-1764975200.txt".
This causes a data-path lock-up and traffic will not be passed by the affected blade.
No known conditions. This typically happens on initialization, but has been seen at runtime.
Reboot the system.
None