Last Modified: Jun 26, 2025
Affected Product(s):
F5OS F5OS, F5OS-A, F5OS-C, Velos
Known Affected Versions:
F5OS-A 1.8.0, 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 rSeries appliance
Eventually the system experience OOM (Out of Memory). On an 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
Restart the L2_agent process on the F5OS host. On an rSeries appliance, one of the following: - as root, run the command 'docker restart system_L2' - as an administrative user from the F5OS CLI, enter config mode and then run 'system diagnostics os-utils docker restart node platform service system_L2' On a VELOS system, restart the partition<ID>_L2 instance on each controller. Log into the system controller as an administrative user, enter config mode, and then run: system diagnostics os-utils docker restart node controller-1 service partition1_L2 system diagnostics os-utils docker restart node controller-2 service partition1_L2 (Adjust 'partition1' to the partition ID for the partition in question)
The l2_agent process no longer leaks memory.