Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0, 11.6.1 HF2, 11.5.4 HF2
Opened: Jan 25, 2016
Severity: 3-Major
In certain circumstances TMM may core if an HA pair configured with mirroring has all the routes to the server pool removed.
Traffic disrupted while tmm restarts.
- HA pair. - FastL4 VIP with mirroring. - default route to pool via an intermediate router. - The active unit is handling traffic. - Active unit fails over and loses its mirroring connection. - Prior active unit comes back and HA connection is reestablished. - During the loss of HA and its recovery the now active unit loses its only route to the pool member.
Do not remove all routes to poolmembers. If this is needed please create other backup routes prior to the deletion.
TMM no longer cores on deleting all routes on a unit with a mirroring fastL4 Virtual during HA connection loss and recovery.
