<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SNMP volume instance in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122822#M26340</link>
    <description>&lt;P&gt;afaik, it seems like there's no way out... anyone knows counterexample?&lt;/P&gt;</description>
    <pubDate>Fri, 02 Sep 2016 01:49:41 GMT</pubDate>
    <dc:creator>Jeff_Yao</dc:creator>
    <dc:date>2016-09-02T01:49:41Z</dc:date>
    <item>
      <title>SNMP volume instance</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122576#M26313</link>
      <description>&lt;P&gt;I'm using WhatsUp Gold to monitor the sizing of the volumes on my filer running ONTAP 8.2.4 7-Mode. All the volumes have the same SNMP OID and are only distinguishable by their instance number. The problem is that every time the filer gets rebooted, the instance numbers on the filer get scrambled and I have to remap the SNMP monitor with the new instance numbers. Is there a way to make the volume instance numbers static, even after a reboot?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 19:24:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122576#M26313</guid>
      <dc:creator>_NETAPPUSER</dc:creator>
      <dc:date>2025-06-04T19:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP volume instance</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122822#M26340</link>
      <description>&lt;P&gt;afaik, it seems like there's no way out... anyone knows counterexample?&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2016 01:49:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122822#M26340</guid>
      <dc:creator>Jeff_Yao</dc:creator>
      <dc:date>2016-09-02T01:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP volume instance</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122919#M26354</link>
      <description>&lt;P&gt;Does this also apply to cDOT 8.3+?&lt;/P&gt;&lt;P&gt;I'm assuming that it does, I doubt that I would get permission to reboot one of our filers just to test it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know virtually nothing about WUG.&lt;/P&gt;&lt;P&gt;I have been using a monitoring tool called OpenNMS (&lt;A href="http://www.opennms.net" target="_blank"&gt;www.opennms.net&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;One of the features it has is to map the instance numbers to the associated volume names when it captures data via SNMP.&lt;/P&gt;&lt;P&gt;The data is stored by volume name and not by instance number.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2016 15:17:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SNMP-volume-instance/m-p/122919#M26354</guid>
      <dc:creator>MKELLYSCSC</dc:creator>
      <dc:date>2016-09-05T15:17:22Z</dc:date>
    </item>
  </channel>
</rss>

