Bug ID 689007: PEM CMP-HASH misconfiguration does not generate error log

Last Modified: Jun 10, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP PEM(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, 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, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1

Fixed In:
14.0.0

Opened: Oct 16, 2017
Severity: 3-Major

Symptoms

PEM requires the DAG to be configured with key as source-ip. If this configuration is not done, the iRule PEM::session fails without a warning. In the case of lookup, the command returns an empty string

Impact

The commands fail. There is no error logged in /var/log/tmm or /var/log/ltm. No warning about misconfiguration.

Conditions

-- The default tmm image (tmm.default) is running. -- The cmp-hash is not configured for SP-DAG. -- There is a query from iRule (or a session creation attempt using data-traffic).

Workaround

No workaround for tmm.default.

Fix Information

There is now an error logged in /var/log/tmm or /var/log/ltm to warn about any misconfiguration.

Behavior Change