ADDING SNMP MONITORS

[matt.lilek]

V1 and originally i was doing this on a box on a different subnet but i have now tested a box that is on the same subnet (same host actually) as the nagiosxi server firewalls off and still the same result

[matt.lilek]

oh and the switch was on a different subnet as was the first box i was trying snmp on

[sreinhardt]

Well the subnet doesn't truly matter provided port 161 is open through any firewalls, and that the host is configured to respond to the nagios machine. So when you say you tested with a box on the same subnet, how did you do this? Have you configured the snmp service to respond to the nagios IP? Also have you tested it with nmap as before?

[matt.lilek]

Yes it is configured to respond nagios IP and it was tested with nmap and everything was fine there, i just get unknown host when i am dealing with snmp.

[sreinhardt]

OK so these are on the same vmware\hyper-v host? What commands have you run against it, and what results\output are you getting back? Just to clarify completely, nmap said open not filtered or open\filtered correct?

[matt.lilek]

I have tried on the same host different hosts it is all the same. I keep getting messages like this: "COMMAND: /usr/local/nagios/libexec/check_snmp_load.pl -H oak-fs1 -C passwd --v2c -m \^C: -w 80 -c 95 -f
OUTPUT: ERROR: Description table : No response from remote host 'oak-fs1'" depending on what performance monitors i am trying to monitor. And yes it says open filtered snmp

[sreinhardt]

It sounds like you spoke with sales, and they are going to get back in touch with you momentarily, with some good ideas. However, I did want to touch on, that the error you are getting only means one of about 3 things. Either, (1)the windows service is not configured to send back\respond to the nagios server, specifically by ip, (2) there is some form of firewall or natting in place that is not forwarding 161 to the remote device and allowing it to respond back, or (3) the remote device does not have this snmp table\mib or the community string does not have permission to access this.
Just as an idea, when I scan a device that does work with snmp it looks like this:

Code: Select all

Starting Nmap 5.51 ( http://nmap.org ) at 2013-09-04 11:43 CDT
Nmap scan report for 192.168.x.xx
Host is up (0.0047s latency).
PORT    STATE SERVICE
161/udp open  snmp

When I scan something that does not work it can look like this, or a few other states also:

Code: Select all

Starting Nmap 5.51 ( http://nmap.org ) at 2013-09-04 11:43 CDT
Nmap scan report for 192.168.x.xx
Host is up (0.0040s latency).
PORT    STATE         SERVICE
161/udp open|filtered snmp