Last Modified: Oct 19, 2025
Affected Product(s):
F5OS F5OS, F5OS-A, F5OS-C, Velos
Known Affected Versions:
F5OS-A 1.8.0, F5OS-A 1.8.3, F5OS-C 1.8.0
Fixed In:
F5OS-C 1.8.1
Opened: Mar 26, 2025 Severity: 2-Critical
- Large memory consumption by the l2_agent. - Tenant disruption on F5 rSeries appliance.
Eventually the system experience OOM (Out of Memory). On an F5 rSeries appliance, a tenant might experience disruptions and slowness, up to and including a TMM SIGABRT core.
- An F5OS system with SNMP configured and a LAG (Link Aggregation Group) with more than 1 member. - SNMP monitoring in use. We can check the l2_agent memory consumption by using `top` command. Ex: Top output showed a 15GB l2_agent process: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 19454 root 20 0 17.3g 14.9g 1788 S 0.0 5.9 174:04.57 /confd/bin/l2_agent -s appliance-1
None.
The l2_agent process no longer leaks memory.