Bug ID 721740: CPU stats are not correctly recorded when snapshot files have timestamps in the future

Last Modified: Apr 19, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(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.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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Fixed In:
14.1.0, 13.1.1.2

Opened: May 24, 2018
Severity: 3-Major

Symptoms

One symptom is that a message similar to the following comes out in the log files frequently. May 24 16:31:53 lusia_60.F5.COM warning merged[6940]: 011b0914:4: No individual CPU information is available. Merged CPU stats will be 0.

Impact

Frequent error messages in the logs, and incorrect merged CPU stats.

Conditions

If all of the snapshot stats files have timestamps in the future, CPU stats will not be correctly merged.

Workaround

Remove all of the stats snapshot files that have timestamps in the future and restart merged.

Fix Information

Merged has been update to correctly deal with the case where all of the stats snapshot file have timestamps in the future, and will correctly merge the CPU stats.

Behavior Change