Bug ID 866613: Missing MaxMemory Attribute

Last Modified: Sep 14, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP AVR(all modules)

Known Affected Versions:
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, 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, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5

Fixed In:
16.0.0

Opened: Jan 05, 2020
Severity: 4-Minor

Symptoms

The MaxMemory Attribute is not reported in the System Monitor statistics report.

Impact

No 'MaxMemory' value label appears in System Monitor statistics. Instead, there are duplicate AvgMemory fields, for example: ...(AvgMemory='3818',AvgMemory='3818').

Conditions

This is encountered when viewing the System Monitor report.

Workaround

Use the AvgMemory value that is the higher of the two to represent MaxMemory. Note: Sometimes, the AvgMemory and MaxMemory values are the same. In that case, use the second value.

Fix Information

The MaxMemory attribute is now reported in System Monitor statistics.

Behavior Change