Bug ID 2181633: Large BIG-IP SSL Orchestrator deployments can cause tmm crash

Last Modified: Jan 12, 2026

Affected Product(s):
BIG-IP LTM, SSLO(all modules)

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3

Opened: Dec 04, 2025

Severity: 3-Major

Symptoms

When a large number of virtual servers are configured on a BIG-IP and traffic is processed by SSL Orchestrator inspection service, TMM can crash if traffic hits the main virtual server before the service virtual server is loaded by TMM.

Impact

TMM crash occurs intermittently. Traffic disrupted while tmm restarts.

Conditions

- BIG-IP SSL Orchestrator deployment has deployed a large number of virtual servers and inspection services. - BIG-IP loads the entire config simultaneously or TMM is restarted when connections are being continuously sent to the BIG-IP. - Client connection hits the main SSL Orchestrator virtual server before service virtual server has finished loading the config in TMM.

Workaround

Before reloading a large SSL Orchestrator BIG-IP config or restarting TMM, mark the public virtual servers as disabled. Enable the public virtual servers individually after reload or TMM restart is successful.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips