Monitor Windows Cluster using NagiosXI

[CoMAdmin]

In my lab environment, I am trying to monitor a Microsoft Failover Cluster with the IP 192.168.0.110. The cluster has two nodes whose IP's are 192.168.0.112 and 192.168.0.113. The cluster has a monitored service of SMTP with IP 192.168.0.111.

I am trying to use the method which involved changing NSClient configs. I followed the instructions in the following article:
https://exchange.nagios.org/components/ ... 2&cf_id=29

However, in Nagios, the service that I created is not able to connect to the cluster. I am specifying the cluster IP, as the instructions say. I tried different ports and get different responses. What port should be specified in the "command" section? The port given in the article is not listed when I run netstat on the active cluster node.

The command in Nagios is :
"Name": check_mscsMnrpe
"Comand Line": $USER1$/check_nrpe_ -H $HOSTADDRESS$ -p 139 -t 30 -c check_mscs -a "$ARG1$" "$ARG2$"

Any help or advice would be appreciated. I am willing to try a better method if someone can please guide me through it.

Thanks.

[mbellerue]

The port that should be specified in the command section will be whatever port NSClient is listening on. Check the NSClient configuration file on the Windows servers at C:\Program Files\NSClient++\nsclient.ini. There should be a port = setting, which defaults to 5666 if I recall. I would recommend against using a low port such as 139. The first roughly thousand ports are privileged ports, and often you have to do special things to get access to those ports.

If your NSClient agents are listening on 5666, then just change the -p flag in your command, and you should be good to go. It looks like you have an extra _ in the command_line definition, but that's probably just a typo here in the forum. But I thought I would call it out, just in case.

Oh also, make sure that any firewall that may be running on your Windows systems allow the NSClient port through.