Bug ID 523261: ASM REST: MCP Persistence is not triggered via REST actions

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2

Opened: May 14, 2015
Severity: 3-Major

Symptoms

Some REST calls that affect Security policies should be persistent to BIG-IP config files after their completion (create, delete, association to virtual servers, and changing language encoding), but are not.

Impact

If the device is restarted configuration may be lost.

Conditions

REST API is being used to manage Security Policies.

Workaround

Any other action that will persist configuration (like an ASM config change through the GUI, or any LTM configuration change).

Fix Information

Configuration is now correctly persisted when required after ASM REST actions.

Behavior Change