Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
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, 11.5.10, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
14.0.0, 13.1.0.8, 12.1.3.2, 11.6.3.2
Opened: Jul 23, 2017 Severity: 4-Minor
Errors encountered - In TMSH CLI transaction: ---------------- transaction failed: 01020036:3: The requested ASM policy (/Common/<some_policy>) was not found. ---------------- In iApp template implementation: ---------------- script did not successfully complete: (01020036:3: The requested ASM policy (/Common/<some_policy>) was not found. ----------------
The policy is created but the modify action cannot find the policy.
In an iApp template implementation or TMSH CLI transaction, create a new ASM policy and then try to modify it's active state.
iApps are built to work with ASM Policy Templates. A new ASM Policy Template can be created from the desired ASM Policy. That can be done via GUI and starting from from v13.0 via REST as well. Then, the newly created ASM Policy Template can be referenced in the iApp template implementation or TMSH CLI transaction as follows: ----------------- tmsh::create asm policy <some_policy> active policy-template NEWLY_CREATED_POLICY_TEMPLATE -----------------
iApp template implementation and TMSH CLI transaction can now modify a newly created ASM policy.