<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>blog.monitoring-plugins.pro</title>
    <link>https://blog.monitoring-plugins.pro/</link>
    <description>Recent content on blog.monitoring-plugins.pro</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.monitoring-plugins.pro/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Direct Distribution of NetApp Monitoring Plugins</title>
      <link>https://blog.monitoring-plugins.pro/posts/2025-10-02-direct-distribution/</link>
      <pubDate>Tue, 02 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/2025-10-02-direct-distribution/</guid>
      <description>&lt;p&gt;As of October 1, 2025, Activaria has taken over the distribution of the NetApp Monitoring Plugins. Previously distributed by Quorum Distribution GmbH, the plugins will now be provided directly by us as the original developer and manufacturer.&#xA;Existing contracts, including active subscriptions remain fully in effect and will be serviced by Activaria. To ensure continued delivery, the necessary customer information has been securely transferred to us.&lt;/p&gt;&#xA;&lt;p&gt;The latest software releases are always available for download at &lt;a href=&#34;https://releases.monitoring-plugins.pro/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;https://releases.monitoring-plugins.pro/&lt;/a&gt;&#xA; using your existing contract number.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Possible false negative: Broken disks have no node</title>
      <link>https://blog.monitoring-plugins.pro/posts/2025-08-02-nodeless-disk-check/</link>
      <pubDate>Sat, 02 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/2025-08-02-nodeless-disk-check/</guid>
      <description>&lt;div class=&#34;alert alert-danger&#34; role=&#34;alert&#34;&gt;&#xA;  &lt;i class=&#34;fas fa-fw fa-skull-crossbones&#34;&gt;&lt;/i&gt;The following text discusses the possibility of a false negative result, depending on your configuration. Please read it carefully.&#xA;&lt;/div&gt;&#xA;&#xA;&lt;p&gt;Recently we got an interesting bug-report: A broken disk did not get alarmed by the &lt;code&gt;check_netapp_disk container-type&lt;/code&gt;-plugin. This false negative happened because of a configuration, where disks are checked per node:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;check_netapp_disk container-type -H filer …  ‑‑include=~^NODE-B\.&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;This will check all disks on NODE-B. But a broken disk may not be related to any node and so it wont show up in the results.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Check NetApp REST v3.2.0 released</title>
      <link>https://blog.monitoring-plugins.pro/posts/2025-05-20-release-netapp-rest-v3.2.0/</link>
      <pubDate>Tue, 20 May 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/2025-05-20-release-netapp-rest-v3.2.0/</guid>
      <description>&lt;h2 id=&#34;new-check-for-disk-stats-iops-throughput-in-v320&#34;&gt;New Check for Disk Stats (iops, throughput) in v3.2.0&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;New Check: &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/latest/configuration/disk/stats&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;&lt;code&gt;check_netapp_disk stats&lt;/code&gt;&lt;/a&gt;&#xA; to monitor disk-path-quality (failed iops), throughput and other disk-metrics.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;New switch &lt;code&gt;--no-include-exclude-message&lt;/code&gt;: Do not show the message with the count of included/excluded instances.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For further details please read the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/release_history/#320-reworked-getter-and-compatibility-logic-disk-path-quality-check&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;release notes&lt;/a&gt;&#xA; and the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/v3.2.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;documentation&lt;/a&gt;&#xA;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lots of new checks in v3.1.0 (stable) and v3.2.0-beta.3</title>
      <link>https://blog.monitoring-plugins.pro/posts/2025-03-11-disk-path-quality/</link>
      <pubDate>Tue, 11 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/2025-03-11-disk-path-quality/</guid>
      <description>&lt;h2 id=&#34;new-checks-in-v310&#34;&gt;New Checks in v3.1.0&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/latest/configuration/node/service-processor&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;&lt;code&gt;check_netapp_node service-processor&lt;/code&gt;&lt;/a&gt;&#xA; has got new subcommands to check the service-processor&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;state (online/offline)&lt;/li&gt;&#xA;&lt;li&gt;last-update-state (passed/failed)&lt;/li&gt;&#xA;&lt;li&gt;is-ip-configured&lt;/li&gt;&#xA;&lt;li&gt;link-status&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The &lt;strong&gt;firmware version&lt;/strong&gt; is now printed into the message.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/latest/configuration/lun/state&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;&lt;code&gt;check_netapp_lun state&lt;/code&gt;&lt;/a&gt;&#xA;: Checks if luns are online/offline and their mapping state.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;new-check-in-v320-beta3&#34;&gt;New Check in v3.2.0-beta.3&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/latest/configuration/disk/stats&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;&lt;code&gt;check_netapp_disk stats&lt;/code&gt;&lt;/a&gt;&#xA; monitors the disk-path-quality (failed IO-operations), througput and other disk-metrics.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For further details please read the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/release_history/#320-reworked-getter-and-compatibility-logic-disk-path-quality-check&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;release notes&lt;/a&gt;&#xA; and the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/v3.2.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;documentation&lt;/a&gt;&#xA;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>v3.0.0 Released: Checks for Node-Hardware, Flexcache, Volume-State, Inodes in Aggregates and Volumes</title>
      <link>https://blog.monitoring-plugins.pro/posts/2024-07-22-hardware-flexcache-volume-state/</link>
      <pubDate>Mon, 22 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/2024-07-22-hardware-flexcache-volume-state/</guid>
      <description>&lt;p&gt;❗️Check NetApp-REST introduces a &lt;a href=&#34;https://blog.monitoring-plugins.pro/posts/2024-02-21-dynamic-regex-value/#change&#34;&gt;breaking change&lt;/a&gt;&#xA; beginning with v3.0.0.&lt;/p&gt;&#xA;&lt;h2 id=&#34;new-checks&#34;&gt;New Checks&lt;/h2&gt;&#xA;&lt;p&gt;Beside of the above mentioned UI-change we offer a lot of new checks:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Node: fan, power-supply, temperature, NVRAm battery, node state (up/down), ha state, give-back state&lt;/li&gt;&#xA;&lt;li&gt;Check for the the flexcache connection status&lt;/li&gt;&#xA;&lt;li&gt;Volume: State- and autosize checks&lt;/li&gt;&#xA;&lt;li&gt;Inode (max-files) checks for both volumes and aggregates&lt;/li&gt;&#xA;&lt;li&gt;Aggregate-state check (online, offline)&lt;/li&gt;&#xA;&lt;li&gt;LIF check (administrative-status, operational-status, is-home)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For further details please read the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/release_history/#300-new-hardware-flexcache-and-volume-state-check&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;release notes&lt;/a&gt;&#xA; and the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/v3.0.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;documentation&lt;/a&gt;&#xA;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New String &amp; Regex Values</title>
      <link>https://blog.monitoring-plugins.pro/posts/2024-02-21-dynamic-regex-value/</link>
      <pubDate>Wed, 21 Feb 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/2024-02-21-dynamic-regex-value/</guid>
      <description>&lt;p&gt;Check NetApp-REST introduces a breaking change beginning with v3.0.0.&lt;/p&gt;&#xA;&lt;h2 id=&#34;change&#34;&gt;Change&lt;/h2&gt;&#xA;&lt;p&gt;For parameters that previously expected a regular expression: Beginning with the v3.0.0 release, values which do &lt;em&gt;not&lt;/em&gt; start with a tilde (&lt;code&gt;~&lt;/code&gt;) are interpreted as &lt;strong&gt;strings&lt;/strong&gt; that must match exactly, and not as regex patterns.&lt;/p&gt;&#xA;&lt;h2 id=&#34;motivation&#34;&gt;Motivation&lt;/h2&gt;&#xA;&lt;p&gt;The new notation is more intuitive, as the former could lead to false negatives, as shown in this example:  &lt;br&gt;&#xA;The option &lt;code&gt;‑‑exclude=vol1&lt;/code&gt; also excluded &lt;em&gt;vol10&lt;/em&gt; or &lt;em&gt;vol11&lt;/em&gt; or even &lt;em&gt;somevol123&lt;/em&gt;. Now, with the new notation, it does exactly what you would expect at first glance: it only excludes &lt;em&gt;vol1&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Check NetApp-ZAPI will not be able to monitor next year&#39;s ONTAPI releases</title>
      <link>https://blog.monitoring-plugins.pro/posts/zapis-eol/</link>
      <pubDate>Mon, 28 Nov 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/zapis-eol/</guid>
      <description>&lt;p&gt;NetApp&amp;rsquo;s ZAPI interface (now called ONTAPI) will reach end of availability (EOA) in January 2023. Therefore the checks from &lt;a href=&#34;https://monitoring-plugins.pro/products/check_netapp_pro/check-netapp-zapi/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Check NetApp-ZAPI&lt;/a&gt;&#xA; won&amp;rsquo;t be of much use in the near future. Fortunately all customers for Check NetAppPRO can use the future-proof &lt;a href=&#34;https://monitoring-plugins.pro/products/check_netapp_pro/check-netapp-rest/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Check NetApp-REST&lt;/a&gt;&#xA; with the same license and therefore without additional costs.&lt;/p&gt;&#xA;&lt;h2 id=&#34;zapi-eoa-timeline-and-recommendations&#34;&gt;ZAPI EOA: Timeline and Recommendations&lt;/h2&gt;&#xA;&lt;p&gt;NetApp announced that ONTAP release in FY22-Q4, will be the final ONTAP version to include ONTAPI (former called ZAPI).&lt;/p&gt;</description>
    </item>
    <item>
      <title>RESTful Spare-Disk and -Partion Check</title>
      <link>https://blog.monitoring-plugins.pro/posts/spare-disk-spare-partition-check/</link>
      <pubDate>Thu, 27 Oct 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/spare-disk-spare-partition-check/</guid>
      <description>&lt;p&gt;The RESTful Spare-Disk Check has got subcommands for checking both spare-disks and spare-partions.&lt;/p&gt;&#xA;&lt;h3 id=&#34;example-for-checking-spare-disks&#34;&gt;Example for checking spare-disks&lt;/h3&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;./check_netapp_spare disk -H filer&#xA;NETAPP_PRO SPARE OK - 28 disks checked&#xA;...&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Checks all nodes for sufficient spare-&lt;strong&gt;disks&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h3 id=&#34;example-for-checking-spare-partitions&#34;&gt;Example for checking spare-partitions&lt;/h3&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;./check_netapp_spare partition -H filer&#xA;NETAPP SPARE WARNING - 68 partitions checked, 68 WARNING&#xA;prod-na-01.1.0.23.P3: 1 spare-disks (WARNING)&#xA;prod-na-01.1.0.23.P2: 1 spare-disks (WARNING)&#xA;prod-na-02.1.0.23.P1: 1 spare-disks (WARNING)&#xA;...&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Checks all nodes for sufficient spare-&lt;strong&gt;partitions&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;about-the-check-netapp-rest-plugins&#34;&gt;About the Check NetApp-REST plugins&lt;/h2&gt;&#xA;&lt;p&gt;The monitoring plugins &lt;code&gt;check_netapp_*&lt;/code&gt; for Nagios®-compatible monitoring frameworks like Nagios Core, Nagios XI, op5-monitor, Icinga, Shinken or Zabbix are enhanced check programs for NetApp filers.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Monitoring Check for E-Series Interfaces</title>
      <link>https://blog.monitoring-plugins.pro/posts/eseries-interface-check/</link>
      <pubDate>Mon, 21 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/eseries-interface-check/</guid>
      <description>&lt;p&gt;The &lt;strong&gt;v1.2.0&lt;/strong&gt; release of our &lt;a href=&#34;https://monitoring-plugins.pro/products/check-eseries/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Check E-Series&lt;/a&gt;&#xA; product brings a new monitoring plugin called &lt;code&gt;check_eseries_interface&lt;/code&gt; to monitor the host-interfaces.&lt;/p&gt;&#xA;&lt;p&gt;This plugin contacts the StorageGRID Management API (StorageGRID Webscale) and checks then several values for being as expected. Examples are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;channel type: &lt;em&gt;driveside&lt;/em&gt; or &lt;em&gt;hostside&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;is degraded: false or true&lt;/li&gt;&#xA;&lt;li&gt;state: &lt;em&gt;optimal&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;miswire type: should be &lt;em&gt;none&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;current interface speed: &lt;em&gt;speed16gig&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;link state: &lt;em&gt;up&lt;/em&gt; or &lt;em&gt;down&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;A typical output for the &lt;strong&gt;SAS state&lt;/strong&gt; check looks like:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Searching the blog</title>
      <link>https://blog.monitoring-plugins.pro/posts/searching-the-blog/</link>
      <pubDate>Wed, 16 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/searching-the-blog/</guid>
      <description>&lt;p&gt;Over the years, this blog has accumulated almost 300 articles. Unfortunately, the built-in JS-based search is overwhelmed by this. We have therefore switched the search bar at the top to an external search engine called MetaGer.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-metager&#34;&gt;Why MetaGer?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://metager.de/#story-ngo&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;MetaGer&lt;/a&gt;&#xA; is a search engine supported by the non-profit SUMA-EV, Association for Free Access to Knowledge. MetaGer protects against censorship by combining results from many search engines. The source code is free and open source and respects your privacy.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Check: Storage Port Status (degraded)</title>
      <link>https://blog.monitoring-plugins.pro/posts/storage-port-check/</link>
      <pubDate>Thu, 27 Jan 2022 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/storage-port-check/</guid>
      <description>&lt;p&gt;We have got this request:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Recently we have noticed that some of our fiber optic cables have degraded, this is sadly &lt;strong&gt;not&lt;/strong&gt; reported anywhere else exept with the commands below…&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;STOR04-A1::*&amp;gt; storage port show -node STOR04-A1-01&#xA; &#xA;                             Speed&#xA;Node               Port Type (Gb/s) State    Status&#xA;------------------ ---- ---- ------ -------- ---------------&#xA;STOR04-A1-01&#xA;                   0a   SAS       6 enabled  online&#xA;                   0b   SAS       0 enabled  offline&#xA;                   0c   SAS       6 enabled  online-degraded&#xA;                   0d   SAS       0 enabled  offline&#xA;                   3a   SAS       0 enabled  offline&#xA;                   3b   SAS       6 enabled  online&#xA;                   3c   SAS       0 enabled  offline&#xA;                   3d   SAS       6 enabled  online&#xA;                   6a   SAS      12 enabled  online&#xA;                   6b   SAS      12 enabled  online&#xA;                   6c   SAS      12 enabled  online&#xA;                   6d   SAS      12 enabled  online&#xA;12 entries were displayed.&#xA; &#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The cable in question is a QSFP copper to optical LC and is used because the disk shelfs are located in another server room. As you can see from the details above it is degraded, and this is most likely because of dust on the connectors.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CONTACT</title>
      <link>https://blog.monitoring-plugins.pro/contact/</link>
      <pubDate>Tue, 21 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/contact/</guid>
      <description>&lt;h2 id=&#34;how-to-buy&#34;&gt;How to buy&lt;/h2&gt;&#xA;&lt;p&gt;The monitoring plugins discussed in this blog are distributed by:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Activaria GmbH&lt;/strong&gt;  &lt;br&gt;&#xA;Marchettigasse 5/10  &lt;br&gt;&#xA;1060 Vienna, AUSTRIA  &lt;br&gt;&#xA;phone: +43 664 143 84 18  &lt;br&gt;&#xA;e-mail: &lt;a href=&#34;mailto:distribution@monitoring-plugins.pro&#34;&gt;distribution@monitoring-plugins.pro&lt;/a&gt;&#xA;&lt;/p&gt;&#xA;&lt;h2 id=&#34;website&#34;&gt;Website&lt;/h2&gt;&#xA;&lt;p&gt;For further information about the monitoring plugins for NetApp, E-Series and Websites please visit &lt;a href=&#34;https://monitoring-plugins.pro&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;monitoring-plugins.pro&lt;/a&gt;&#xA;&lt;/p&gt;&#xA;&lt;h2 id=&#34;impressum&#34;&gt;Impressum&lt;/h2&gt;&#xA;&lt;p&gt;This blog is maintained by / Für den Inhalt verantwortlich:&lt;/p&gt;&#xA;&lt;p&gt;Activaria GmbH, FN 586550 z Handelsgericht Wien  &lt;br&gt;&#xA;Ingo Lantschner  &lt;br&gt;&#xA;Marchettigasse 5/10  &lt;br&gt;&#xA;1060 Wien  &lt;br&gt;&#xA;AUSTRIA  &lt;br&gt;&#xA;E-Mail: &lt;a href=&#34;mailto:ila@monitoring-plugins.pro&#34;&gt;ila@monitoring-plugins.pro&lt;/a&gt;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;Unternehmensgegenstand: Entwicklung von System-Monitoring Plugins (Software)&lt;/p&gt;</description>
    </item>
    <item>
      <title>RESTful Volume Snapshot Check</title>
      <link>https://blog.monitoring-plugins.pro/posts/restful-snaphot-volume-check/</link>
      <pubDate>Mon, 13 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/restful-snaphot-volume-check/</guid>
      <description>&lt;p&gt;This new plugin monitors the space occupied by snapshots on a volume in its first stage of development. It is similar to its ZAPI predecessor &lt;code&gt;check_netapp_pro.pl Snapshots&lt;/code&gt; in that it can calculate the space required by snapshots either relative to the volume size or the snapshot reserve. The parameter &lt;code&gt;--base=volume|reserve&lt;/code&gt; is responsible for this.&lt;/p&gt;&#xA;&lt;h2 id=&#34;syntax-and-options&#34;&gt;Syntax and Options&lt;/h2&gt;&#xA;&lt;p&gt;With many options like &lt;code&gt;--base=volume|reserve&lt;/code&gt; or &lt;code&gt;--include/exclude=&amp;lt;regex&amp;gt;&lt;/code&gt; the check can be tailored to the needs of your organisation. Please have a look at the &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/v3.0.0/configuration/snapshot/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;checks documentation&lt;/a&gt;&#xA; page for explanations and examples.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Check for missing (accidentally deleted) volumes</title>
      <link>https://blog.monitoring-plugins.pro/posts/missing-volume-alarm/</link>
      <pubDate>Mon, 15 Nov 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/missing-volume-alarm/</guid>
      <description>&lt;p&gt;The new &lt;code&gt;check_netapp_volume missing&lt;/code&gt; plugin notifies you or your team, when a volume has been removed from the system.&lt;/p&gt;&#xA;&lt;h2 id=&#34;motivation-and-workflow&#34;&gt;Motivation and Workflow&lt;/h2&gt;&#xA;&lt;p&gt;NetApp has a “recovery queue” which is set to 12 hours by default. If the monitoring reports that a volume has been deleted, you have the chance to recover that volume.&lt;/p&gt;&#xA;&lt;p&gt;Please check out the plugin&amp;rsquo;s &lt;a href=&#34;https://docs.monitoring-plugins.pro/check-netapp-rest/v3.0.0/configuration/volume/missing/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Documentation Page&lt;/a&gt;&#xA; for more details on how to implement this check into your monitoring framework and business-processes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Check Site Simple v1.1.0 released</title>
      <link>https://blog.monitoring-plugins.pro/posts/check-site-simple-release-1.1.0/</link>
      <pubDate>Mon, 23 Aug 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/check-site-simple-release-1.1.0/</guid>
      <description>&lt;p&gt;We are pleased to announce the &lt;strong&gt;1.1.0 release&lt;/strong&gt; of our monitoring plugin &lt;code&gt;check_site_simple&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The following is new in this version:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The &lt;strong&gt;links to images&lt;/strong&gt; and other media are checked as well. This means that incorrectly embedded images or videos or those whose sources no longer exist are now recognized as well.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Links to &lt;strong&gt;external&lt;/strong&gt; sources can be provided with their own grace period. The background for the introduction of this new option is that sometimes servers to which you want to link are unstable. However, a webmaster has no direct influence on external sources. Instead of deleting the link because of occasional instability, he can now use the &lt;em&gt;grace-period&lt;/em&gt; to delay the alarm specifically for external sources only. Internal &amp;ldquo;broken links&amp;rdquo; are alerted immediately regardless of this.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RESTful volume check for NetApps ONTAP filer</title>
      <link>https://blog.monitoring-plugins.pro/posts/restful-check-netapp-volume/</link>
      <pubDate>Tue, 27 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/restful-check-netapp-volume/</guid>
      <description>&lt;p&gt;The v1.2.0 release of our &lt;a href=&#34;https://monitoring-plugins.pro/products/check_netapp_pro/check-netapp-rest/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Check NetApp-REST&lt;/a&gt;&#xA; product contains a new monitoring plugin called &lt;code&gt;check_netapp_volume usage&lt;/code&gt;. It provides the monitoring of:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the used space of each volume (in Bytes)&lt;/li&gt;&#xA;&lt;li&gt;the total used space of several volumes&lt;/li&gt;&#xA;&lt;li&gt;the average used space of several volumes&lt;/li&gt;&#xA;&lt;li&gt;the min/max of used space of several volumes&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;A typical output would look like:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ check_netapp_volume usage -H filer -w 30GiB -c 50GiB&#xA;NETAPP VOLUME USAGE OK - 5 volumes checked&#xA;vserv_b.vol2: 1.254MiB&#xA;vserv_b.vol1: 1.23MiB&#xA;vserv_a.vol1: 1.184MiB&#xA;vserv_b.vol0: 1.27MiB&#xA;vserv_a.vol0: 1.238MiB&#xA;| &amp;#39;vserv_a.vol0&amp;#39;=1298432B;32212254720;53687091200;0; &amp;#39;vserv_b.vol0&amp;#39;=1331200B;32212254720;53687091200;0; &amp;#39;vserv_a.vol1&amp;#39;=1241088B;32212254720;53687091200;0; &amp;#39;vserv_b.vol1&amp;#39;=1290240B;32212254720;53687091200;0; &amp;#39;vserv_b.vol2&amp;#39;=1314816B;32212254720;53687091200;0;&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h3 id=&#34;reporting-on-groups-of-volumes&#34;&gt;Reporting on groups of volumes&lt;/h3&gt;&#xA;&lt;p&gt;To get the &lt;strong&gt;sum of all used-space on all volumes&lt;/strong&gt; use the &lt;em&gt;aggregated&lt;/em&gt; subcommand:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Monitoring Check for E-Series Network Interfaces</title>
      <link>https://blog.monitoring-plugins.pro/posts/eseries-nic-check/</link>
      <pubDate>Mon, 26 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/eseries-nic-check/</guid>
      <description>&lt;p&gt;The v1.1.0 release of our &lt;a href=&#34;https://monitoring-plugins.pro/products/check-eseries/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Check E-Series&lt;/a&gt;&#xA; product brings also a new monitoring plugin called &lt;code&gt;check_eseries_nic&lt;/code&gt;. This provides monitoring of:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the &lt;strong&gt;link-status&lt;/strong&gt; (up/down)&lt;/li&gt;&#xA;&lt;li&gt;the &lt;strong&gt;current-speed&lt;/strong&gt; (1Gib/s, 10GiB/s, &amp;hellip;)&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;setup-error&lt;/strong&gt; (true/false)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;A typical output would for the &lt;strong&gt;link-status&lt;/strong&gt; check look like:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ ./check_eseries_nic link-status -H 10.1.1.11 --system-id=1&#xA;NETAPP ESERIES NIC CRITICAL - 4 nics checked, 3 CRITICAL&#xA;wan1.280107001000000000000: down (CRITICAL), slot 1, label P2&#xA;wan0.280007001000000000000: up, slot 0, label P1...&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Or for the &lt;strong&gt;current-speed&lt;/strong&gt; subcommand:&lt;/p&gt;</description>
    </item>
    <item>
      <title>E-Series Free Pool Space Monitoring</title>
      <link>https://blog.monitoring-plugins.pro/posts/eseries-free-pool-space/</link>
      <pubDate>Fri, 23 Jul 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/eseries-free-pool-space/</guid>
      <description>&lt;p&gt;We have released a new monitoring plugin called &lt;code&gt;check_eseries_pool&lt;/code&gt;. The first version has exactly one subcommand called &lt;code&gt;free-space&lt;/code&gt;. This monitors the free space still available for thin volumes in the disk pool.&lt;/p&gt;&#xA;&lt;p&gt;It is particularly useful when you start taking snapshots or mirroring to another system. In such cases, you will monitor the &lt;em&gt;FreePoolSpace&lt;/em&gt; to track the changes until they are mirrored to the other system or until the snapshot is deleted.&lt;/p&gt;</description>
    </item>
    <item>
      <title>EMS Log-Monitoring</title>
      <link>https://blog.monitoring-plugins.pro/posts/ems-log-monitoring/</link>
      <pubDate>Mon, 21 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/ems-log-monitoring/</guid>
      <description>&lt;h2 id=&#34;how-to-integrate-the-ems-log-into-an-existing-system-monitoring-solution&#34;&gt;How to integrate the EMS-Log into an existing System-Monitoring solution&lt;/h2&gt;&#xA;&lt;p&gt;In this article &lt;em&gt;ONTAP REST APIs: Automate Notification of High-Severity Events&lt;/em&gt; Mahalakshmi describes how to use &lt;em&gt;messages&lt;/em&gt; to get notified about system &lt;em&gt;events&lt;/em&gt;, depending on their type and severity. It&amp;rsquo;s a really flexible and comprehensive way to monitor NetApps ONTAP.&lt;/p&gt;&#xA;&lt;p&gt;What if you already have a system-monitoring solution like Nagios, Icinga, op5 Monitor or Shinken in place? In that case the destinations (the recipients of the notifications) are already defined in the monitoring system. So all you need is a monitoring-plugin which does the filtering-part.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RESTfull Disk Check for NetApp&#39;s Ontap</title>
      <link>https://blog.monitoring-plugins.pro/posts/disk-container-type-available/</link>
      <pubDate>Fri, 18 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/disk-container-type-available/</guid>
      <description>&lt;p&gt;The family of Check NetApp REST monitoring plugins has grown. With the &lt;code&gt;check_netapp_disk container-type&lt;/code&gt; plugin the storage admin has a constant eye on disks that have been moved into unwanted containers.&lt;/p&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s look at an example:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;.$ check_netapp_disk container-type -H sim96&#xA;NETAPP DISK CONTAINER TYPE OK - 28 disks checked&#xA;sim96cluster-01.NET-1.28: spare&#xA;sim96cluster-01.NET-1.27: spare&#xA;sim96cluster-01.NET-1.26: aggregate&#xA;sim96cluster-01.NET-1.25: aggregate&#xA;sim96cluster-01.NET-1.24: aggregate&#xA;sim96cluster-01.NET-1.23: aggregate&#xA;sim96cluster-01.NET-1.22: aggregate&#xA;sim96cluster-01.NET-1.21: aggregate&#xA;sim96cluster-01.NET-1.20: aggregate&#xA;sim96cluster-01.NET-1.19: spare&#xA;sim96cluster-01.NET-1.18: spare&#xA;sim96cluster-01.NET-1.17: aggregate&#xA;sim96cluster-01.NET-1.16: aggregate&#xA;sim96cluster-01.NET-1.15: aggregate&#xA;sim96cluster-01.NET-1.14: aggregate&#xA;sim96cluster-01.NET-1.13: aggregate&#xA;sim96cluster-01.NET-1.12: aggregate&#xA;sim96cluster-01.NET-1.11: aggregate&#xA;sim96cluster-01.NET-1.10: aggregate&#xA;sim96cluster-01.NET-1.9: aggregate&#xA;sim96cluster-01.NET-1.8: aggregate&#xA;sim96cluster-01.NET-1.7: aggregate&#xA;sim96cluster-01.NET-1.6: spare&#xA;sim96cluster-01.NET-1.5: spare&#xA;sim96cluster-01.NET-1.4: spare&#xA;sim96cluster-01.NET-1.3: aggregate&#xA;sim96cluster-01.NET-1.2: aggregate&#xA;sim96cluster-01.NET-1.1: aggregate&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;On this filer (it is a simulator) we have 28 disks. All disks are in either the aggregate or the spare container. Using the default switch of &lt;code&gt;--ok-type=^aggregate|spare$&lt;/code&gt; the check is OK.&lt;/p&gt;</description>
    </item>
    <item>
      <title>check_site_simple checks media-sources as well</title>
      <link>https://blog.monitoring-plugins.pro/posts/check_site_simple-checks-media-sources-as-well/</link>
      <pubDate>Tue, 01 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/check_site_simple-checks-media-sources-as-well/</guid>
      <description>&lt;p&gt;The latest release of &lt;code&gt;check_site_simple&lt;/code&gt; (v1.1.0.beta.1 as of writing this article) will find &lt;strong&gt;broken links to image and media-sources&lt;/strong&gt; as well.&lt;/p&gt;&#xA;&lt;p&gt;Like it&amp;rsquo;s predecessors the integrated crawler of &lt;code&gt;check_site_simple&lt;/code&gt; flags any broken link found somewhere on the checked site but now links to images and media files (e.g. audio or video files linked from your site) will get checked too.&lt;/p&gt;&#xA;&lt;p&gt;To give users full control we have also integrated a  new switch &lt;code&gt;--disable-media-checks&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Check NetApp&#39;s E-Series</title>
      <link>https://blog.monitoring-plugins.pro/posts/check_eseries-released/</link>
      <pubDate>Thu, 27 May 2021 00:00:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/check_eseries-released/</guid>
      <description>&lt;p&gt;The first stable release (v1.1.0) of our brand new &lt;strong&gt;Check E-Series&lt;/strong&gt; product brings an automated health check for e-series nodes.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;check_eseries_health&lt;/code&gt; will run the health checks regularly and automatically report any errors found.&lt;/p&gt;&#xA;&lt;h2 id=&#34;example&#34;&gt;Example&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ ./check_eseries_health --host=10.1.1.125 --system-id 1 [...]&#xA;NETAPP ESERIES HEALTH CRITICAL - 16 health checks checked, 1 CRITICAL&#xA;StorageGRID-XG-102.missingVolumes: notCompleted (CRITICAL)&#xA;StorageGRID-XG-102.integratedHealthCheck: ok&#xA;StorageGRID-XG-102.dbSubRecordsValidation: ok&#xA;StorageGRID-XG-102.melEventCheck: ok&#xA;StorageGRID-XG-102.validPassword: ok&#xA;StorageGRID-XG-102.failedDrivesPresent: ok&#xA;StorageGRID-XG-102.exclusiveOperations: ok&#xA;StorageGRID-XG-102.driveCheck: ok&#xA;StorageGRID-XG-102.nvsramDisableCfwDownloads: ok&#xA;StorageGRID-XG-102.hotSparesInUse: ok&#xA;StorageGRID-XG-102.controllerStatusOptimal: ok&#xA;StorageGRID-XG-102.volumeGroupsComplete: ok&#xA;StorageGRID-XG-102.objectGraphSyncCheck: ok&#xA;StorageGRID-XG-102.configurationDatabaseCheck: ok&#xA;StorageGRID-XG-102.spmDatabaseVerification: ok&#xA;StorageGRID-XG-102.storageDeviceAccessible: ok&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;technical-details&#34;&gt;Technical Details&lt;/h2&gt;&#xA;&lt;p&gt;Check E-Series is a monitoring-plugin for &lt;strong&gt;Nagios-compatible system-monitoring&lt;/strong&gt; 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.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Update function and Grafana compatibility</title>
      <link>https://blog.monitoring-plugins.pro/posts/update-function-and-grafana-compatibility/</link>
      <pubDate>Sat, 17 Feb 2018 18:39:52 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/update-function-and-grafana-compatibility/</guid>
      <description>&lt;p&gt;I can recommend the unstable release &lt;strong&gt;3.10.1_10&lt;/strong&gt; to all experimenting monitoring admins. Above all, this has the character of a technology preview. Included are two major innovations:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The update mode for all getters&lt;/li&gt;&#xA;&lt;li&gt;The option to output Grafana compatible performance data even for status checks.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;update-mode&#34;&gt;Update Mode&lt;/h2&gt;&#xA;&lt;p&gt;The update mode for the getter is quickly explained: adding the option &amp;ndash;update and an age, the getter is instructed to check the existing store first to its age before contacting the filer. Example:```&#xA;$ ./get_netapp_cm.pl -H filer -o volume &amp;ndash;update=3min&#xA;Data for object &amp;lsquo;volume&amp;rsquo; collected within 0.576s. Number of instances stored: 6&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ignore Case for -exclude</title>
      <link>https://blog.monitoring-plugins.pro/posts/ignore-case-for-exclude/</link>
      <pubDate>Tue, 13 Jun 2017 20:31:14 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/ignore-case-for-exclude/</guid>
      <description>&lt;p&gt;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.: &lt;code&gt;$ ./check_netapp_pro.pl Usage ‑o volume ‑‑exclude=VMWare&lt;/code&gt; This snippet excludes all volumes &lt;strong&gt;containing&lt;/strong&gt; ‚VMWare‘ in their name (&lt;em&gt;AB_VMWare_vol1&lt;/em&gt;, &lt;em&gt;AB_VMWare_vol2&lt;/em&gt;, …). 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 &lt;em&gt;AB_VMWare_vol1&lt;/em&gt; 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. &lt;code&gt;$ ./check_netapp_pro.pl Usage ‑o volume ‑‑exclude=VMWare ‑‑ignore_case&lt;/code&gt; In this case, all possible notations of VMWare would be matched, such as:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Testing/Fixing Release 3.4.1_01</title>
      <link>https://blog.monitoring-plugins.pro/posts/testingfixing-release-3-4-1_01-2/</link>
      <pubDate>Wed, 16 Mar 2016 18:17:54 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/testingfixing-release-3-4-1_01-2/</guid>
      <description>&lt;h1 id=&#34;341_01-fixes-usageshelf-environment-diskcount-workload-lunsize&#34;&gt;3.4.1_01 FIXES USAGE/SHELF-ENVIRONMENT, DISKCOUNT, WORKLOAD, LUNSIZE&lt;/h1&gt;&#xA;&lt;p&gt;Released 2016-03-18&lt;/p&gt;&#xA;&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Usage&lt;/strong&gt;-Check: Handling of volumes with no state-attribute&lt;/li&gt;&#xA;&lt;li&gt;&lt;em&gt;shelf-environment&lt;/em&gt;-object in cm-getter needs a node-name (sometimes)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;new-and-improved&#34;&gt;New and improved&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;new &lt;strong&gt;DiskCount&lt;/strong&gt; check (counts spare-disks per type or storage-pool)&lt;/li&gt;&#xA;&lt;li&gt;new &lt;em&gt;workload&lt;/em&gt;-object in the perf-getter (in preparation for a cdot total-ops check)&lt;/li&gt;&#xA;&lt;li&gt;extended &lt;em&gt;lun&lt;/em&gt;-object in the 7m/cm-getters (in preparation for a LunSize check)&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>DiskCount counts SSD spare disks</title>
      <link>https://blog.monitoring-plugins.pro/posts/diskcount-counts-ssd-spare-disks/</link>
      <pubDate>Tue, 08 Mar 2016 20:01:51 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/diskcount-counts-ssd-spare-disks/</guid>
      <description>&lt;p&gt;Our new &lt;a href=&#34;https://netapp-monitoring.info/en/help/DiskCount.html&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;DiskCount&lt;/a&gt;&#xA; check counts available disks on a system. This can be quite handy when setting a filter, e.g. only counting SSD drives in the spare container. This way, one can use thresholds to send warning messages as soon as the number of spare SSD disks falls below a certain threshold. In contrast to the previously available check check_netapp_spare, &lt;strong&gt;DiskCount&lt;/strong&gt; can be configured with a detailed set of criteria for its alert messages. Example: &lt;code&gt;./check_netapp_pro.pl DiskCount ... ‑‑container_type=spare ‑‑disk_type=SSD ‑w 1 ‑c 1 NETAPP_PRO DISKCOUNT OK - 1 disk with matching criteria found. NA17-01 1.1.12: - spare SSD | disk_count=1;1;1;0;&lt;/code&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Alarm for non-zeroed Spare Disks</title>
      <link>https://blog.monitoring-plugins.pro/posts/alarm-for-non-zeroed-spare-disks/</link>
      <pubDate>Fri, 11 Dec 2015 23:03:58 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/alarm-for-non-zeroed-spare-disks/</guid>
      <description>&lt;p&gt;Our &lt;a href=&#34;https://netapp-monitoring.info/en/help/Disk&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Disk&lt;/a&gt;&#xA; check is going to have a new feature. Using the switch &lt;code&gt;‑‑what=non-zeroed-spare&lt;/code&gt; an alarm is sent as soon as non-zeroed spare disks have been found. Depending on wether the zeroing process is currently running or not, a WARNING (including progress) will be sent or else CRITICAL.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Check the Is-home flag of a network port</title>
      <link>https://blog.monitoring-plugins.pro/posts/check-the-is-home-flag-of-a-network-port/</link>
      <pubDate>Wed, 29 Apr 2015 10:34:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/check-the-is-home-flag-of-a-network-port/</guid>
      <description>&lt;p&gt;Today we announce a new check &lt;a href=&#34;https://netapp-monitoring.info/en/help/NetInterface.html&#34; title=&#34;Help for NetInterface&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;NetInterface&lt;/a&gt;&#xA; which monitors the Is-Home flag of a network interface and sends an alarm if current-port differs from home-port. This enables us to monitor the output of the following CLI command in a continuous and automated way:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;clu1::&amp;gt; network interface show -is-home false &#xA;Logical    Status   Network . Current      Is-Home &#xA;----------- -------- ---------- ------------ ------- &#xA;upgradelif  up/up    10.24.33.82/24 clu1-02 e0a   false&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Also refer to &lt;em&gt;Enabling and reverting LIFs to home ports&lt;/em&gt; (library.netapp.com/ecmdocs/ECMP1196799/html/GUID-7865FB3E-F57B-4976-803D-A87F2F760342.html &amp;ldquo;NetApp Support Article Enabling and reverting LIFs to home ports&amp;rdquo; (not openly available any more)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Monitoring Network Interfaces in DataONTAP 8.2.1</title>
      <link>https://blog.monitoring-plugins.pro/posts/monitoring-network-interfaces-in-dataontap-8-2-1/</link>
      <pubDate>Tue, 21 Oct 2014 13:39:00 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/monitoring-network-interfaces-in-dataontap-8-2-1/</guid>
      <description>&lt;p&gt;In cmode DataONTAp 8.2.1, the object &lt;em&gt;ifnet,&lt;/em&gt; used for monitoring the network performance will no longer be available. It will be replaced by the new performance object &lt;em&gt;lif&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Since there have been quite a few changes with the counters, the next release will include an additional check: &lt;a href=&#34;http://netapp-monitoring.info/en/help/PerfLif.html&#34; title=&#34;Help for the NetApp Monitoring Plugin PerfLif&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;PerfLif&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;This check works as follows:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;--------------------------------------------------------&#xA; recv_data = Number of bytes received per second &#xA;--------------------------------------------------------&#xA; recv_errors = Number of received Errors per second&#xA;--------------------------------------------------------&#xA; recv_packet = Number of packets received per second&#xA;--------------------------------------------------------&#xA; sent_data = Number of bytes sent per second &#xA;--------------------------------------------------------&#xA; sent_errors = Number of sent errors per second&#xA;--------------------------------------------------------&#xA; sent_packet = Number of packets sent per second &#xA;--------------------------------------------------------&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The life uptime could also be monitored, but this feature is not yet implemented.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Monitoring Network Interfaces</title>
      <link>https://blog.monitoring-plugins.pro/posts/monitoring-network-interfaces/</link>
      <pubDate>Fri, 10 Oct 2014 15:18:49 +0000</pubDate>
      <guid>https://blog.monitoring-plugins.pro/posts/monitoring-network-interfaces/</guid>
      <description>&lt;p&gt;All in all, we are offering three different checks to monitor network interfaces from a NetApp Filer in the next release. All three of them support 7-mode as well as cluster mode filers:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://netapp-monitoring.info/en/help/NetPort.html&#34; title=&#34;NetPort checks help-screen&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;NetPort&lt;/a&gt;&#xA; or &lt;a href=&#34;http://netapp-monitoring.info/en/help/NetPort7m.html&#34; title=&#34;NetPort7m (for 7-Mode) checks help-screen&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;NetPort7m&lt;/a&gt;&#xA; checks if the network interfaces are activated or not.&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://netapp-monitoring.info/en/help/IfGrp.html&#34; title=&#34;IfGrp checks help-screen&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;IfGrp&lt;/a&gt;&#xA; checks if an interface group has enough links in the status up in order to remain redundant.&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://netapp-monitoring.info/en/help/PerfIf.html&#34; title=&#34;PerfIf checks help-screen&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;PerfIf&lt;/a&gt;&#xA; (or &lt;a href=&#34;https://netapp-monitoring.info/en/help/PerfLif.html&#34; title=&#34;Help for the PerfLif Nagios-Check for NetApp&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;PerfLif&lt;/a&gt;&#xA; if you are monitoring a cluster-mode filer with DataONTAP &amp;gt;=8.2.x) checks and counts the transfer rates or error for each network interface.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
  </channel>
</rss>
