Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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.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
Fixed In:
11.6.0
Opened: Jul 08, 2013 Severity: 3-Major Related Article:
K14968
When attempting to configure a LTM Policy with a target of 'forward', event of 'request', action of 'select', and parameters of 'clone-pool', 'node', 'member', 'nexthop', or 'rateclass', a message similar to the following is logged in /var/log/ltm: err tmm[11363]: 016e0000:3: Could not bind action 'forward select policy=/Common/policy-name rule=rule-name action-id=0 node=/Common/10.1.2.3', reason ERR_NOT_SUPPORTED'. Although the configuration appears to successfully save, traffic that matches at or below this rule in the policy, malfunctions.
Traffic matched by the policy at the affected rule, or a later rule, malfunctions.
This occurs in an LTM Policy with a target of 'forward', event of 'request', action of 'select' and parameters of 'clone-pool', 'node', 'member', 'nexthop', or 'rateclass'.
To work around forwarding to a node, configure a pool with the desired node IP address as a member, and use that pool in the policy in place of the node IP address. To work around other forwarding options, create an iRule that performs the required logic.
An LTM Policy with a target of 'forward', event of 'request', action of 'select' and parameters of 'clone-pool', 'node', 'member', 'nexthop', or 'rateclass' now function as intended.
