SNMP Errors...

[tandrews]

I'm set up on a windows2003 box withh IIS, Mysql 5.0.2, Net-SNMP 5.2.1, PHP 4.3, RRDTool.

Removed the MIBDIRS environment variable.

The Cacti web interface is working, all paths are set, cmd.php is running fine. I get the following output:


03/16/2005 08:15:04 AM - SYSTEM STATS: Time: 3.1090 s, Method: cmd.php, Processes: 1, Threads: N/A, Hosts: 2, Hosts/Process: 2
03/16/2005 08:15:03 AM - CMDPHP: Poller[0] Host[0] WARNING: Result from SNMP not valid. Partial Result:
03/16/2005 08:15:03 AM - CMDPHP: Poller[0] Host[0] WARNING: Result from SNMP not valid. Partial Result:

Whenever I create a new device I get a little red "SNMP Error" under "SNMP Information" under the device name (upper left corner).

This is a Cisco router... and the data query is SNMP interface statistics. I get the following Debug info for that query:

+ Running data query [1].
+ Found type = '3' [snmp query].
+ Found data query XML file at 'c:\inetpub\wwwroot\cacti/resource/snmp_queries/interface.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.2.1.2.2.1.1'
+ No SNMP data returned
+ Found data query XML file at 'c:\inetpub\wwwroot\cacti/resource/snmp_queries/interface.xml'
+ Found data query XML file at 'c:\inetpub\wwwroot\cacti/resource/snmp_queries/interface.xml'
+ Found data query XML file at 'c:\inetpub\wwwroot\cacti/resource/snmp_queries/interface.xml'

Where would you suggest I begin to look?

[tandrews]

Debug mode output from Cacti Log:

03/16/2005 02:50:04 PM - SYSTEM STATS: Time: 3.1236 s, Method: cmd.php, Processes: 1, Threads: N/A, Hosts: 2, Hosts/Process: 2
03/16/2005 02:50:03 PM - CMDPHP: Poller[0] Time: 1.1272 s, Theads: N/A, Hosts: 1
03/16/2005 02:50:03 PM - POLLER: Poller[0] CACTI2RRD: c:\rrdtool\rrdtool.exe update c:\inetpub\wwwroot\cacti\rra\snmp_oid_13.rrd --template snmp_oid 1111006201:U
03/16/2005 02:50:03 PM - POLLER: Poller[0] CACTI2RRD: c:\rrdtool\rrdtool.exe update c:\inetpub\wwwroot\cacti\rra\5min_cpu_11.rrd --template 5min_cpu 1111006201:U
03/16/2005 02:50:03 PM - PHPSVR: Poller[0] DEBUG: PHP Script Server Shutdown request received, exiting
03/16/2005 02:50:03 PM - CMDPHP: Poller[0] Host[0] SNMP: v0: None, dsname: snmp_oid, oid: .1.3.6.1.2.1.2.2.1.10.2, output: U
03/16/2005 02:50:03 PM - CMDPHP: Poller[0] Host[0] WARNING: Result from SNMP not valid. Partial Result:
03/16/2005 02:50:03 PM - CMDPHP: Poller[0] Host[0] SNMP: v0: None, dsname: 5min_cpu, oid: .1.3.6.1.4.1.9.2.1.58.0, output: U
03/16/2005 02:50:03 PM - CMDPHP: Poller[0] Host[0] WARNING: Result from SNMP not valid. Partial Result:
03/16/2005 02:50:03 PM - CMDPHP: Poller[0] PHP Script Server Started Properly
03/16/2005 02:50:03 PM - PHPSVR: Poller[0] PHP Script Server has Started - Parent is cmd
03/16/2005 02:50:03 PM - PHPSVR: Poller[0] DEBUG: FILENM: c:\inetpub\wwwroot\cacti\script_server.php
03/16/2005 02:50:03 PM - PHPSVR: Poller[0] DEBUG: DIRNAM: c:/inetpub/wwwroot/cacti
03/16/2005 02:50:03 PM - PHPSVR: Poller[0] DEBUG: GETCWD: c:/inetpub/wwwroot/cacti
03/16/2005 02:50:03 PM - PHPSVR: Poller[0] DEBUG: SERVER: cmd
03/16/2005 02:50:01 PM - POLLER: Poller[0] DEBUG: About to Spawn a Remote Process [CMD: c:\php\php-win.exe, ARGS: -q c:\inetpub\wwwroot\cacti/cmd.php 0 10]

[mrh]

Have you checked you've installed and running the SNMP service on the monitored machines? Also you must check in the SNMP service properties, under security that exists a community (public/R.O. for example) and your cacti box is allowed to retrieve SNMP info.

You can check any host whenever you want with getif utility (free-downloadable), you can find it via google

[TheWitness]

You may not have access to the mib's. Some service providers don't want things like that shared.

TheWitness

[tandrews]

Thank you both.

This is a Cisco 2600 series router. I am currently monitoring this box with MRTG and simply wanted to take a shot with Cacti. I use Getif to retrieve OIDs for all my hardware and know the snmp community strings for everything (and have the proper string in the device setup in Cacti).

Would I be better served to simply re-try this on one of my Linux boxes? Setting up on a spare Windows2003 server just seemed to be the quick and easy route... not so anymore.