On 02/03/07, zaman L <[EMAIL PROTECTED]> wrote:
> ./snmpd -f -Lo -x udp:127.0.0.1:161 /tmp/snmp.skt
No - that's wrong.
The -x option is used to specify an *AgentX* socket.
So the agent is now listening for AgentX connections
on the standard SNMP port, and listening for SNMP
connections on the named socket /tmp/snmp.skt
This won't work.
> But there is no SNMP agent listening after I checked it with netstat -ultnp
> tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 16670/named
> tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 16670/named
> tcp 0 0 ::1:53 :::* LISTEN 16670/named
> tcp 0 0 ::1:953 :::* LISTEN 16670/named
> udp 0 0 127.0.0.1:161 0.0.0.0:* 14434/snmpd
>
> As you can see from the last line , snmpd is not in listening mode.
That's because it's a UDP-based server, not TCP.
Though you've started it in a very strange manner (see above)
> Please somebody help me in starting the agent so that it
> responds to the snmp commands.
Try the following:
- Shut down the agent
- Run "netstat -ultmp"
Is there *anything* listed with port "161" ?
If so, then stop.
- Run "snmpd -f -Lo -c /path/to/your/snmpd.conf"
What does that display?
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
