Installation

Check NetApp-SnapCenter checks the SnapCenter database for failed or missing jobs.

Installation Steps

1. Create the directory /usr/local/monitoring-plugins.pro/netapp-snapcenter/var/support (if it does not already exist) and untar the downloaded archive to it.

   mkdir -p /usr/local/monitoring-plugins.pro/netapp-snapcenter/var/support
   tar -xzf check-netapp-snapcenter-1.0.0.tar.gz --directory /usr/local/monitoring-plugins.pro/netapp-snapcenter/
   

   Why var/support ...

   The above mkdir-line creates also the var/support subdirectory beneath the checks default location. This comes in handy whenever you create a --support-file for a feature or bug-fix request. If you do not want to have this directory now, just shorten the command line to mkdir -p /usr/local/monitoring-plugins.pro/netapp-snapcenter

   Explanation of the tar command ...

   The above tar command is the short form of:

   cp check-netapp-snapcenter-1.0.0.tar.gz /usr/local/monitoring-plugins.pro/netapp-snapcenter
   cd /usr/local/monitoring-plugins.pro/netapp-snapcenter
   tar -xzf check-netapp-snapcenter-1.0.0.tar.gz
   rm check-netapp-snapcenter-1.0.0.tar.gz
   cd -
   

2. Copy the license file to its default directory. Since Check NetApp-SnapCenter is part of the Check NetAppPRO-suite it does not require a special license.

   cp CNR-00000-00000_check_netapp_pro.dat /usr/local/monitoring-plugins.pro/netapp-snapcenter/etc
   

3. 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/monitoring-plugins.pro/netapp-snapcenter
   chown -R nagios netapp-rest/
   

4. Create a monitoring user for the database server. The SnapCenter check does not get its data from the filer but from the database used by the SnapCenter application. This user should have not more than read-only rights since its credentials will be stored in plain text.

   Read more about how to create that user ...

   The MySQL Server repository database password is automatically generated during SnapCenter Server installation (for SnapCenter 4.2 - this may change in future versions). This automatically generated password is not known to SnapCenter users at any point. If you want to access the repository database, you should reset the password as described in NetApps SnapCenter documentation. Please do not forget to create a read-only user than and do not use an overprivileged user for monitoring.

5. Adapt the example configuration.

   • Write the credentials of the database-user created in the previous step into the commands-file:

     cd /usr/local/monitoring-plugins.pro/netapp-snapcenter/etc/
     vi commands.cfg
     ...
     

   • Also the hosts.cfg will need your attention (tell it about the host-names which should get monitored)

     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, …)

   cfg_dir=/usr/local/monitoring-plugins.pro/netapp-snapcenter/etc
   

Result

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

Job Type Details

As already mentioned above by default Check NetApp-SnapCenter will query Backup-jobs only. You can change that behavior with the --job-type parameter. But the exact spelling of the job-type in the database differs sometimes from its spelling in the SnapCenters GUI. You will find the database-spelling in the output of our checks together with their job-id. You must use the database-spelling for the --job-type parameter.

Example:

70125 : Backup of Resource Group ''L0001_VMWARE'' with policy ''daily7withRepl'' : 2020-12-02 04:00:14 : 2020-12-02 04:52:55 : Backup : Completed

Explanation: This line is for the job with ID 70125 and its type is Backup (which is the default).