> On Tue, 2006-01-31 at 08:25 -0500, [EMAIL PROTECTED] wrote:
> > But I ran _snmpd_ with -Dsess_async_send and I think this is
> > reported by the client. Did you mean to run the client with -D?
>
> It could be either.
> It might be the agent receiving the request, but being unable
> to return a response. Or the client may be unable to send
> the request in the first place.
> Running the agent with '-d' would indicate whether it's
> receiving the request or not.
Apparently not, no output.
> (Particularly if you send a single 'snmpget' or 'snmpgetnext'
> request, rather than the repeated requests of 'snmpwalk')
>
>
> > I don't think my
> > client is smart enough to pass command-line options to SNMP
> > library initialization.
>
> If your client doesn't handle the standard command-line options,
> then try adding:
>
> debug_register_tokens("sess_async_send");
>
> to the code.
I'll do that. Thanks.
I wonder if these some endian issue with the max. messsage size? PPC
and Arm have different endianness. But surely I wouldn't be the first
to find this. And that doesn't explain that it works off-node but not on.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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
