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.
As of 19th of June we released the next stable version 4.3.0 which brings a new filter for overcommitted aggregates to the Usage check and a check to monitor the NTP (time) configuration of a filer (check_netapp_time). But there is more - just check out the release-history for the details.
As always the new release can be downloaded from the Q-Portal. Customers who have already installed the RC with version number 4.
check_netapp_pro already provides a way to flag volumes which do not have snapshots at all. The check SnapshotLessVolume just looks for the size used by snapshots and if that size is equal to 0 it will raise an alarm.
Lately, while working on a check for snapmirrors, I found some attributes from which we could derive and check the snapshots policy name and the number of snapshot copies in the volume.
Releasing v4.3.0 – NetApp Monitoring Blog - Jun 5, 2019
[…] of 19th of June we released the next stable version 4.3.0 which brings a new filter for overcommitted aggregates to the Usage check and a check to monitor the NTP (time) configuration of a filer […]
An interesting option for check_netapp_pro, available with the 4.3.0 release, is the new [netapp_double_dash]aggr_over=n feature.
The Usage plugin has always checked volume and aggregate capacities. The latter being serviced in dedicated detail via the OvercommitAggr plugin. The new option added to the Usage plugin now enables a more intelligent check of the space available and to alarm on these only when the aggregates are also overcommitted. In some cases, depending on your requirements, this might even do away with the extra OvercommitAggr check altogether.
A bug has been discovered in the PerfDisk report functionality of check_netapp_pro. This error has been fixed and you should decide whether this is important enough for you to install an unstable release or simply wait for the next stable version. The bug manifests itself by reporting Multiple_Values instead of the physical disk name:
check\_netapp\_pro.pl PerfDisk -H $HOST \[netapp\_ellipsis\] Multiple\_Values (Multiple\_Values, 3004278A:071FE132:0\[netapp\_ellipsis\] \[netapp\_ellipsis\] The cause was that the newer versions of DataONTAP offer a more complete performance object _disk:constituent _while our check is using the older disk object.
Looking forward to the next release of check_netapp_pro brings several enhancements. The first one off the block, due to be released with 4.3.0, is the [netapp_double_dash]top=n parameter.
To assist with managing large slabs of information, scrolling off the top of your screen, it is now possible to retain the n top lines, where n can be any suitable integer for your purpose. The sorted results will be snipped accordingly and an ellipsis shown to indicate that you are looking at trimmed data.
The NetAppPro team is pleased to announce the latest stable release of check_netapp_pro. This release offers several new checks - some of them are still experimental and will need customer feedback for further improvement.
Experimental Checks check_netapp_unused_luns searches and flags LUNs which are mapped but whose initiators are not logged in. This check is quiet a complex one and should be used mainly in an experimental environment. It is quite possible that ‘testing in the field’ will generate useful feedback for the development team and enable us to improve it further.