NetApp Monitoring

Documentation

SnapMirrorMetrics-Check

Checks SnapMirror relations lag-time, transfer-duration or transfer-size.

Usage

$ check_netapp_pro.pl SnapMirrorMetrics -H <host> [--metric=lag-time|transfer-duration|transfer-size] [ ... ] [--help]

Description

This plugin checks either the lag-time, the transfer-duration or the transfer-size of each relation. Thanks to the --comparison switch both too large and suspiciously small numbers can be alarmed. See the advanced examples below.

ATTENTION: Relations without a valid value for the selected metric are silently skipped! (But you can make this visible in verbose-mode on the commandline.)

Therefore we highly recommend to additionally check with SnapMirrorState to detect such relations.

Simple Examples

[S1] ./check_netapp_pro.pl SnapMirrorMetrics -H filer

Check all relations for their lag-time using the default-thresholds

NETAPP_PRO SNAPMIRRORMETRICS CRITICAL - 2 snapmirror relations, 2 critical and 0 warning.
No SVC-ACK relevant changes in reason.
vserv1:snapdst: 136109.0s snapmirrored (CRITICAL)
vserv1:snapdest_2: 135657.0s snapmirrored (CRITICAL)
| vserv1:snapdest_2=135657s;14400;86400;0; vserv1:snapdst=136109s;14400;86400;0;
[S2] ./check_netapp_pro.pl SnapMirrorMetrics -H filer --metric=transfer-duration -w 600 -c 1200

Checks the transfer-duration instead of the lag-time.Warn if the last transfer took longer than 10 min.

NETAPP_PRO SNAPMIRRORMETRICS OK - 2 snapmirror relations checked.
vserv1:snapdest_2: 47.0s snapmirrored
vserv1:snapdst: 28.0s snapmirrored
| vserv1:snapdest_2=47s;600;1200;0; vserv1:snapdst=28s;600;1200;0;

Advanced Examples

Hint: The input for advanced examples is shortend. Replace the '...' below with ‑H <your filers ip or host-name>

[A1] ./check_netapp_pro.pl SnapMirrorMetrics ... -m transfer-size -w 1 -c 2

Checks for overly large transfer-sizes. Warns if the total number of bytes transferred as part of the last transfer exceeds 1 MiB (1024 kiB)

NETAPP_PRO SNAPMIRRORMETRICS OK - 2 snapmirror relations checked.
vserv1:snapdest_2: 0.7MiB snapmirrored
vserv1:snapdst: 0.6MiB snapmirrored
| vserv1:snapdest_2=712704B;1048576;2097152;0; vserv1:snapdst=647168B;1048576;2097152;0;
[A2] ./check_netapp_pro.pl SnapMirrorMetrics ... -m transfer-size -w 10 -c 15 --factor=Gi

Same as above but warns for more than 10 GiB (10 Giga Byte)

[A3] ./check_netapp_pro.pl SnapMirrorMetrics ... -m transfer-size -w 100 -c 20 --factor=ki --comparison=lt

Checks for suspicious small transfers. Warns if the last transfer was smaller than 100 kiB.

NETAPP_PRO SNAPMIRRORMETRICS OK - 2 snapmirror relations checked.
vserv1:snapdest_2: 696.0kiB snapmirrored
vserv1:snapdst: 632.0kiB snapmirrored
| vserv1:snapdest_2=712704B;102400;20480;0; vserv1:snapdst=647168B;102400;20480;0;

[A4] ./check_netapp_pro.pl SnapMirrorMetrics ... -m lag-time -w 15 -c 30 --factor=min

Checks the lag-time. Thresholds and output are in minutes (instead of seconds)

NETAPP_PRO SNAPMIRRORMETRICS OK - 1 snapmirror relation checked
vserv1:snapdst: 0.5min snapmirrored
| vserv1:snapdst=28s;900;1800;0;
[A5] ./check_netapp_pro.pl SnapMirrorMetrics ... -m lag-time -w 2 -c 3 --factor=d

Checks the lag-time. Thresholds and output are in days (instead of seconds)

[A6] ./check_netapp_pro.pl SnapMirrorMetrics ... -m lag-time -w 4 -c 6 --factor=w

Checks the lag-time. Thresholds and output are in weeks (instead of seconds)

[A7] ./check_netapp_pro.pl SnapMirrorMetrics ... -m lag-time -w 15 -c 30 --factor=min --uninitialized_relation_is_ok

Uninitialised snapmirrors are OK as well. Useful if you setup a far away vserver peer and activated protection with snapmirror - synchronisation can take a long time than.

© Copyright 2009-2023 Ingo Lantschner • Phone: +43-664-143 84 18 • contact@netapp-monitoring.info • en/help/SnapMirrorMetrics.html • last update: 2023-03-07