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 …
You are currently uploading a file for the [netapp_loggedin_as] account.
NB. You may switch to another user from the list (hover over the row to get the switch controller) and then use the link at the base of the page to switch back to your account.
[wordpress_file_upload …
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 …
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 …
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 …
When using the DiskPaths plugin with check_netapp_pro, it can be useful to leverage the lesser known --port_pattern_ok argument. For example, if you are receiving an error message similar to this:
The found port combination is reported to be BA, which is considered wrong because the default values for the port …
\> check\_netapp\_pro.pl DiskPaths -H $HOST wrong combination 1 nodes, 2 paths for mycluster-01 with \*\*wrong\*\* port-combination: BA (CRITICAL)
.bg-accent { background: #0459b3; } .tagline { color: white; } #htmlmap_cats { margin-left: -80%; margin-right: -30%; }