The problem described by M Kulkarni would result in a noSuchName
response in v1. The timeout indicates one of four things:
1) The snmp daemon is not running.
2) The snmp daemon is running on a non-default port.
3) A firewall or operating system security feature is interfering with
communication.
4) The first object available is using more processing time than is
available within the timeout. Since the object is sysDescr, this is almost
certainly not the case.
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Pranesh Kulkarni
> Sent: Wednesday, March 26, 2008 12:36 AM
> Please check once again the config file snmpd.conf
>
> The agent isn't configured to accept commands with the
> community "public" or for "localhost"(might be you have given
> address instead of localhost")
>> On Wed, Mar 26, 2008 at 12:58 PM, komang adi
>> <[EMAIL PROTECTED]> wrote:
>>
>>
>> I have installed Net-SNMP 5.3.1 on Ubuntu 7.10. I also
>> have configure the /etc/snmp/snmpd.conf. And after restart,
>> and want to check snmp running it's shown :
>>
>> [EMAIL PROTECTED]:/usr/local# snmpwalk -v 1 -c public
>> localhost .1.3.6.1.2.1.1.1.0
>> Timeout: No Response from localhost
This is a poor choice of application ping. Doing a get-next on .1.3 is
a better choice.
HTH,
Mike
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
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
