Bug ID 756311: High CPU during erroneous deletion

Last Modified: Jul 03, 2019

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.4,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,,, 14.0.0,,,,,, 14.1.0,,,,,,

Fixed In:

Opened: Jan 23, 2019
Severity: 3-Major


The utilization of some CPUs in the system starts going up and remains so for a long time. Might see messages similar tot he following in tmm logs: -- notice PEM: spm_subs_id_consistency_check_cb: Session; Instance ID mismatch ERR_OK for subscriber id 310012348494 with -- notice PEM: spm_subs_id_consistency_check_cb: Session; Look up returned err ERR_OK for subscriber id 3101512411557


TMM may need to be restarted if the CPU usage does not subside. Traffic disrupted while tmm restarts.


The exact conditions under which this occurs are unknown. One potential trigger is CDP flap.


Try deleting all subscribers from the CLI.

Fix Information


Behavior Change