SNMP - no output

[Irulusug]

Hi!

Ive got some problems monitoring Lightspeed Enterprise. I followed the intstructions on your wiki, but dont get any output from snmpd.

My snmpd.conf looks like this:

pass .1.3.6.1.4.1.8888 /usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php

If I call /usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php manually I dont get any output. Cacti says: No Such Instance currently exists at this OID

I searched the forum and found a hint to check OIDs.

/usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php '-g' .1.3.6.1.4.1.8888.101.1 outputs:

.1.3.6.1.4.1.8888.101.1
string
LiteSpeed Web Server

But snmpwalk -c hhpv2 -v 2c 127.0.0.1 .1.3.6.1.4.1 timeouts: Timeout: No Response from 127.0.0.1

Any ideas? Thanks for your help!

Christoph

[xing]

Chris,

1) First of all. Please use OID: .1.3.6.1.4.1.22253. This OID is registered with LiteSpeed Technologies so you should not have any future conflicts.

2) Looks like you were testing with our beta release. Please check the /add-ons/ folder of 2.2+ installer for the final release of our snmpd bridge package. Re-import the templates into cacti to update them to the new official OID.

3) Check to see if any php errors were logged.

But snmpwalk -c hhpv2 -v 2c 127.0.0.1 .1.3.6.1.4.1 timeouts: Timeout: No Response from 127.0.0.1

Looks like your OID part is wrong. It should be:

snmpwalk -c hhpv2 -v 2c 127.0.0.1 .1.3.6.1.4.1.22253.101

4) If your manual test of "/usr/local/php5/bin/php /var/www/xxxx/html/cacti/scripts/litespeed.php '-g' .1.3.6.1.4.1.22253.101.1" works and outputs the product name, then there is some problem with your snmpd.conf.

[xing]

I would recommend to trace the problem going backwards.

Use a clean slate snmpd.conf as shown in the wiki:


//working sample snmpd.conf
rocommunity public
pass .1.3.6.1.4.1.22253 /usr/bin/php /litespeed_snmp_scripts/sample.php


Again, make sure you upgrade all your code/templates to our final non-beta release.

If the above snmpd.conf works, then we are sure there is something wrong with your original snmpd.conf.