Bug ID 503951: AFM policies not synced

Last Modified: Mar 12, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP AFM(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.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

Fixed In:
11.6.3.2

Opened: Jan 30, 2015
Severity: 2-Critical

Symptoms

During configuration sync you notice that AFM policies are not enforced on one of the devices, and you see errors in /var/log/ltm: crit tmm1[25043]: 015e0001:2: pktclass: pktclass_blobs not initialized.

Impact

Policies do not sync and the sync does not recover.

Conditions

It is not known exactly what triggers this, but it is encountered during system initialization.

Workaround

None

Fix Information

None

Behavior Change