Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.6.2 HF1, 11.4.0, 11.4.1
Fixed In:
11.6.0, 11.5.1 HF5, 11.5.0 HF1, 11.4.1 HF4
Opened: Jan 09, 2014 Severity: 2-Critical Related Article:
K15731
The TMM process may segfault, or an entry similar to the following may appear in the logs: "Could not bind action 'forward select policy=... rule=... action-id=0 virtual=...', reason ERR_NOT_SUPPORTED
1. If a change is made to the targeted virtual server, the tmm process can suddenly stop working when the policy is executed. 2. If, at tmm startup, the policy targets a non-existent virtual, then policy will fail with ERR_NOT_SUPPORTED in logs.
1. Policy targets a virtual, for example: ltm policy /Common/mypolicy { controls { forwarding } requires { http } rules { ... default_policy_rule { actions { ... 1 { forward select virtual /Common/virtual2 } } } ... } ... } 2. A change is made to the virtual server (/Common/virtual2, in this case), say adding or removing a profile, or deleting it altogether.
There is no workaround at this time.
Making configuration changes, such as adding/removing a profile, to the targeted virtual will not adversely affect policy execution.