Bug ID 606983: ASM errors during policy import

Last Modified: May 07, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 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, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4

Fixed In:
14.1.0, 13.1.0.8, 12.1.3.6

Opened: Jul 26, 2016
Severity: 3-Major

Symptoms

Import failure when importing ASM policy with many Session Awareness Data Points. ASM logs errors similar to the following: -- crit g_server_rpc_handler_async.pl[10933]: 01310027:2: ASM subsystem error (asm_config_server.pl,F5::ASMConfig::Handler::log_error_and_rollback): Could not update the Export Policy Task 'Export Policy Task (1469519765.114479)'. DBD::mysql::db do failed: Got a packet bigger than 'max_allowed_packet' bytes.

Impact

asm_config_server crash occurs. asm_config_server recovers automatically, within ~15-30 seconds.

Conditions

-- ASM provisioned. -- Session Awareness enabled. -- Many (more than 1000) active Session Awareness 'Block All' data points are present. -- Export a policy. -- Import the same policy.

Workaround

Either release all Session Awareness Data Points before export, or remove them from the exported policy before importing it back.

Fix Information

Import failure no longer occurs when importing ASM policy with more than 1000 Session Awareness Data Points. Now, there is a maximum of 1000 Session Awareness Data Points exported into an XML policy export.

Behavior Change