Last Modified: Jun 10, 2021
See more info
Known Affected Versions:
13.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.3, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.4, 220.127.116.11
Opened: Oct 04, 2017
With LTM Policy now supporting more tmm events, you may experience an error when updating an LTM Policy and see one of the following error messages: -- Policy '<name>', rule '<name>'; defines an action which occurs before one of its conditions, or before a condition in an earlier rule with lower ID. -- Policy '<name>'; an action occurs before conditions in another rule. For best-match, all actions must happen later than all conditions.
Policy cannot be saved.
You have defined a policy where at least one of the actions is set to fire at a time before the associated condition. For example, defining an action to occur at http-request time which depends on a condition that is evaluated at http-response time. For first-match policies, rules are validated in ID/ordinal order, and actions events on later rules must occur at or after condition events in the current and prior rules. For best-match policies, all actions must occur at or after than all conditions. For all-match policies, action and condition events need to be consistent with a rule, and there is no inter-rule dependence.
LTM Policy supports more LTM framework events, so policy authors need to be aware of event ordering and ensure that actions occur at or after associated conditions.