Re: fresh install - snmp timeouts

"Dave Shield" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
On 02/01/07, Siddharth Deshpande <[email protected]> wrote:
> i have configured the snmpd daemon to run as a system service
> using a startup script with the main command as:
>
> > # exec snmpd -c /usr/local/share/snmp/snmpd.conf -f -D -A
> >     -Lf /var/log/snmpd/snmpd.log <My IP>:161
>
>         Please let me know if this is correct).

The main thing that I'd suggest is wrong with that command is the '-D'
flag.   This will turn on *all* debugging, which could generate a lot of
output - most of which is probably not useful.

Also, if you've compiled the agent from source with the default settings,
then it should be looking in /usr/local/share/snmp/snmpd.conf
anyway.  So the '-c ...snmpd.conf' option is probably unnecessary
(but shouldn't do any harm).



> When i try to use the simple utilities like snmpget, snmpwalk etc., the
> only result i get is:
>
> > <command>: Timeout

Please see the FAQ entry
     Why doesn't the agent respond?
(http://www.net-snmp.org/wiki/index.php/FAQ:Applications_04)


> > udp        0      0 0.0.0.0:32771           0.0.0.0:*                                 3603/snmpd
> > udp        0      0 0.0.0.0:32772           0.0.0.0:*                                 3603/snmpd
> > udp        0      0 0.0.0.0:32773           0.0.0.0:*                                 3603/snmpd
> > udp        0      0 0.0.0.0:32774           0.0.0.0:*                                 3603/snmpd
> > udp        0      0 <MY IP>:snmp          0.0.0.0:*                           3603/snmpd

>
>         Can anybody tell me what are these other sockets associated with snmpd
> (the ones bound to 0.0.0.0)?

If you've got 'trapsink' (or similar) entries in your snmpd.conf file, then the
agent will set up an SNMP session for each of these.  That's most likely the
cause of the other sockets.

>                            And why the socket bound to the default
> snmp port (UDP 161) doesn't show an ESTABLISHED state?

Because it's not established.
It's *listening* for incoming requests, but most of the time there'll be nothing
coming in.   I wouldn't normally expect UDP-based services to be marked
as ESTABLISHED anyway - that's more of a connection-oriented (i.e. TCP)
concept.

Don't worry about it - I doubt it's relevant.
The problem is most likely one of access control.

See the FAQ for details.


Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.