Installation Steps

  1. Create the directory /usr/local/ (if it does not already exist) and untar the downloaded archive to its parent.

    mkdir -p /usr/local/
    tar -xzf check-netapp-rest-1.4.0.tar.gz --directory /usr/local/
    Explanation of the commands ...
  2. Copy the license file to its default directory

    cp CNR-00000-00000_check_netapp_pro.dat /usr/local/

    The example-configuration directory contains a license.cfg that will monitor the above directory for expiring licenses. More information about the license file and how to check for expiration can be found in the chapter License File.

  3. Create a storedir

    mkdir -p /usr/local/

    The above typescript creates the storedir at its default location. If you prefer it somewhere else you can either symlink the default-storedir to an other place or use the --storedir parameter.

    For customers who also use the Perl checks (Check NetApp-ZAPI): The checks from Check NetApp-REST have no explicit getter anymore but still use an auto-getter function to cache results locally. Therefore we still need a storedir.

  4. Change the owner of the files to the monitoring-daemons user. (In the example below, change the username from nagios to e.g. icinga or whatever your daemon runs with.)

    cd /usr/local/
    chown -R nagios netapp-rest/
  5. Copy and adapt the example configuration. At least the hosts.cfg will need your attention (tell it about the host-names which should get monitored)

    cd /usr/local/
    cp ../etc.example/* .
    vi hosts.cfg
  6. Let the monitoring system know about the location of the configuration files. E.g. on Nagios or Icinga add the following line to the main configuration file (nagios.cfg, icinga.cfg, …)

  7. Create a monitoring user on your NetApp-system (or use the existing read-only role). Write the credentials of this user into the default authfile (/usr/local/ A detailed description and typescript is in Filer Configuration

After these few steps you can reload the monitoring-servers configuration and should see some results.

Additional Notes

Compatibility with ZAPI Checks

The syntax of Check NetApp-REST is quite similar to the former (now part of Check NetApp-ZAPI) with these exceptions:

  • --authfile|-f expects the new ini-format. The older text-format is not supported any more. The minimum authfile is now:

    user = monitoring_user_name
    pass = monitoring_user_password
  • --port has been removed.

  • All underscores in the parameters have been replaced by dashes (e.g. --max_age is now written --max-age).

Using the authfile from the ZAPI Checks

Of course you can use the eventually already existing authfile from Check NetApp-ZAPI for Check NetApp-REST as well (if it is in the ini-format). Just symlink it into the above mentioned default-location or explicitly name it with the --authfile parameter. You can then administrate all NetApp hosts in one file for both of our monitoring products.