Bug ID 634265: Using route pools whose members aren't directly connected may crash the TMM.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2

Fixed In:
13.0.0, 12.1.3

Opened: Dec 19, 2016

Severity: 2-Critical

Related Article: K34688632

Symptoms

The TMM crashes when trying to resolve routes using route pools whose members are not directly connected.

Impact

Traffic disrupted while tmm restarts. The TMM crashes whenever a connection tries to resolve such a route.

Conditions

A configuration has route pools whose members aren't directly connected. Additionally, this is an issue only in configurations where the TMM doesn't proxy traffic but sources traffic. An example is an sFLOW configuration.

Workaround

Create route pools with directly connected members.

Fix Information

Using route pools whose members aren't directly connected no longer crashes the TMM.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips