TMM Memory on F5 BigIP devices not being calculated correctly in DX NetOps Spectrum or CA Performance Management (CAPM)

Products

• CA Performance Management - Usage and Administration
• DX NetOps
• CA Spectrum

Issue/Introduction

Currently using Spectrum to monitor aggregate memory on F5s. Aggregated memory is leading to false alerts for Memory utilization.

F5s partition their memory leading Spectrum to see it as being utilized see the following articles from the vendor:

f5 article K52090030

f5 article K44014003

In either Spectrum or Performance Management, is there a way to monitor TMM memory? 

Environment

DX NetOps Release : 22.2 or later

Resolution

You should be able to correct the monitoring in Spectrum by linking the TMM OIDs to the NRM memory attributes:

sysGlobalTmmStatMemoryUsed  1.3.6.1.4.1.3375.2.1.1.2.21.29
sysGlobalTmmStatMemoryTotal 1.3.6.1.4.1.3375.2.1.1.2.21.28

And using these attribute IDs in

NRM_MemoryUsedAttr 
NRM_MemoryTotalAttr

So if you look for the device Spectrum OneClick, go to the Attributes tab and search for the above, you will see:

Replace the attributes that the NRM_MemoryUsedAttr and NRM_MemoryTotalAttr are pointing to, to the respective attributes of sysTmmStatMemoryUsed  and sysTmmStatMemoryTotal.

This should give you the memory readings you're after in Spectrum.

You should also be able to monitor TMM memory for these F5 devices in CAPM, the OIDs are in the F5BigIPTMMMemoryMib VC:

You may have to check the Vendor Certification (VC) priority order though to ensure the right VC is picked:

So probably select F5 TMM Memory as higher in the order for these devices.