This agent has the ability to function as a drop in replacement for NSClient providing the same features as NSClient combined with the ability to execute scripts on the monitored Windows server.
check_nrpe can also be used in the communication with op5 NSClient++. This one is normally used when you are performing checks on the Windows server with custom scripts.
To change the configuration open the custom.ini file using your favorite text-editor (e.g. WordPad). This file is empty and but take a look at NSC.ini to view all settings.
Read the
NSC.ini file carefully to get a complete understanding of all configuration options. Lines starting with
; (semicolon) are comments.
This option lists all servers that are allowed to talk to the agent. Enter the IP-address of the op5 Monitor/Statistics server. If this option is left blank anybody will be able to communicate with the agent.
Set debug to 1 to enable debugging. This is normally not needed but can be very useful when debugging.
This is the port used for NSClient style requests, i.e. using the check_nt plugin. If any other application is already using the default port it might be necessary to change this option.
This is the port used for nrpe style requests. In order for a minimum of configuration on the op5 Monitor server it’s recommended that this option is left with the default value. If this is changed new nrpe check commands using the configured port need to be created on the op5 Monitor server.
Set this to 1 to enable the possibility to include arguments in nrpe requests. This could be considered a security risk so only enable this if needed. Also, make sure to set the
allowed_hosts option described above if arguments are allowed.
The nrpe handlers provide a way to execute any custom plugin/check command on the monitored Windows server. In this section you configure all the commands that should be available.
MRTGEXT was originally written as an NLM for Novell Netware to obtain values used with the widely known MRTG (predecessor of cacti, which is the base of OP5 Statistics), but it can also be used to poll values from op5 Monitor.
To install this extension, simply copy the MRTGEXT.NLM to each NetWare server's SYS:SYSTEM directory that you wish to gather statistics from. Then edit the server's AUTOEXEC.NCF to “LOAD MRTGEXT” so it will load each time the server is restarted.
will change the port that MRTGEXT listens on for statistic requests. By default, MRTGEXT will use port
9999. For example, to have MRTGEXT use port
1023, add
-port=1023 to the load line. If you change the port number on the command line, be sure to modify the perl script as well.
For those with an MLA license (mostly for NetWare 5), the MRTGEXT.NLM currently can not obtain a valid value for the server license count. Using this option will tell the MRTGEXT.NLM the license count max to report. This is important if you use the NWEXTCFG.PL to create configuration files or if you use the servstat.pl script. For example, if you have a NetWare 5 MLA license and you really only have a 100 user server, then you would add
-mla=100 to your load command line.
It formats all types of Windows Eventlog entries into syslog format and sends them to a syslog host (The op5 Monitor server or the op5 LogServer). The agent can also forward plaintext log-files.
Introduction
The op5 SyslogAgent is a repackaged version of the Datagram SyslogAgent, which initially is a bug fixed version of Sabre Net's old NT_Syslog. The op5 SyslogAgent is licenced as GPL software.
The op5 SyslogAgent installation package consists of an msi installer. To install simply double click the installation msi file and follow the on-screen instructions.
After the installation is completed you will be asked if you want to start SyslogAgentConfig. If you don't do this the agent won't be configured and cannot be started. If you choose to start the