Alarming failed disks on an old filer

Neither the checks nor the CLI command sysconfig -c were able to find failed disks on a Ontap 8.2.4 (7mode) system. aggr status –f reports: „Broken disks (empty)“. The only way to detect them was sysconfig -a, returning a long list, similar to the one below: … 134L84  : NETAPP   X414_HV60A15 NA03 560.0GB 520B/sect (LXY…4N) 134L85  : NETAPP   X414_HV60A15 NA03 560.0GB 520B/sect (LXY…1N) 134L86  : NETAPP   X414_HV60A15 NA03   0.0GB 0B/sect (Failed) 134L87  : NETAPP   X414_HV60A15 NA03 560.0GB 520B/sect (LXY…HN) 134L88  : NETAPP   X414_S160A15 NA08 560.0GB 520B/sect (6SL…NF) … This make for an interesting use case for check_netapp_anycli.pl. This is how these failed disks are being alarmed:``` ./check_netapp_anycli.pl -H my_old_netapp –in=sysconfig –in=-a –out=“Failed|failed” –like_result=CRITICAL –unlike_result=OK

CRITICAL - output matches pattern ‘Failed|failed’


Please note, that the syntax for check\_netapp\_anycli.pl will change with version 3.8.2 (planned release for June 2017). **The example above already uses the new syntax.**

More improvements for check_netapp_events
Ignore Case for -exclude

Comments