This article is about an enhancement for the following two monitoring-plugins:


In DataONTAP Cluster Mode the specific engine for SnapVaults has been removed and therefore, there no longer is an API. Thus, SnapVaults are nothing more than SnapMirrors of the type vault. In principle, this is quite practical, since numerous features have been added to the SnapMirror checks, which can now be used for SnapVaults as well.

Maybe it would make sense to include a type based filter option. Currently, there is the option to filter by name – this can be done quite flexibly with any number of ‑‑include and ‑‑exclude switches, each of which evaluates a regular expression. Purposeful evaluation of SnapVaults, or rather SnapMirror relations of the type vault, would require a naming convention where it is possible to unambiguously deduce the type from the name. An additional filter that is independent from the name might be useful.

Relationship-type would have to be evaluated. It can be described as follows:

Specifies the type of the SnapMirror relationship. Possible values:

“data_protection” ,
“load_sharing” ,
“vault” ,
“restore” ,

A filter such as in this example would be conceivable:

  • ‑‑type=vault to check relations of the type vault only.
  • ‑‑type=data_protection ‑‑type=transition_data_protection to check relations of the type data_protection or transition_data_protection only.

We value your opinion on this subject. Please write to: developer[ a t ]

Pro Tip: In Version 3.0.13 relationship-type is already stored by cm-Getter and can be viewed with ‑‑explore:

$ ./ -H sim -o snap-mirror ‑‑explore
Existing data for object 'snap-mirror'
Instance: cluster1://hansi/snapdst (uuid n/a)
current-transfer-error = n/a
destination-cluster = cluster1
destination-location = cluster1://hansi/snapdst
is-healthy = true
lag-time = n/a
last-transfer-duration = n/a
last-transfer-error = n/a
last-transfer-size = n/a
mirror-state = snapmirrored
relationship-id = n/a
relationship-type = data_protection
source-cluster = cluster1
source-location = cluster1://hansi/snapsrc
unhealthy-reason = n/a
Explore done - now configure your nagios ...