port = the port you are using for the NSClientListener (defaults to 12489)•
command = is the various things you can monitor. The various commands all take different additional
arguments which are all showed in the help.
•
To check the CPU load you can for instance run the following (assuming your windows server has 10.0.0.1 as
ip address)
check_nt -H 10.0.0.1 -p 12489 -v CPULOAD -w 80 -c 90 -l 5,80,90,10,80,90
CPU Load 0% (5 min average) 0% (10 min average)
|'5 min avg Load'=0%;80;90;0;100 '10 min avg Load'=0%;80;90;0;100
If you instead got the following don't worry, it is because your NSClient++ is not configured properly and, we
will solve that in the next section.
CRITICAL - Socket timeout after 10 seconds
2. NSClient++ configuration
The first thing you need to do is decide which modules you want to use. NSClient++ is modular by design this
means you only use the features you want (and if you want you can use all of them). The modules can be
roughly divided into two kinds.
check commands1.
protocols (and utility modules).2.
The first kind is the one you *use* it responds to your commands and "finds" monitored data for you. The
second kind is the one that allows you to talk to the first kind. When it comes to modules for the NSClient
mode you will need the following:
Module Description Commands
CheckSystem.dll Handles many system checks
CPU, MEMORY, COUNTER
etc
CheckDisk.dll Handles Disk related checks USEDDISKSPACE
FileLogger.dll Logs errors to a file so you can see what is going on N/A
NSClientListener.dll
Listens and responds to incoming requests from
nagios
N/A
To enable modules you edit the [modules] section in the nsc.ini file and your section should look something
like this:
1. Nagios command line 5