Last Modified: May 29, 2024
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4
Opened: Jul 12, 2016 Severity: 3-Major
Attempting to forward traffic to a virtual server using an iRule or LTM policy will cause tmm to crash if that configuration is applied to the virtual server specified in the iRule / LTM policy. This issue can also occur when forwarding traffic through a series of virtual servers, i.e. /Common/vs_one forwards to /Common/vs_two, which forwards to /Common/vs_three, which forwards back to /Common/vs_one.
Traffic disrupted while tmm restarts.
One of the following: -- An iRule using the 'virtual' command -- An LTM policy using the 'forward' command selecting a virtual server And the iRule and/or LTM policy are applied to the virtual server specified. For instance, these are examples of configurations that would cause TMM to crash if applied to the virtual server "/Common/vs_otters" ltm rule /Common/forward_virtual { when CLIENT_ACCEPTED { virtual /Common/vs_otters } } ltm policy more-clams { controls { forwarding } [...] rules { rule-one { actions { 0 { forward select virtual /Common/vs_otter } } conditions { 0 { http-host host values { some-host } } } } [...] } }
Adjust the iRule / LTM policy configuration so that traffic does not loop.
None