snmpwalk

[womp]

Everytime I use snmpwalk x.x.x.x public it times out
I am on a suse box and cannot pinpoint what would be
causing this timeout issue.
Any one know?

 

[lgarner]

Offhand, it should be "snmpwalk -c public x.x.x.x".

Otherwise, make sure snmpd is running on the target, there's no firewall to interfere, and the community name and SNMP versions match.

 

[womp]

I still get the "snmpwalk: Timeout" on my command line.
These systems are all on the same subnet and I am
able to do the command successfully from one linux box but only one linux box.
We are trying to figure out what is different on the other
systems

 

[Tarwn]

Second thing to try, use the -v flag to specify an SNMP version (though if it was defaulting to 3 you usually get auth error, but it's still a good practice to get in).

Next check the configs on the box your trying to hit. It is possible it has been setup up to only accept SNMP requests from a specific IP address or range, which would explain why your first box could hit it but not your second box.

 

[womp]

where do I check for settings of snmp?

 

[lgarner]

/etc/snmp/snmpd.conf. And, the version could also be the issue. Try:

snmpwalk -v 1 -c public localhost

 

[womp]

Yes, I tried just as you have it written but I receive this:

linux:/home/hansonr # snmpwalk -v 1 -c public nagios
Timeout: No Response from nagios

Then I tried it on a totally different system and received this:

linux:/home/hansonr # snmpwalk -v 1 -c public thoosa
Timeout: No Response from thoosa

I then tried to ssh into both machines and had no problems doing so.

 

[lgarner]

Check that snmpd is running on nagios and thoosa.

See on each computer if it's listening by "netstat -ln |grep 161". Also check from linux with "nmap nagios -sU -p 161" and do the same for thoosa.

As long as you're sure "public" is the right community name, it really sounds like the daemon isn't listening or communication is being blocked. You didn't enable any firewall, did you?