Hi!
I'm not an expert of pass_persist, but I think you only need to specify
this line:
pass_persist -p1 .1.3.6.1.4.1.2021.13.16 /opt/aac/bin/snmp_ipmi_bridge.py
It will pass all requests in the .1.3.6.1.4.1.2021.13.16 tree to the
script (snmp_ipmi_bridge.py). There is no need for the next three lines
of your config. They, and all other sub-trees in the
.1.3.6.1.4.1.2021.13.16 tree (for instance .1.3.6.1.4.1.2021.13.16.0 and
.1.3.6.1.4.1.2021.13.16.999999999 should they be queried for), will be
passed to the script. It is up to the script to handle queries for
"incorrect" OIDs and return an appropriate error:
"For GET and GETNEXT requests, PROG will be passed two lines on stdin,
the command (get or getnext) and the requested OID. It should respond by
printing three lines to stdout - the OID for the result varbind, the
TYPE and the VALUE itself - exactly as for the pass directive above./If
the command cannot return an appropriate varbind, it should print print
"NONE\n" to stdout (but continue running)./"
http://www.net-snmp.org/docs/man/snmpd.conf.html
/Fredrik
Kozikowski, Mark skrev 2014-04-23 15:23:
A little more information,
I am seeing in the logging that the 3 oids are being reported as
'duplicate registration..'
M
------------------------------------------------------------------------
*From:* Kozikowski, Mark [mkozikow...@aaccorp.com]
*Sent:* Wednesday, April 23, 2014 8:52 AM
*To:* net-snmp-users@lists.sourceforge.net
*Subject:* quesition regarding pass_persist
Hello all,
I am having a problem with my snmp configuration.
I have a python script that is invoked when the following lm_sensors oids
are called. the snmp.conf file contains:
pass_persist -p1 .1.3.6.1.4.1.2021.13.16 /opt/aac/bin/snmp_ipmi_bridge.py
pass_persist -p1 .1.3.6.1.4.1.2021.13.16.3 /opt/aac/bin/snmp_ipmi_bridge.py
pass_persist -p1 .1.3.6.1.4.1.2021.13.16.4 /opt/aac/bin/snmp_ipmi_bridge.py
pass_persist -p1 .1.3.6.1.4.1.2021.13.16.5 /opt/aac/bin/snmp_ipmi_bridge.py
The problem I am having is that no matter which iod is used in an
snmpwalk call, the response
of snmp only returns the data from ...13.16.5.
I can see from the snmp logging that an snmpget to ...13.16.3.1.3.1 is
correctly recognized,
but then is sends ...13.16.5.1.3 to my script.
I have looked at permissions, MIB files, code and all sorts of snmp
logging and debugging
output, but I cannot find what the issue is.
Help would be greatly appreciated.
Mark
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
