We are happy to announce that the next major release of check_netapp_pro is now available on the Q-Portal for download.
The breaking changes for this release are:
A new directory layout which will ease the creation of RPM-packages. Also we have introduced a new getter for DataONTAP 9.7s new API plus several new checks. Some of these are already available as a compiled binary with zero dependencies. Several of the getters and checks now require a license-file, which you will find at the Q-Portal.
The new UnprotectedVolume check searches for volumes not protected by a SnapMirror.
An alarm is generated if one or more unprotected volumes are found. Specific volumes and vservers can be checked by using the standard check_netapp_pro --include= and --exclude= arguments. A simple example follows using the default arguments and a single host
./check\_netapp\_pro.pl UnprotectedVolume -H filer NETAPP\_PRO UNPROTECTEDVOLUME CRITICAL - 7 volumes checked, 6 critical and 0 warning mycluster-01:vol0: unprotected (CRITICAL) vserv\_a:vol0: unprotected (CRITICAL) vserv\_b:vol0: unprotected (CRITICAL) vserv\_b:vol1: unprotected (CRITICAL) vserv\_b:vol1\_mirror: unprotected (CRITICAL) vserv\_b:vol2: unprotected (CRITICAL) vserv\_a:vol1: protected (vserv\_b:vol1\_mirror, data\_protection) This check is part of the upcoming 5.
The check_netapp_quotas script returns a list of filers where quotas are in
place and where quotas are exceeded.
This script has a nifty new feature, which is available from check_netapp_pro version 5 onwards, to list quota limits per user. Enabling the --list_users switch will make the check_netapp_quotas script print a human-readable view of both soft- and hard-limits, which are overused, per user. An example will make this clearer. First, the standard check_netapp_quotas behaviour:
The new VolumeAge check for check_netapp_pro warns about overly old or exceptionally young volumes, where the age is calculated as the difference between the volume creation-time and now.
Thresholds (--warning, --critical) may be set in days (d) or week (w). Various arguments can be used to narrow down the search in more detail, see the online docs. for other options. A particularly useful feature to check for young volumes is to invert the comparison-logic with --comparison=lt (less-than).
The very useful --rm_ack=… parameter lets us decide how to deal with the posibility to remove a service acknowledgement in case of a reason-change. The optional arguments supplied until now have included ignore, always, never and reason-change, with the latter being the default. This parameter now has an additional option: off.
As one might expect, this explicitly switches the analysing of reason-changes, which is the prerequisite for deciding if a service acknowledgement should be removed or not, entirely off.
With the upcoming new v5.0.0 release comes an interesting new check for Snap Centers. The new program is check_netapp_snapcenter and is being delivered as the first of several checks which is compiled into a binary.
The check itself will query the _NetApp SnapCenter_s database directly and report any errors occurring within the last 24 hours. Thus avoiding the issue of having to wait until the backup snapshots have been created, (each 24 hour timeframe), and enabling the prompt discovery and fix of any emerging errors.