<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NetApp on blog.monitoring-plugins.pro</title>
    <link>https://blog.monitoring-plugins.pro/tags/netapp/</link>
    <description>Recent content in NetApp on blog.monitoring-plugins.pro</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Jun 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.monitoring-plugins.pro/tags/netapp/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
