nsclient++ monitoring Windows hosts in Nagios

Nagios itself does not provide the corresponding monitoring, it is to implement monitoring is dependent on the SNMP protocol or the relevant plug-in to complete the corresponding monitoring, and usually in order to deploy quickly and easily, on the Linux host generally more Nrpe extension, And on the Windows host on the use of more is the nsclient++ extension, the difference is Nrpe or through the plug-in to complete the monitoring, and nsclient++ no plug-in, is the Nagios monitoring host sent monitoring request to nsclient++ to complete the monitoring task, nsclient++ can be used to meet the daily Windows host monitoring, but the disadvantage is not flexible enough. This specific can be see: http://jim123.blog.51cto.com/4763600/1922662 in the text has specific instructions, here do not do a detailed introduction. As for the installation of nsclient++ is very simple, first in nsclient++ 's official website: http://www.nsclient.org/nsclient/Download the appropriate version of the system, in the installation process is a bit more important as follows, Need to fill in the Allowed IP (Nagios monitor server IP) and password, as follows: 650) this.width=650; "Src=" https://s1.51cto.com/wyfs02/M02/9E/94/ Wkiol1mtvmabqvcwaaca2mds4uq791.png-wh_500x0-wm_3-wmp_4-s_141142161.png "title=" NSClient++ "alt=" Wkiol1mtvmabqvcwaaca2mds4uq791.png-wh_50 "/>

Here need to fill in the IP address of the monitoring server, and then configure the password, tick all the plug-ins, from here to know that nsclient++ can use Check_nrpe and check_nt two kinds of plug-ins to implement monitoring, but in general use of nsclient++ When you monitor Windows hosts, most of them use CHECK_NT, and then step by step steps to install them, so there's not much space to explain. After nsclient++ is installed and the nsclient++ service is enabled (you can use services.msc ), the default installation path is C:\Program files\nsclient++, which opens after installation nsclient++ Nsclient.ini file under the path of the installation file: 650) this.width=650; "Src=" https://s4.51cto.com/wyfs02/M00/9E/99/wKioL1mT4_ Iap0c7aagfihrngje282.png-wh_500x0-wm_3-wmp_4-s_2105673149.png "title=" Nsclient.ini "alt=" wKioL1mT4_ Iap0c7aagfihrngje282.png-wh_50 "/>

Here you can see the configured password and the allowed Nagios monitoring host IP and other related configuration parameters, in the future need to modify the configuration can change the settings here, after modification requires Nagios monitoring Server/usr/local/nagios/etc/objects/ Commands.cfg modified configuration Add on Nagios host using check_nt password and nsclient++ listening port information, default port is 12489

Define command{command_name check_nt command_line $USER 1$/check_nt-h $HOSTADDRESS $-P 12489-s S5raw Lafemy3lzqi-v $ARG 1$ $ARG 2$}

Because there were previously configured Cfg_dir under Nagios.cfg, the configuration parameters are centrally managed in the folder configuration:

Cfg_dir=/usr/local/nagios/etc/serverscfg_dir=/usr/local/nagios/etc/objects

, the windows.cfg template is available when the Nagios installation is configured, and the Windows.cfg template is modified under the previous backup to keep the following in the/usr/local/nagios/etc/objects folder:

Define hostgroup{hostgroup_name windows-servers alias Windows Servers}

Other sections with the previous configuration changed to a custom file name in the/usr/local/nagios/etc/servers directory there are several default monitors in the template that are defined by the CHECK_NT configuration, as for the use of check_nt with Check_ Nrpe almost specific can be seen: http://jim123.blog.51cto.com/4763600/1955618 in the text has relevant parameters in detail, in short use or relatively simple, in the default monitoring template will have W3SVC monitoring, It is mainly used to monitor whether the IIS service under Windows is normal if it does not need to be removed, there is an error in monitoring the Explorer process in the default template, there is no capitalization process name, where it needs to be modified so that it can be tested on the Nagios monitoring server, Monitor for the version number of the print nsclinet++ in the default template

[Email protected] libexec]#/check_nt-h 192.168.2.204-p 12489-s s5rawlafemy3lzqi-v clientversion

, you can also add the relevant services that you need to monitor, or the configuration files defined in/usr/local/nagios/etc/servers by the process configuration. One thing to note here is that the firewall on the 2008 version of Windows is the default to turn off the Ping echo protocol for ICMP If you use Nagios monitoring or ping to check the host's survival, So you also need to open the ICMP ping echo protocol in the inbound rules on the firewall on the Windows Monitoring client host, as follows: 650) this.width=650; "Src=" https://s5.51cto.com/wyfs02/M00/ 9e/9c/wkiol1mt7xmqr5amaadccn0utwk869.png-wh_500x0-wm_3-wmp_4-s_1919060924.png "title=" Windows Firewall "alt=" Wkiol1mt7xmqr5amaadccn0utwk869.png-wh_50 "/>

Turn on file and printer share echo requests so that when you use Nagios to monitor Windows ' hosts, there is no check to the host.

This article from "Technical essay" blog, declined reprint!

nsclient++ monitoring Windows hosts in Nagios