Bug ID 2285753: Container Takes Multiple Attempts to Recover from daemon crash

Last Modified: Oct 16, 2026

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

Known Affected Versions:
2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4

Opened: Apr 21, 2026

Severity: 3-Major

Symptoms

If bgpd or other daemons crash or are killed in the f5-tmm-routing container this results in the container being restarted. On restart will see additional failures which take another container restart to recover.

Impact

F5-tmm-routing container will take additional cycle to recover from crash to one of its routing daemons. Routing will take that additional time to recover

Conditions

Bgpd is killed or crashes

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips