check_dd.pl error

[lcontreras]

Hi guys,

I really need a big help on this, my environment:

Nagios 4.2.4
CentOS Linux release 7.6.1810 (Core)

I'm trying to monitor a EMC Data Domain using check_dd.pl plugin, and I get the following error: UNKNOWN : Plugin Timed Out

I made some testing from terminal, and I get these:

[root@ensnagios01-intra-temporal]# /bin/perl ./check_datadomain.pl -H 10.200.8.21 -v DISKUSED -C NAGIOS
CRITICAL:No response from remote host "10.200.8.21" for .1.3.6.1.4.1.19746.1.3.2.1.1 with snmp version 1
[root@ensnagios01-intra-temporal]# /bin/perl ./check_datadomain.pl -H 10.200.8.21 -v DISKUSED -C NAGIOS -P 2
CRITICAL:No response from remote host "10.200.8.21" for .1.3.6.1.4.1.19746.1.3.2.1.1 with snmp version 2
[root@ensnagios01-intra-temporal]# /bin/perl ./check_datadomain.pl -H 10.200.8.21 -v DISKUSED -C NAGIOS -P 3

Any idea on how solving this situation?

[mcapra]

I am going to assume you are using this copy of the check_dd.pl plugin:
https://exchange.nagios.org/directory/P ... in/details

The error you are seeing is a general SNMP connection failure. It is not specific to this plugin -- many Perl based plugins use the Net::SNMP module.

A good first step would be to double-check that the firewall rules on 10.200.8.21 are allowing inbound connections on port 161. If you have nmap on your Nagios Core machine, this can tell you whether or not your Nagios Core machine can reach port 161 on the remote host:

Code: Select all

nmap 10.200.8.21 -p 161 -sU

You want to see "open" for the state. Not "filtered" (unless the Nagios Core machine's address is allowed explicitly/implicitly) or "closed".

[lcontreras]

Hi mcapra,

Check details below:


cpan[2]> install Term::ReadLine::Perl
Term::ReadLine::Perl is up to date (1.0303).

cpan[3]> install Net::SNMP
Net::SNMP is up to date (v6.0.1).

]# nmap 10.200.8.21 -p 161 -sU

Starting Nmap 6.40 ( http://nmap.org ) at 2019-01-04 13:48 -04
Nmap scan report for 10.200.8.21
Host is up (0.00032s latency).
PORT STATE SERVICE
161/udp open snmp

Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds

[tgriep]

Another cause for that error is that the SNMP Community string is not set correctly.
Can you verify that the Community string is set to NAGIOS?

Is it a lower case nagios for the community string and not upper case? If so change it to lower case and test it again.

[lcontreras]

To make this case very weird, I have a Nagios same version on Ubuntu Server 14.04 and the check works without any problem, important note: I didn't made that deployment of that Nagios on Ubuntu. So, in that path, I confirm that the snmp string is NAGIOS uppercase.

[scottwilkerson]

I would try running the following just to make sure you can make the SNMP requests work to that IP period

Code: Select all

snmpwalk -Os -c NAGIOS -v 2c 10.200.8.21 iso.3.6.1.2.1.1.1

[lcontreras]

I'm still getting :

[root@ensnagios01-intra-edenorte-com-do ~]# snmpwalk -Os -c NAGIOS -v 2c 10.200.8.21 iso.3.6.1.2.1.1.1
Timeout: No Response from 10.200.8.21
[root@ensnagios01-intra-edenorte-com-do ~]#

[scottwilkerson]

I'm still getting :

[root@ensnagios01-intra-edenorte-com-do ~]# snmpwalk -Os -c NAGIOS -v 2c 10.200.8.21 iso.3.6.1.2.1.1.1
Timeout: No Response from 10.200.8.21
[root@ensnagios01-intra-edenorte-com-do ~]#

Ok, so this proves that it is not the plugin that is the problem. The problem is likely that the SNMP UDP packets are being dropped somewhere on the network

[lcontreras]

Thanks Scott, I will check with security team what's going on with it.

Let's close this ticket at the end of the week, so in that I could comment what happened at the end.

[scottwilkerson]

Thanks Scott, I will check with security team what's going on with it.

Let's close this ticket at the end of the week, so in that I could comment what happened at the end.

Sounds good