Bug ID 636412: ASM start process fail with 'Protobuf message exceeds max defined size' on machines with thousands of ASM configuration entities

Last Modified: Nov 07, 2022

Affected Product(s):
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, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jan 03, 2017

Severity: 3-Major

Symptoms

ASM start process fails on machines with thousands of ASM configuration entities. The log file contains error messages similar to the following: Protobuf message exceeds max defined size. Table: CONFIG_TYPE_DYNAMIC_TABLES.

Impact

ASM may report legitimate request traffic as a violation.

Conditions

Issue is very rarely reproducible and requires thousands of ASM policy entities on the machine.

Workaround

There is no workaround at this time.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips