Dave, Thanks for the advice. You're like a superhero, only with email instead of the ability to fly or x-ray vision.
I upgraded to version 5.4.1 and attempted the same test. Results are still the same. When i add the bogus entries into the snmpd.conf file, the log entries show up in /var/log/syslog. The pass entry does not show anything in the log, so I am assuming that pass is functioning as you said. ------syslog----------------------------------------------- Jun 25 09:16:19 Build-Box-T3 snmpd[11135]: NET-SNMP version 5.4.1 Jun 25 09:16:50 Build-Box-T3 snmpd[11135]: Connection from UDP: [127.0.0.1]:49444 Jun 25 09:16:50 Build-Box-T3 snmpd[11135]: Connection from UDP: [127.0.0.1]:49444 Jun 25 09:17:01 Build-Box-T3 /USR/SBIN/CRON[11147]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 25 09:18:02 Build-Box-T3 snmpd[11135]: Connection from UDP: [127.0.0.1]:47318 Jun 25 09:29:30 Build-Box-T3 snmpd[11135]: Received TERM or STOP signal... shutting down... Jun 25 09:29:33 Build-Box-T3 snmpd[11238]: /etc/snmp/snmpd.conf: line 374: Warning: Unknown token: bogus. Jun 25 09:29:33 Build-Box-T3 snmpd[11238]: /etc/snmp/snmpd.conf: line 376: Warning: Unknown token: bogus. Jun 25 09:29:33 Build-Box-T3 snmpd[11238]: NET-SNMP version 5.4.1 Jun 25 09:29:58 Build-Box-T3 snmpd[11238]: Connection from UDP: [127.0.0.1]:46027 ------------------------------------------------ Also, it seems that nothing new is logged when using the debug command. I will keep testing using the debug flags to see if I can find anything new. Thanks again, Tyler On Thu, Jun 25, 2009 at 2:26 AM, Dave Shield <[email protected]>wrote: > 2009/6/24 Tyler Smith <[email protected]>: > > I am trying to use the SNMPD pass command in version 5.1.2 > > That's a *very* old version, and is no longer supported. > You should consider upgrading to a more recent release. > > > I read that the agent must be built with support for pass. Is > > there a simple way to check if pass was built in to the agent? > > Does the agent report an error when reading the snmpd.conf file? > If it doesn't include support for "pass", then it will complain when > it gets to that particular line. > > You can check this by adding a couple of bogus entries to the > snmpd.conf file: > > > > > ---------snmpd.conf-------------------------------------------------------------------------------------- > > exec 1.3.6.1.4.1.33066.1.1 googleping /bin/ping -c 1 -w 1 -q > www.google.com > > exec 1.3.6.1.4.1.33066.1.2 serial_num_query /bin/cat /etc/snmp/serial > > exec 1.3.6.1.4.1.33066.1.3 route_table /bin/netstat -r > > exec 1.3.6.1.4.1.33066.1.4 netstat /bin/netstat > bogus before > > pass .1.3.6.1.4.1.2021.255 /bin/sh /etc/snmp/passtest > bogus after > > > -------------------------------------------------------------------------------------------------------------- > > > If you see two complaints about "bogus", but nothing about "pass", > then you can be confident that the agent supports the pass directive. > > If all three lines trigger a complaint, then it doesn't. > > And if you don't see *any* error messages, then you are looking in the > wrong place! > > It might also be worth running the agent with '-Ducd-snmp/pass' > and see what gets logged when you query the "pass" subtree. > > Dave >
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
