Skip to main content
Version: 7.2402.x.x RR

Monitoring using SNMP

The nevisAppliance features status monitoring using the Simple Network Management Protocol (SNMP). This allows you to monitor all Nevis services remotely by any monitoring tool supporting this protocol.


The SNMP daemon can be initialized using the nevisappliance script and the command m.

Use the nevisappliance command to enable the SNMP daemon

It creates an snmpd.conf file and sets the community string for read-only access. You can adapt the file according to your requirements. The /usr/share/snmp/mibs/NEVIS-MIB.txt management information base file describes the Nevis-specific parameters that can be supervised via SNMP.

See also Monitoring ClamAV and Database monitoring for information on additional components that you can configure on your nevisAppliance.

The following section shows a small selection of these parameters:

  •<instance index>

    Alternatively, if you are using a failover cluster, the instanceProxyFOStatus attribute can be checked:<instance index>

    Indicates whether the nevisProxy instance is running (=1) or not (=0).

  •<instance index>

    Number of open user sessions.

    You should ensure that you have enough free sessions (at least 80% of the configured maximum).

  •<instance index>

    Virtual memory (in kilobytes) allocated by the working proxy process.

    During operation the memory consumption increases and an increase of several gigabytes is not uncommon. Usually, this value does not exceed its initial size by more than 2GB.

  •<instance index>

    Average request time (in seconds) of the HTTP requests.

    Can be an indication of slow application response times but sometimes you may also measure slow request times due to long-polling ajax requests or the download of huge files. This value is mainly used for statistical purposes and you don't need to configure a threshold.

  •<instance index>

    Number of TCP connections to the nevisProxy instance.

    In normal operation, this value shall not exceed 50% of the configured maximum.

  •<instance index>

    Indicates if the nevisAuth instance is running (=1) or not (=0).

  •<instance index>

    Heap usage (in kbytes) of the nevisAuth instance's virtual machine.

    The value must not exceed (80%) of the configured limitation (Xmx).

  •<instance index>

    Indicates if the nevisLogRend instance is running (=1) or not (=0).

  •<instance index>

    Indicates if the nevisIDM instance is running (=1) or not (=0).

  • instanceIdmJVMKBHeapUsage.<instance index>

    Heap usage (in kbytes) of the nevisIDM instance's virtual machine.

    The value must not exceed (80%) of the configured limitation (Xmx).

  •<instance index>

    Indicates whether the nevisCred instance is running (=1) or not (=0).


    Number of disk devices which are online (to monitor the raid controller).Value must not change (a lower value indicates a device outage).


    Available memory (in kilobytes) of the server.

    A server should always have enough free memory to handle peak-loads. A minimum of 256Mbytes is recommended.


    Free swap space (in kilobytes) of the server.

    The server must not use the whole swap space during normal operation. We expect that at least 1GB of swap space will be left unused.


    Load of the server.

    The load of a server shall not exceed the number of available CPU cores heavily.


    Free disk space (in kilobytes) of the server.

Disk space is required to write log or persistent data. Always ensure that there is enough disk space available. A minimum of 10Gbytes is recommended (free disk space can fall below this value during a nevisAppliance update due to the transfer of the new image to the server).

Parameters are accessed on a per instance basis (instance index). You should verify/monitor the instance name as well to make sure that you are monitoring the correct instance.

Extended service statistics


Additional request statistic information of the monitored nevisProxy instance (OIDs marked as "optional" within the MIB) can be collected via SNMP after activating the statistic log facility. The following CustomLog attribute (or an equivalent definition) has to be configured within the Server node of the navajo.xml of nevisProxy (example for a proxy instance with the name "default").

CustomLog=""|/opt/nevisproxy/bin/qslog -f ISBDUkEa -x -u nvpuser -o
/var/opt/nevisproxy/default/logs/stat.log" "%h %>s %b %D %{clID}e %k
%{Event}e %{dTr1B}e ""


The following example shows how you can configure Nagios to monitor your Nevis infrastructure.


The check_snmp plugin needs to be installed on your Nagios server. We recommend adding two commands using this plugin (usually within the /etc/nagios3/commands.cfg file) to verify status responses either by regular expressions or thresholds. Adapt the path "/usr/lib/nagios/plugins/" according to your environment.

Sample commands using check:snmp

define command{
command_name check_snmp_neviscmd
command_line /usr/lib/nagios/plugins/check_snmp -H $HOSTADDRESS$ -o $ARG1$ -C
$ARG2$ -t 20 -r $ARG3$
define command{
command_name check_snmp_neviscmd_threshold
command_line /usr/lib/nagios/plugins/check_snmp -H $HOSTADDRESS$ -o $ARG1$ -C
$ARG2$ -t 20 -w $ARG3$

You can now configure the OIDs to monitor within the configuration files of your Nagios server. Figure 3 shows you a sample Nagios configuration to monitor the state of a nevisProxy instance (if it is up or down). The string "public" represents the community string to authenticate the SNMP requests. Adapt it to your environment settings.

Example for checking the status of a nevisProxy instance

define service {
use generic-service
host_name myserver
service_description nevisProxy default status
check_command check_snmp_neviscmd!.!public!1

The shell script /root/tools/ can be used to:

  • read the current status information from the specified nevisAppliance over the network, and
  • generate a base configuration file that can be used by Nagios.