I am new to this whole network monitoring lark but have just installed zenoss 2.0.6 because I want to get a near real time (say 5 seconds latency) graphical representation of some statistics coming from a custom MIB over a network.

I have my MIB working fine, I can poll it using snmpwalk and it returns good values. I have imported my MIB into zenoss which sees all the OIDs and names just fine, I have created data types and data points in the template for one of my end nodes running the MIB daemon, I have created 5 graphs to show 5 different data types. The first two ran ok for about half and hour, then stopped. The next two have never shown any data, the last one runs fine. I queried the RRD database which shows 'nan's for all the values which don't show on the graph so I can't fault the graph itself, it appears RRD is not getting the right values. But if I query snmpwalk using an OID copy/pasted from zenoss it works fine. Why would this be going wrong for 4 out of 5 graphs?

On a maybe related note, for the first couple of days of running this, the graphs (I'm on the default CPU utilization etc graphs now) would sometimes cut out. The only way I found to start them again was run #/etc/init.d/zenoss restart . Again the RRD Database would be full of 'nan's in those blank periods. Is this likely related?

On a different note, I want to change the update rate to about 5 seconds. I changed the 'SNMP Performance Cycle Interval' value for the localhost to 5 seconds, pressed save and restarted zenoss for good measure and nothing happened. I changed all the other values on that page to 5 seconds too and, not suprisingly, nothing happened. I had a quick look at the code and, although I don't know any Python, it appears to me that it sets a variable perfsnmpCycleInterval to '5 * 60' by default so I assume it is not managing to set the variable to my value. Any ideas why not?

The best thing for you to check would be your $ZENHOME/log/ zenperfsnmp.log. This will give information on the SNMP collection cycle. You can run it in the foreground with full debugging if you want more information by running "zenperfsnmp run -v 10".

You did change the SNMP cycle time in the correct place. However, anytime you change this value you must delete all of the RRD files that were previously created. The reason for this is that the RRD files are created with specific step and heartbeat values that cannot be adjusted after creation.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to