Re: No Response from localhost

On 26/03/2008, Mike Ayers <mike_ayers@tvworks.com> wrote:
>
> The problem described by M Kulkarni would result in a noSuchName
> response in v1.

Err... no. Not if the agent wasn't configured to accept the
community "public"

> 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.

5) the agent doesn't recognise the community "public"


Komang, in my experience, the three most likely causes are 1), 3) or 5)

You can check 1) via the command "ps -ef | grep snmpd"
This will show whether the SNMP agent is running or not.

3) is usually only a problem when querying the agent from a remote system.
If you are sending the query to 'localhost', then most typical
default firewall
configurations will allow this.

As long as the agent is running, I'd suspect that the most likely cause
is access control. What does your snmpd.conf look like?

It's also worth checking the system logs to see whether the snmpd agent
reports anything when it first starts up.

Dave

-------------------------------------------------------------------------
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;164216...et/marketplace
_______________________________________________
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/...net-snmp-users