On 2/12/08, Dave Shield <[EMAIL PROTECTED]> wrote:
>
> On 11/02/2008, Larry Dickson <[EMAIL PROTECTED]> wrote:
> > I inserted ### before the "perl do" line in each copy of snmpd.conf that
> had
> > it.
>
> And restarted the agent, I presume?
Yes, with service snmpd restart.
> The behavior did not change, i.e. it still timed out as before.
>
> Hmmmm....
> Curiouser and curiouser....
>
> Other things to try:
>
> - snmpgetnext .... netSnmp.1.3.2.2 (the config table)
> does this work or hang?
>
> - run snmpd using "-DnsExtendTable" and repeat these queries
> what does snmpd report?
>
> - run snmpd using "-Dread_config"
> do you see anything unexpected?
>
> How was the agent configured/compiled originally?
I'll have to dig into these things later... the boss wants to focus on
failover. I'll get back to you.
> I forgot to mention, when I do a
> > getnext on netSnmp.1.8 I get an additional line that says
> >
> > Connection from <UNKNOWN>
> >
> > before it jumps to our private subtree;
>
> I don't think that is relevant.
> The problem definitely seems to be related to the nsExtend subtree.
But that still leaves my 2nd question... how does a subagent respond to a
getnext on its last leaf?
Larry Dickson
Dave
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
