We are trying to monitor our IBM storage box using snmp, I have started the snmpd on our nagios instance and did a snmpwalk on the localhost using the below command and it works.
[root@localhost ~]# snmpwalk -v 2c -c public -O n localhost system
.1.3.6.1.2.1.1.1.0 = STRING: Linux eu2napu002 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.8072.3.2.10
.1.3.6.1.2.1.1.3.0 = Timeticks: (137502) 0:22:55.02
.1.3.6.1.2.1.1.4.0 = STRING: Root <root@localhost> (configure /etc/snmp/snmp.local.conf)
.1.3.6.1.2.1.1.5.0 = STRING: eu2napu002
.1.3.6.1.2.1.1.6.0 = STRING: Unknown (edit /etc/snmp/snmpd.conf)
.1.3.6.1.2.1.1.8.0 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.2.1 = OID: .1.3.6.1.6.3.11.2.3.1.1
.1.3.6.1.2.1.1.9.1.2.2 = OID: .1.3.6.1.6.3.15.2.1.1
.1.3.6.1.2.1.1.9.1.2.3 = OID: .1.3.6.1.6.3.10.3.1.1
.1.3.6.1.2.1.1.9.1.2.4 = OID: .1.3.6.1.6.3.1
.1.3.6.1.2.1.1.9.1.2.5 = OID: .1.3.6.1.2.1.49
.1.3.6.1.2.1.1.9.1.2.6 = OID: .1.3.6.1.2.1.4
.1.3.6.1.2.1.1.9.1.2.7 = OID: .1.3.6.1.2.1.50
.1.3.6.1.2.1.1.9.1.2.8 = OID: .1.3.6.1.6.3.16.2.2.1
.1.3.6.1.2.1.1.9.1.3.1 = STRING: The MIB for Message Processing and Dispatching.
.1.3.6.1.2.1.1.9.1.3.2 = STRING: The MIB for Message Processing and Dispatching.
.1.3.6.1.2.1.1.9.1.3.3 = STRING: The SNMP Management Architecture MIB.
.1.3.6.1.2.1.1.9.1.3.4 = STRING: The MIB module for SNMPv2 entities
.1.3.6.1.2.1.1.9.1.3.5 = STRING: The MIB module for managing TCP implementations
.1.3.6.1.2.1.1.9.1.3.6 = STRING: The MIB module for managing IP and ICMP implementations
.1.3.6.1.2.1.1.9.1.3.7 = STRING: The MIB module for managing UDP implementations
.1.3.6.1.2.1.1.9.1.3.8 = STRING: View-based Access Control Model for SNMP.
.1.3.6.1.2.1.1.9.1.4.1 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.2 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.3 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.4 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.5 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.6 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.7 = Timeticks: (9) 0:00:00.09
.1.3.6.1.2.1.1.9.1.4.8 = Timeticks: (9) 0:00:00.09
However, when we try snmpwalk for the storage device we get a message shown below. Our storage team is quiet sure that the SNMP is enabled on their box.
[root@localhost ~]# snmpwalk -v 2c -c npsvc IP
Timeout: No Response from IP
I have tested the snmpwalk to our 2nd nagios instance and I see the same error there as well. Seems to be an issue where it is not able to connect to any external devices. Could you please let me know how do I connect to the external devices using snmp and get the performance stats from the Storage box.
Because SNMP is a UDP type protocol it's difficult from the client to troubleshoot any potential network issues between you and the storage array. Do you know of any hosts that are successfully able to query the SNMP daemon on the array? If so can we get a functioning command line that works from that host.
Another potential troubleshooting method might be to query the 2nd Nagios host since it's something you have full control over. Also they may potentially be on the same network segment so we could eliminate any potential firewall issues. Can you lower port 161 UDP on the 1st Nagios server's firewall then do an snmpwalk from the 2nd server? Even if that fails it may simply be an ACL issue, but we can troubleshoot that when we reach that point.
We have already tried doing an snmp walk from the 1st nagios instance to the 2nd nagios instance (as updated in my 1st post) and even then I get the same message, i.e. Timeout: No Response from IP
Sorry if my troubleshooting steps all sound trivial, and maybe you've already done them - I'm just not quite clear.
1) Have you done an snmpwalk to localhost on 2nd box? If so does it work?
2) Can you PM your snmpd.conf of the 2nd box to me?
3) Can you post (or PM if you prefer) the output of iptables-save on the 2nd box?
In case it's not obvious I'm chasing this at the server side. I've never seen a system that prevented its snmpwalk/snmpget client from making connections so I feel like the problem is almost certainly at the server side.
Your IPTables config does not however. You will need to add a rule to IPTables to allow snmp queries from external hosts. It will NOT work without this rule:
Please add this to your IPTables on host2 then try to query from host1 again.
We cannot create a support ticket internally, we need you to e-mail [email protected] and this will generate a support ticket. Feel free to do that and we'll get you into the ticketing system. In the meantime please try to add that IPTables rule and let us know if you can run your snmp query afterwards.