NetApp Monitoring on blog.monitoring-plugins.pro

Check NetApp-ZAPI will not be able to monitor next year's ONTAPI releases

Mon, 28 Nov 2022 00:00:00 +0000

NetApp’s ZAPI interface (now called ONTAPI) will reach end of availability (EOA) in January 2023. Therefore the checks from Check NetApp-ZAPI won’t be of much use in the near future. Fortunately all customers for Check NetAppPRO can use the future-proof Check NetApp-REST with the same license and therefore without additional costs.

ZAPI EOA: Timeline and Recommendations

NetApp announced that ONTAP release in FY22-Q4, will be the final ONTAP version to include ONTAPI (former called ZAPI).

RESTful volume check for NetApps ONTAP filer

Tue, 27 Jul 2021 00:00:00 +0000

The v1.2.0 release of our Check NetApp-REST product contains a new monitoring plugin called check_netapp_volume usage. It provides the monitoring of:

the used space of each volume (in Bytes)
the total used space of several volumes
the average used space of several volumes
the min/max of used space of several volumes

A typical output would look like:

$ check_netapp_volume usage -H filer -w 30GiB -c 50GiB
NETAPP VOLUME USAGE OK - 5 volumes checked
vserv_b.vol2: 1.254MiB
vserv_b.vol1: 1.23MiB
vserv_a.vol1: 1.184MiB
vserv_b.vol0: 1.27MiB
vserv_a.vol0: 1.238MiB
| 'vserv_a.vol0'=1298432B;32212254720;53687091200;0; 'vserv_b.vol0'=1331200B;32212254720;53687091200;0; 'vserv_a.vol1'=1241088B;32212254720;53687091200;0; 'vserv_b.vol1'=1290240B;32212254720;53687091200;0; 'vserv_b.vol2'=1314816B;32212254720;53687091200;0;

Reporting on groups of volumes

To get the sum of all used-space on all volumes use the aggregated subcommand:

Check NetApp's E-Series

Thu, 27 May 2021 00:00:00 +0000

The first stable release (v1.1.0) of our brand new Check E-Series product brings an automated health check for e-series nodes.

check_eseries_health will run the health checks regularly and automatically report any errors found.

Example

$ ./check_eseries_health --host=10.1.1.125 --system-id 1 [...]
NETAPP ESERIES HEALTH CRITICAL - 16 health checks checked, 1 CRITICAL
StorageGRID-XG-102.missingVolumes: notCompleted (CRITICAL)
StorageGRID-XG-102.integratedHealthCheck: ok
StorageGRID-XG-102.dbSubRecordsValidation: ok
StorageGRID-XG-102.melEventCheck: ok
StorageGRID-XG-102.validPassword: ok
StorageGRID-XG-102.failedDrivesPresent: ok
StorageGRID-XG-102.exclusiveOperations: ok
StorageGRID-XG-102.driveCheck: ok
StorageGRID-XG-102.nvsramDisableCfwDownloads: ok
StorageGRID-XG-102.hotSparesInUse: ok
StorageGRID-XG-102.controllerStatusOptimal: ok
StorageGRID-XG-102.volumeGroupsComplete: ok
StorageGRID-XG-102.objectGraphSyncCheck: ok
StorageGRID-XG-102.configurationDatabaseCheck: ok
StorageGRID-XG-102.spmDatabaseVerification: ok
StorageGRID-XG-102.storageDeviceAccessible: ok

Technical Details

Check E-Series is a monitoring-plugin for Nagios-compatible system-monitoring frameworks like Nagios-XI, Nagios-Core, Icinga, op5-monitor or Shinken. It is written in Go and distributed as a ready-to-run precompiled binary without any dependencies.

Update function and Grafana compatibility

Sat, 17 Feb 2018 18:39:52 +0000

I can recommend the unstable release 3.10.1_10 to all experimenting monitoring admins. Above all, this has the character of a technology preview. Included are two major innovations:

The update mode for all getters
The option to output Grafana compatible performance data even for status checks.

Update Mode

The update mode for the getter is quickly explained: adding the option –update and an age, the getter is instructed to check the existing store first to its age before contacting the filer. Example:``` $ ./get_netapp_cm.pl -H filer -o volume –update=3min Data for object ‘volume’ collected within 0.576s. Number of instances stored: 6

Ignore Case for -exclude

Tue, 13 Jun 2017 20:31:14 +0000

The parameter ‑‑exclude= can be used to exclude specific instances from a check. For instance, a group of volumes (provided they have a naming convention) can be excluded, e.g.: $ ./check_netapp_pro.pl Usage ‑o volume ‑‑exclude=VMWare This snippet excludes all volumes containing ‚VMWare‘ in their name (AB_VMWare_vol1, AB_VMWare_vol2, …). But the devil is in the detail: storage admins have to take great care for case-sensitive names otherwise unwanted side effects can occur: for volumes AB_VMWare_vol1 and_ AB_vmware_vol2_ the pattern above would only exclude the first volume. Using the new switch ‑‑ignore_case we no longer have this issue. $ ./check_netapp_pro.pl Usage ‑o volume ‑‑exclude=VMWare ‑‑ignore_case In this case, all possible notations of VMWare would be matched, such as:

Testing/Fixing Release 3.4.1_01

Wed, 16 Mar 2016 18:17:54 +0000

3.4.1_01 FIXES USAGE/SHELF-ENVIRONMENT, DISKCOUNT, WORKLOAD, LUNSIZE

Released 2016-03-18

Fixed

Usage-Check: Handling of volumes with no state-attribute
shelf-environment-object in cm-getter needs a node-name (sometimes)

New and improved

new DiskCount check (counts spare-disks per type or storage-pool)
new workload-object in the perf-getter (in preparation for a cdot total-ops check)
extended lun-object in the 7m/cm-getters (in preparation for a LunSize check)