Dave,
Thanks, I'm getting closer...
asyncapp doesn't support snmpcmd() interface but I took a close look at
snmptranslate to see what was different.
1) added debug_register_tokens("parse-mibs") and
snmp_set_do_debugging(1) to asyncapp.c, compiled and ran.
Output showed me asyncapp app was finding and loading the mibs from the
standard location.
2) pulled the command switch in toto from snmptranslate into asyncapp
in an attempt to enable the -IR functionality (which seems to cause a
call to snmp_in_toggle_options("R"). Kind of clueless where this ends
up - found a reference to the function in documentation on
mib_utilities but no description... At any rate, the -IR flag took but
didn't solve the problem so I figured the problem was in a followon
call.
3) changed asyncapp to use the (IP term here) fully qualified name,
i.e. instead of an OID name of "system.sysDescr.0" I used
"iso.org.dod.internet.mgmt.mib-2.system.sysDescr.0" (this in a call to
read_objid(). The error went away.
So I guess my question can be a little more focused now.
What sequence of configuration / command line args / function calls
enables me to enter other than a fully qualified name and get a
meaningful response back?
Rick
Dave Shield wrote:
On 01/02/07, Rick Lloyd <[EMAIL PROTECTED]> wrote:
Running asyncapp gives me:
No log handling enabled - turning on stderr logging
read_objid: Unknown Object Identifier (Sub-id not found: (top) -> system)
It looks as if this application can't find the MIB files.
Either they are not installed, or it's looking in the wrong place.
Also, running snmptranslate system yields:
No log handling enabled - turning on stderr logging
system: Unknown Object Identifier (Sub-id not found: (top) -> system)
Ignore that - snmptranslate does not do "random lookup" by default.
You need to give it a fuller OID specification....
Although, snmptranslate -IR system tells me:
SNMPv2-MIB::system
... or use the '-IR' flag explicitly!
(See http://www.net-snmp.org/wiki/index.php/TUT:snmptranslate#Specifying_a_MIB_object)
Given that snmptranslate can recognise "system", that shows that the MIB files
*are* installed on the system. So it's more likely that 'asyncapp' is
looking in
the wrong place.
I'm not sure whether this application understands the standard
command-line options.
If so, try running
asyncapp -Dparse-mibs
If not, add
debug_register_tokens("parse-mibs")
to the code, and recompile.
In either case, this should show where the command is looking for the MIB files
(and which MIB files it's trying to load).
Compare that with "snmptranslate -Dparse-mibs", and look for significant
differences.
Dave
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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
|
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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
