Disable Node Monitoring

We have a major problem with Cirrus Configuration Manager V3 Enterprise DL 1000 with 980 devices (Cisco)

We are not able to work in the application when "Node Monitoring" is running !

Is there a fix ?

Or are we able to "Disable Node Monitoring" before we startup Cirrus Configuration Management ?

This is my problem, when we open the application we are not able to click on the lighting bolt, this can take up to 20 minuets or more

We had this issue and supports repsonse was turn offf node monitoring and this will stop the lag when Cirrus is started which it did but it caused another major problem with this is that if you add a new node with monitoring off that node will not be discovered and you will get an SNMP error, support are working on a fix. So to add a new node we turn on node montioring let it discover the device and then turn it off again. We don't need node montioring as we are running Orion anyway.

The other option of course if you don't have Orion or any other node monitoring product is to leave Cirrus running all the time not ideal but will solve the lag on startup.

HTH

Jon

jon, I'll agree that there is an obvious SNMP bug when "node monitoring" is enabled.
As far as the 20 minute application startup for the previous posters:

 Just wait it out, once.  I left my cirrus alone for a night, came back, and it was stable enough for me to disable node monitoring entirely.

 -JP

This brings up a good question.  What are the pros and cons of leaving monitoring on in Cirrus if you have Orion?  I have them both on the same box, should I disable node monitoring in Cirrus?

I've recently moved Cirrus onto the same box as Orion and personally can't see any point of having monitoring on Cirrus is only open when I'm using it and I will soon get an alert from Orion if I loose a switch. I don't see any pros when you also have Orion whether on the same box or not, but pros to turning it off is that ICMP traffic is cut down and thus possible congestion.

 

 

I have found that if I add devices, they are unknown unless I turn node monitoring on on the server and leave it for hours at a time so that it will go out and discover the device.  I have over 2750 devices in Cirrus presently and would add more if I thought that the server could handle it.  Once that is done i have to run a custom SQL query to rename half of my cisco devices because it does not recognize them.   Orion knows what they are but Cirrus just labels them as "Cisco" .  My Cirrus is very slow too unless the node monitoring is shut off.  If you click on anything it takes about 15 minutes to respond and the CPU is pinned at 25% and only using less than 512MB of RAM.  Is there a way to tweak Cirrus to use more horsepower on larger servers?