NAGIOS monitoring Windows server process analysis

Nagios Monitoring Windows Server Processes As described below:

The difference between nsclient and nrpe *** is:

1. NRPE is installed on the monitors, and there are also plugins, and final monitoring is made by these plugins. When the monitoring host sends the monitor request to NRPE, NRPE calls the plugin to complete the monitoring.

2.NSCLIENT, only NSCLIENT is installed on the monitors, without any plugins. When the monitor hosts send the monitor request to NSCLIENT, NSClient completes the monitoring, and all the monitor is done by nsclient.

This also illustrates a big problem in NsClient, not flexible, no scalability. It can only complete the monitoring operations included in itself, can not be extended by some plugins. It is good to do it in nsclient, basically Fully meet our monitoring needs.

Client:

Download NSClient *** Version at the official site http://www.nsclient.org: (Nsclient ++ – Win32-0.3.5)

CD NSCLIENT ++

NSClient ++ / Install

Services.msc ¨¤ nsclientpp ¨¤ login ¨¤ Check the desktop and server interaction ¨¤ application ¨¤ determined

NSClient ++ / Start

NSCLIENT ++ / STOP

Edit NSClient ++ / nsc.ini:

1. All comments in front of all modules in the [Modules] are removed, except for the checkwmi.dll and remoteconfiguration.dll.

2, [settings] section Set the ‘password’ option to set the password, the function is required to provide a password when the NAGIOS is connected. Here we don’t have password!

3, [settings] section of the ‘allowed_hosts’ option is removed and the IP of the monitor host is added. Such as: allowed_hosts = 127.0.0.1, 192.168.1.0 / 24, 222.73.231.21 / 32

Sealed in a comma. If this place is blank, all hosts can be connected.

Note that the [settings] section is part of the [NSClient] section there is also this option.

4, [nsclient] ‘port’ option must be guaranteed that it is not annotated, and its value is ‘12489’, which is the default listener of NSClient.

NSClient ++ / Start

NetStat -an View port 12489 is normal to listen!

Check_command check_nt! uPtime Monitoring the time of the Windows server

Check_command check_nt! cpuload! -l 5, 80, 90 Monitor the CPU load of the Windows server

Check_command check_nt! memuse! -w 80 -c 90 Monitoring the memory of the Windows server

Check_command check_nt! useddiskspace! -l c -w 80 -c 90 monitoring Windows server C space

Check_command check_nt! serviceState! -d Showll -l Telnet Monitor the status of Telnet service

Check_command check_nt! procstate! -d showll -l explorer.exe Monitoring Explorer process status

Server:

A Copy the Windows.cfg template file, monitor 192.168.112.103:

Cp /usr/local/nagios/etc/windows.cfg /usr/local/nagios/etc/192.168.112.103.cfg

Vi 192.168.112.103.cfg

Modify configuration (host name, IP, alias)

B Join 192.168.112.103.cfg to the NAGIOS master configuration file:

vi /usr/local/nagios/etc/nagios.cfg

Cfg_file = / usr / local / nagios / etc / objects / 192.168.112.103.cfg

C Verify that the configuration file is correct and restarted:

/ usr / local / nagios / bin / nagios -v /usr/local/nagios/etc/Object/nagios.cfg (check if the configuration file is correct)

Service Nagios Restart (restart NAGIOS make the configuration take effect)

D View Naigios Monitoring page and find that the host has been added normally.

The Nagios monitoring the Windows server process is as described above. If the reader can read the Nagios 3.0 installation configuration nagios, Nagios 3.0 modifies the Apache configuration?, How does Nagios 3.0 monitor Linux servers?And teach you how to perform Nagios 3.0 initial installation configuration, the next section we will introduce ten Nagios troubleshooting skills.

Uncategorized