NPM 10.3 Topology

glummoon

Is there a way to disable this completely, or possibly make it so that it is not a default option?

Find more posts tagged with

Accepted answers

All comments

pacetti

If you are running the latest version of NPM, you can configure your topology polling interval as follows:

Click Settings in the top right corner of your web console.
Click Polling Settings in the Settings grouping.
In the Polling Statistics Intervals section, set the Default Node Topology Poll Interval as desired.
Click Submit at the bottom of the view.

HTH,

Andrew

glummoon

I have set it to 1440(24 hours), but the problem here is that it is causing

massive CPU spikes(roughly 4 minutes in duration) on certain pieces of my

gear as it polls. In short it is not useful to me and it is having a

detrimental effect on my network, so I would like to disable it completely.

epenney

We noticed same (only small % of nodes appear to be affected). I am thinking of changing our topology polling interval to 1440(24hrs) as well, so that we still get benefit of L2/L3 data gathered, but reduce the frequency of the high cpu (basically snmp denial of service) that affects certain devices. Did you notice any negative impact by setting to 24hrs, rather than default 30min. ?

GZhytar

Folks,

in NPM 10.3.1 we introduced changes in topology polling that should reduce CPU spikes on devices (basically we have short delays between sending SNMP queries that should prevent device from being slammed). I'd recommend to upgrade to 10.3.1 here.

Answering second question - there is no negative impact from setting 24 hours interval for topology collection. You'll just have your topology data updated less often.

thanks