|Version 9 (modified by rpr, 2 years ago) (diff)|
This is a grooving process before it was all manual but slowly we are getting a more "automated" installation process so hopefully this will keep improving in the future as well and some of the steps might go away.
NSClient++ comes with an interactive installer (MSI) which should preferably be used. There is also a command line option for registering (and de-registering) the service -- for details refer to the manual installation guide. If you are using Windows NT4 there is some dependencies you need to install manually -- for details refer to the NT4 Dependency guide.
Details on how to do silent installs and automated silent installs can be found at the Installation Guide page.
Thus to install the Client you simply click the MSI package (for your platform) and follow the wizard through. BUT after you have installed it still needs to be configured as follows.
Before you start NSClient++ you need to configure it by editing the configuration file (NSC.ini), which is a plain text file and is explained in detail under Configuration.
The configuration file (NSC.ini) NEEDS to be configured as for security reasons all plug-ins are disabled by default. The reason for this is so no one will accidentally install this and get potential security issues. Also notice that by default allowed_hosts are 127.0.0.1 so you need to modify this as well.
3. System tray
If you plan to use the SystemTray module (that shows a System Tray icon on the Windows desktop you need to install the SystemTray module as well as NSClient++ on "old" versions of Windows (XP and earlier versions). On modern version of Windows (XP and newer) you can used the new experimental shared session support. For details on this see the System tray installation guide.
4. Testing and Debugging
After you have installed NSClient++ you need to start it. As it is a normal Windows service you can either use the "net start" and "net stop" commands in the command line or you can use the Computer Manager's Services node.
When you are starting and/or configuring your client you can use the "debug" mode which will be very helpful as you will see the debug log in "real time" when you play around with it. To start NSClient++ in test/debug mode use the following command (you can also use the icon on the start menu):
5. Windows Firewall
I have yet to figure this out but hopefully someone can help me write this! I shall for the next version try to make an automated exception thingy for the windows firewall.
6. External Firewall (optional)
Firewall configuration should be pretty straight forward:
- If you use NRPEListener (check_nrpe) you need the NRPE port open (usually 5666) from the nagios server towards the client.
- If you use the NSClientListener (check_nt) you need the (modified) NSClient port open (usually 12489) from the nagios server towards the client.
- If you use the NSCA Module (passive checks) you need the NSCA port open from the client towards the nagios server. client:* -> nagios:5667
- If you use the NRPEClient module to check any remote systems (use NSClient++ as a proxy) you need to have NRPE port (usually 5666) open from NSClient++ (the proxy) to the remote-client in addition to the method you use to submit the results to the server. nsclient-proxy:* -> remote-client:5666
|Protocol||Source||Source port||Destination||Destination port||Comment|
|NRPE||nagios||<all>||client||5666||The nagios server initiates a call to the client on port 5666|
|NSClient||nagios||<all>||client||12489||The nagios server initiates a call to the client on port 12489|
|NSCA||client||<all>||nagios||5667||The client initiates a call to the nagios server on port 5667|
|NRPE-proxy||client||<all>||remote-client||5666||The client initiates a call to the remote client on port 5666|
- nagios is the IP/host of the main nagios server
- client is the Windows computer where you have installed NSClient++
- remote-client is the "other" client you want to check from NSClient++ (using NSClient++ as a proxy)
All these ports can be changed -- check your nsc.ini.