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