Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

What could be causing my NPM server CPU utilization demands, Memory and Disk writing after updating version?

After the update version of NPM and NTA my server started to demand the use of CPU, memory and disk write, have been submitted something.

Find more posts tagged with

upgrade

Accepted answers

All comments

rob.hock

What version did you upgrade to? A support case would probably be the best course of action: http://www.solarwinds.com/support/

aojendiz

The updated versions that were:

NPM 10.5

NTA 3.11.0

kmmorey

I have been working through this as well. My issue seems to be tied to the new multicast routing functionality. I disabled that on the nodes and it has gone away for the time being. You may want to try that.

FormerMember

I would take kmmorey's advice...disable multicast. If you have a lot of multicast enabled nodes then the easiest way is to delete all the multicast pollers directly from the database (you'll have to disable a stored procedure too). Ref Case 496889 when you call support.

Multicast is definitely not ready for prime time!

michal.hrncirik

We've fixed the problem with CPU spikes in NPM 10.6 RC so I would recommend to try this updated.

rgward has mentioned that here: http://thwack.solarwinds.com/ideas/2610 If you would like to complete disable multicast (not per node via List Resources), you can do that via SQL query: DELETE FROM Pollers WHERE PollerType LIKE '%multicast%'

I believe that you guys would like to control multicast (and other polling) globally, please vote here: http://thwack.solarwinds.com/ideas/2610

aojendiz

thanks

I commented that the issue has been solved, the solution was to increase the RAM as well as CPU cores.