Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

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

Incorrect Memory and CPU utilization for F5 Big-IP

Created by Malik Haider, last modified by Michael Almadova on Oct 31, 2016

Views: 4,229 Votes: 6 Revisions: 15

Overview

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 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):

5fcpume.PNG

 

Used Poller F5 Device Poller by SolarWinds:

 

f5poller.PNG

 

Environment

NPM version 11.5 - NPM 12

 

Cause 

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

 

Resolution

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

 

f5solarpoller.PNG

 

solarmemresult.PNG

 

 

Last modified

Tags

Classifications

Public