Bug ID 2440693: Stale NAT kernel routes remain after routing container restart

Last Modified: Oct 16, 2026

Affected Product(s):
BIG_IP_NEXT(BNK) BNK(all modules)

Fixed In:
2.3.3, 2.2.4

Opened: Jul 23, 2026

Severity: 2-Critical

Symptoms

A routing container restart can leave stale NAT kernel routes when the system updates NAT policy mid-restart (for example, during an OOM-triggered restart).

Impact

A stale route is invalid or could cause cross-pod BGP route advertisements

Conditions

Occurs when, - The routing container is restarted - The NAT policy addresses are modified.

Workaround

Restart the entire Pod, or just tmrouted container.

Fix Information

During reinitialization of the routing daemon a full load sync of routes will occur.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips