Bug ID 528407: TMM may core with invalid lasthop pool configuration

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.6.0, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1, 11.5.4, 11.4.1 HF10

Opened: Jun 17, 2015

Severity: 3-Major

Related Article: K72235143

Symptoms

In certain circumstances, TMM may core if the unit is configured with an invalid, non-local lasthop pool,

Impact

Traffic disrupted while tmm restarts.

Conditions

1) BIG-IP system with VIP and lasthop pool with non-local pool member. 2) Sys db tm.lhpnomemberaction set to 2.

Workaround

Configure lasthop pool to use local members/addresses.

Fix Information

TMM no longer cores with an invalid lasthop pool configuration.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips