jp replied on Thu, Apr 2 2009 11:18 AM

rated by 0 users

rchaill, by default, NCM will do an ICMP poll of every device listed in NCM.  I find this very inefficient out of the box.

You can either completely disable ICMP polling [This will also disable regular SNMP Discovery], or tune the ICMP polling time and increase it.

File, Options, Node Monitoring

Either turn on or off the Node moniotirong option - if it is on, you can tune the timers.

In my case I set the time between monitors to 9 hours with one icmp poll per second, with a 24-hour rediscovery.

rcahill replied on Thu, Apr 2 2009 4:20 PM

rated by 0 users

I have "tuned" the ICMP pollers from 5 minutes to near 15 minutes already.  The console still seems as though the application is still being overworked by something new.

We have had Cirrus installed for 2 years and the post-5.1 upgrade was the first time it is almost unusable.

Thanks for the response.

jp replied on Fri, Apr 3 2009 3:52 PM

rated by 0 users

For the purposes of my post here, I did turn on polling - it was previously off.  The app is horribly slow now.

I've turned polling off entirely, it's nice and speedy again.

jsokolo replied on Fri, Apr 10 2009 6:12 PM

rated by 0 users

I have also found this issue after upgrading from Cirrus 4 to NCM 5.  I have been running 230 nodes on Cirrus using a desktop PC, and set the node list showing ALL configs and it has been running for over a year, so each node in the node list displays over 365 configs, and it runs extremely fast.  I upgraded to NCM 5 on a dedicated server with a dedicated SQL server and if I have more than 5 configs displayed for each device in the node list; the node list pulsates and it is extremely difficult to get anything done in the console.  I opened a support case and they told me to reduce the number of condigs displayed in the node list.   I think there is something wrong in 5.x

kahmeelyon replied on Thu, May 28 2009 8:26 AM

rated by 0 users

I have this problem too!  Any comment from SolarWinds?  The left pane of the screen just keeps refreshing which completely locks up the app!

I just upgraded to 5.5 in the hopes that this would be fixed.  But it is not.

chris.lapoint replied on Thu, May 28 2009 11:08 AM

rated by 0 users

For those experiencing this issue, please open a support ticket with support.    To resolve this problem temporarily, you should consider disabling node monitoring (File > Settings > Node Monitoring).