Hi,

I have a CentOS system and I just recently installed net-snmp and net-snmp-utils.

I set up a basic snmpd.conf file with basically the community string as "public" and restarted the service.

Locally I can run snmpwalk -v 1 localhost -c public system and get a nice blast of snmp data out put.

I can do the same with snmpwalk -v 2c -c public localhost system.

Now when I try these commands from another (monitoring system), i.e. to do an snmpwalk on my centOS box, I get:

Timeout: No response from 192.0.5.142 <---my CentOS box).

I can ping from that monitoring server to my CentOS box. I can ssh. If it's a port problem then I should have been able to get snmp data even when running the command locally on the CentOS box, right?

Incidentally I can successfully get snmpwalk data from other systems on the 192.0.5.X network when I execute the command on the monitoring/management box.

Thanks for any help.

Nope; doing it locally will work, even if there is a firewall/iptables rule blocking it from the network. Since you've ruled out a config problem with SNMP on that box, can walk it locally, and have ruled out network issues with that VLAN, check the firewall/iptables rules. Since it's a new installation (you don't say what version), it may have shoved rules out there automatically at build time.

I recommend running TShark on one or both of the machines, see where your SNMP commands are going.