Process Analysis of nagios monitoring Windows Server

NagiosThe Windows Server monitoring process is described as follows:

The biggest difference between NSClient and Nrpe is:

1. nrpe is installed on the monitored host and there are plug-ins. The final monitoring is performed by these plug-ins. When the monitoring host sends the monitoring request to nrpe, nrpe calls the plug-in to complete monitoring.

2. NSClient is different. Only NSClient is installed on the monitored machine, and no plug-in is available. after the monitoring host sends the monitoring request to NSClient, NSClient directly completes monitoring, and all monitoring tasks are completed by NSClient.

This also illustrates a major problem of NSClient, which is not flexible and not scalable. it can only perform its own monitoring operations and cannot be extended by some plug-ins. fortunately, NSClient has already done a good job, basically meeting our monitoring needs.

Client:

Download NSClient latest version in official site http://www.nsclient.org :( NSClient ++-Win32-0.3.5)

Cd nsclient ++

Nsclient ++/install

Services. msc à nsclientpp à logon. Select the check box to allow desktop and server interaction. Then click "application ".

Nsclient ++/start

Nsclient ++/stop

Edit nsclient ++/nsc. ini:

1. The comments in front of all modules in [modules] are removed except CheckWMI. dll and RemoteConfiguration. dll.

2. In the [Settings] section, set the 'Password' option to set the password, which is required when nagios is connected. We do not need a password here!

3. Remove the comment of the 'allowed _ hosts' option in the [Settings] section and add the IP address of the monitoring host. Example: allowed_hosts = 127.0.0.1, 192.168.1.0/24,222.73 .231.21/32

Separated by commas. If this field is blank, all hosts can be connected.

Note that it is in the [Settings] section, because this option is also available in the [NSClient] section.

4. The 'Port' option of [NSClient] must not be commented out and its value is '123', which is the default listening port of NSClient.

Nsclient ++/start

Netstat-an: Check whether port 12489 is listening!

Check_command check_nt! UPTIME monitoring windows server running time

Check_command check_nt! CPULOAD! -L 5, 80, 90 monitor the CPU load of Windows Servers

Check_command check_nt! MEMUSE! -W 80-c 90 monitor Windows Server Memory

Check_command check_nt! USEDDISKSPACE! -L c-w 80-c 90 monitoring Windows Server C space

Check_command check_nt! SERVICESTATE! -D SHOWALL-l telnet monitors the telnet service status

Check_command check_nt! PROCSTATE! -D SHOWALL-l assumer.exe monitors the Explorer process status

Server:

A. Copy the windows. cfg template file to 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 the host name, IP address, and alias of the Configuration)

B. Add 192.168.112.103.cfg to the main configuration file of nagios:

Vi/usr/local/nagios/etc/nagios. cfg

Export _file =/usr/local/nagios/etc/objects/192.168.112.103.cfg

C. Verify that the configuration file is correct and restart:

/Usr/local/nagios/bin/nagios-v/usr/local/nagios/etc/object/nagios. cfg (check whether the configuration file is correct)

Service nagios restart (restart nagios to make the configuration take effect)

D. Check the naigios monitoring page and find that the host has been added normally.

The process of monitoring Windows server using nagios is described above. If you do not understand anything, read Nagios 3.0's installation and configuration nagios and Nagios 3.0's instructions on how to modify Apache configuration? How does Nagios 3.0 monitor Linux servers? And teach you how to perform initial Nagios 3.0 installation and configuration. Next we will introduce ten Nagios troubleshooting techniques.