Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1
Fixed In:
13.0.0, 12.1.3.2
Opened: Jan 06, 2017 Severity: 2-Critical Related Article:
K73107660
Unreliable behavior from ASM REST API. 1) REST API tasks (like apply-policy) sometimes do not execute. 2) Calls that end in error are not correctly rolled back on the system.
1) REST API tasks (like apply-policy) sometimes do not execute. 2) Calls that end in error are not correctly rolled back on the system.
A REST worker can enter this state if it processes specific calls that ended in error, such as creating a new active Policy. Note: Policies are meant to be created inactive and then activated through the apply-policy task.
1) Do not create 'active' policies. Create them with 'active': false, and then use the apply-policy task to set them active. 2) To recover a device that has reached this state, restart restjavad using the following command: bigstart restart restjavad
REST workers maintain correct state and behavior after calls with errors.