Hi all,
Thanks to your help I got it talking... The new NetSNMP::agent call was
BEFORE the new NetSNMP::OID call(s) in pass.pm. When I adjusted the code to
make this true in our subagent, it started talking. There are other
problems, but they are minor in comparison...
Thanks again,
Larry
On 4/18/08, Larry Dickson <[EMAIL PROTECTED]> wrote:
>
> PROGRESS! ...
>
> There is an error in your "pass.pm" file, line 56. Instead of
>
> @inputs = ();
>
> it should have
>
> @inputs = @ARGV;
>
> because the way it is it never sees anything. After fixing that error
> everything works. Now I just have to figure out why my subagent never
> triggers the connection - even with your snmpd.conf file.
>
> Larry
>
> On 4/18/08, Larry Dickson <[EMAIL PROTECTED]> wrote:
> >
> > I'm assuming that being root means you have permissions for everything.
> > But it does not seem to work.
> >
> > I ran your snmpd.conf with the following changes: (1) replaced your
> > 10.11.0.0 with our 192.168.1.0 (2) commented out the perl do line. The
> > snmpd version is standard version 5.4.1 from the tar.gz file; the only
> > nondefault configure option was to tell it to default to V1 instead of V3. I
> > used a file /var/db/snmp/1.3.6.1.4.1.99999 with content
> >
> > 1.3.6.1.4.1.99999.1.0 string foo
> > 1.3.6.1.4.1.99999.2.0 gauge 1
> > 1.3.6.1.4.1.99999.3.0 counter 12
> >
> > (first char each line was tab) and (as root) after starting the agent,
> > ran the subagent with
> >
> > ./pass.pm /var/db/snmp
> >
> > There seem to be two levels of dysfunction, one of which pass.pm solves,
> > the other one not. I got for the first time ever a subagent response - which
> > I suppose is standard ??? -
> >
> > NET-SNMP version 5.4.1 AgentX subagent connected
> >
> > When I used the command "snmpwalk localhost 1.3.6.1.4.1.99999" as
> > suggested in the comments in pass.pm, it complained so I tried "snmpwalk
> > -c public localhost 1.3.6.1.4.1.99999" and got nothing. snmpget and
> > snmpgetnext were also unable to see 99999. Putting a period in front of the
> > 1.3.6... makes no difference.
> >
> > When I tried your snmpd.conf (with above changed) and our subagent, the
> > "subagent connected" message does not appear. This puzzles me since I think
> > our subagent calls all the setup calls yours does. I'll check.
> >
> > Larry
> >
> > On 4/18/08, Dirk-Willem van Gulik <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > On Apr 18, 2008, at 6:05 PM, Larry Dickson wrote:
> > >
> > > Thank you, Dw. I will see if it works. I notice that embedded perl and
> > > > subagent are treated as mutually exclusive, so I will strip out the
> > > > embedded
> > > > perl line from the snmpd.conf.
> > > >
> > >
> > > Yes and no - as an instance - it is mutually exclusive - but I
> > > commonly run several instances of the same script; the known/safe ones
> > > within net-snmp and then one or two odd-one's outside as a sub-agent
> > > serving
> > > an OID tree which is more ad-hoc or risky.
> > >
> > > Also, there appears to be no "pass.conf" so I will omit that. I also
> > > > notice that it talks about 5.3.1 and says /var/agentx/master was the
> > > > default; I could never get a socket in 5.4.1 until I added an explicit
> > > > agentXSocket line to snmpd.conf
> > > >
> > >
> > > I've seen that as well - and in each time (sofar) it was a simple
> > > permission problem.
> > >
> > > Dw
> > >
> >
> >
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
