On Sat, 2006-03-04 at 11:27 +0530, Ajay Hotchandani wrote:
> > What happens if you try
> > snmpwalk -v 2c -t 60 -c public localhost .1.3.6.1.6
> > ? (to give the agent more time to respond)
>
> Same output:
> "Timeout: No Response from localhost"
OK - so it's probably not simply the agent taking too
long to respond.
The next thing I'd try is
snmpgetnext -v 2c -c public -r 0 -d localhost .1.3.6.1.6
That will doubtless fail as well, but do you see the request
and a response, or just the request?
If you see the dump of a response, then the problem would
seem to lie with the client (or at least the client dropping
a possibly malformed response packet).
If you only see the outgoing dump, then the problem is
probably squarely with the agent.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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
