[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: snmpwalk to remote address gives timeout



Fabrice LORRAIN schreef:

> Bart wrote:
> > I have 2 debian boxes, one at stable, the other one at testing.
> >
> > If i run "snmpwalk -v 1 -c public localhost system" at the testing box
> > I get the results I expect:
> > SNMPv2-MIB::sysDescr.0 = STRING: Linux Box2 2.6.19.061203 #1 Sun Dec 3
> > 15:32:44 CET 2006 i686
> > SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
> > DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (493706) 1:22:17.06
> > SNMPv2-MIB::sysContact.0 = STRING: Root <root@localhost> (configure
> > /etc/snmp/snmpd.local.conf)
> > ...
> > [snip]
> >
> > However if I run "snmpwalk -v 1 -c public 192.168.1.36 system" on the
> > stable box, with 192.168.1.36 the IP address of the testing box, i get:
> > Timeout: No Response from 192.168.1.36
> >
> > snmpd is up and running, I can ping both ways, there are no firewalls
> > in place. What could be wrong?
> >
>
> Is snmpd listening on your interfaces ?
>
> Check with "sudo netstat -natup | grep 161" on the sarge box.
>
> @+,
> 	Fab
>

On Sarge I have:
netstat -natup | grep 161
udp        0      0 0.0.0.0:161             0.0.0.0:*
       707/snmpd
But Sarge is looking for snmp info on Etch. So for the fun of it, on
Etch it is:
netstat -natup | grep 161
udp        0      0 127.0.0.1:161           0.0.0.0:*
       1636/snmpd



Reply to: