Last Modified: Mar 12, 2019
Affected Product:
See more info
BIG-IP ASM
Known Affected Versions:
11.3.0, 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.5.3 HF2, 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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 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, 11.6.3.2, 11.6.3.3, 11.6.3.4
Fixed In:
12.0.0
Opened: Oct 06, 2013
Severity: 3-Major
When attempting to apply the security policy after changing the wildcard parameter level using the Configuration utility, you receive the error "Could not apply configuration; Set active failed". in the log /var/log/asm asm_config_server.pl|ERR|Aug 06 13:18:44.521|15771|F5::SetActive::Impl::set_active,,Setting policy active failed: Failed on insert to DCC.ACCOUNT_WILDCARD_OBJECT_PARAMETERS (DBD::mysql::db do failed: Duplicate entry '0-22-15381589614532762388-6' for key 'PRIMARY')
Could not apply the configuration; set active failed.
This occurs when attempting to apply the changes to policy from the Configuration utility by changing wildcard parameter level.
This can be fixed by policy import/export as XML. Alternatively, this can be fixed by adjusting the wildcard parameter order.
The system now correctly applies the security policy after you change the level of the wildcard parameter and click Apply Policy from the Configuration utility.