Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Incorrect Memory and CPU utilization for F5 Big-IP in NPM

Incorrect Memory and CPU utilization for F5 Big-IP in NPM

Created by Malik Haider, last modified by Jessica Solis on Aug 15, 2018

Views: 4,778 Votes: 6 Revisions: 17

Updated August 8, 2018


This article provides brief information and a resolution to the issue when you have incorrect Memory Radial Gauge reported CPU and Memory utilization for the F5 Big IP 100%. This will be available after the upgrade to NPM 12.0 and has been removed when installing NPM 12.0 from a fresh install. The issue is with the poller and CPU and Memory should be used to poll data correctly. 


Results with F5 Poller (Incorrect CPU):



Used Poller F5 Device Poller by SolarWinds:





NPM version 11.5 - NPM 12



The issue is caused when the F5 Poller bundled with NPM 11.0 was providing incorrect information.



  • Go to Node Details page > List Resources, and then select CPU & Memory Poller by SolarWinds. 







Last modified