Check NetApp-SnapCenter checks the SnapCenter database for failed or missing jobs.
Create the directory
/usr/local/monitoring-plugins.pro/netapp-snapcenter/var/support (if it does not already exist) and untar the downloaded archive to its target dir.
mkdir -p /usr/local/monitoring-plugins.pro/netapp-snapcenter/var/support tar -xzf check-netapp-snapcenter-1.1.0.tar.gz --directory /usr/local/monitoring-plugins.pro/netapp-snapcenter/
mkdir-line also creates 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
The above tar command is the short form of:
cp check-netapp-snapcenter-1.1.0.tar.gz /usr/local/monitoring-plugins.pro/netapp-snapcenter cd /usr/local/monitoring-plugins.pro/netapp-snapcenter tar -xzf check-netapp-snapcenter-1.1.0.tar.gz rm check-netapp-snapcenter-1.1.0.tar.gz cd -
Copy the license file to its default directory.
mkdir /usr/local/monitoring-plugins.pro/netapp-snapcenter/etc cp CNR-00000-00000_check_netapp_pro.dat /usr/local/monitoring-plugins.pro/netapp-snapcenter/etc
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.
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/ chown -R nagios netapp-snapcenter/
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 not have more than read-only rights since its credentials will be stored in plain text.
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 and to not use an over-privileged user for monitoring.
Adapt the example configuration.
Copy the example-files to etc/:
cd /usr/local/monitoring-plugins.pro/netapp-snapcenter/ cp etc.example/* etc/
Write the credentials of the database-user created in the previous step into the
vi etc/commands.cfg ...
hosts.cfg will need your attention (tell it about the host-names which should get monitored)
vi etc/hosts.cfg ...
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 (
After these steps you can reload the monitoring-servers configuration and should see the results.
check_netapp_snapcenter will query Backup-jobs only. So if there are no Backup-jobs you will get 0 results. You can change this job-type filter to whatever you want (search for the
--job-type parameter in the command-line help). See below for details.
--help on the commandline for the many options offered by this check.
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
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).