Bug ID 484524: tmm connflow remains after icmp unreachable message from VIP2VIP virtual

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Oct 14, 2014
Severity: 3-Major
Related AskF5 Article:
K17536

Symptoms

If a tmm connflow gets an ICMP unreachable message, the system typically terminates the connflow. However, if the connflow gets an ICMP unreachable from another virtual server through VIP2VIP, the connflow remains alive.

Impact

connflow remains until timeout. Although the active connection costs some resources, the impact is minor.

Conditions

This occurs in VIP2VIP configurations.

Workaround

None

Fix Information

if the connflow gets an ICMP unreachable from another virtual server through VIP2VIP, the connflow is now terminated, which is correct behavior.

Behavior Change