<?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: Aggregate disks over-utilized - LEGIT? in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Aggregate-disks-over-utilized-LEGIT/m-p/129438#M23331</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've run into both issues with new ONTAP9 systems. &amp;nbsp;The system we had reporting over-utilization was a FAS8060 with a FlashPool enabled RAID-TEC SATA aggregate. &amp;nbsp;Anyway, we stood the system up and from ~1AM to ~5AM the aggregate would report over-utilized during raid-scrub. &amp;nbsp;Once we started putting "real" workloads on the system, the opportunistic raid-scrubs died down to background noise and now if we see an over-utilization it tends to be legit (i.e. usually our snapmirror jobs).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The disk-fragmentation thing appears to be a BURT:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/s/article/ka11A0000001Z2w/oncommand-performance-manager-alert-node-disk-fragmentation" target="_blank"&gt;https://kb.netapp.com/support/s/article/ka11A0000001Z2w/oncommand-performance-manager-alert-node-disk-fragmentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've run into this on a couple of aggregates (no rhyme or reason why some and not others are alerting - but that's why it's a BURT I 'spose).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Agreed that OCPM isn't all that DFM was. &amp;nbsp;We've been able to sleuth out some ways of getting almost the equivalent information we'd get from DFM but some of it is lacking. &amp;nbsp;That said, we've had better luck tuning the alerts like "vol growth rate abnormal" in OCPM than we ever did in OpsMgr/etc. &amp;nbsp;Maybe I never understood it entirely in the 7mode monitoring, but we were able to tweak the std deviation/etc in OCPM in such a way where abnormal really means abnormal (whereas we just stopped using it with OpsMgr/7mode).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
    <pubDate>Mon, 27 Mar 2017 16:18:16 GMT</pubDate>
    <dc:creator>colsen</dc:creator>
    <dc:date>2017-03-27T16:18:16Z</dc:date>
    <item>
      <title>Aggregate disks over-utilized - LEGIT?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Aggregate-disks-over-utilized-LEGIT/m-p/129380#M23312</link>
      <description>&lt;P&gt;&lt;U&gt;OnCommand Performance Manager&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Policy Name: Aggregate disks over-utilized&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Max Data Disk Utilization value of 99% on aggr2_6Gb has triggered a WARNING event based on threshold setting of 95%.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;------------------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We moved 5 DS2246 shelves populated with 900GB SAS drives from a retired FAS to our current FAS8200. Ever since, we've been receiving these alerts during early morning disk scrubs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thing is, we haven't even created any volumes on either aggregate residing on these shelves. This is our #1 built-in alert that we get from performance manager and I've come to believe that they are not terribly noteworthy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both aggrs are the same and constructed as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;58 disks, raid-dp, rg size 20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This alert and the 'Node disk fragmentation' canned alert come through a lot and given they're built-in, cannot be adjusted. This tool has really been kinda just meh for us as the lack of granularity in alerting rules just isn't near what used to be with DFM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:17:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Aggregate-disks-over-utilized-LEGIT/m-p/129380#M23312</guid>
      <dc:creator>bsnyder27</dc:creator>
      <dc:date>2025-06-04T15:17:32Z</dc:date>
    </item>
    <item>
      <title>Re: Aggregate disks over-utilized - LEGIT?</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Aggregate-disks-over-utilized-LEGIT/m-p/129438#M23331</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've run into both issues with new ONTAP9 systems. &amp;nbsp;The system we had reporting over-utilization was a FAS8060 with a FlashPool enabled RAID-TEC SATA aggregate. &amp;nbsp;Anyway, we stood the system up and from ~1AM to ~5AM the aggregate would report over-utilized during raid-scrub. &amp;nbsp;Once we started putting "real" workloads on the system, the opportunistic raid-scrubs died down to background noise and now if we see an over-utilization it tends to be legit (i.e. usually our snapmirror jobs).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The disk-fragmentation thing appears to be a BURT:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/s/article/ka11A0000001Z2w/oncommand-performance-manager-alert-node-disk-fragmentation" target="_blank"&gt;https://kb.netapp.com/support/s/article/ka11A0000001Z2w/oncommand-performance-manager-alert-node-disk-fragmentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've run into this on a couple of aggregates (no rhyme or reason why some and not others are alerting - but that's why it's a BURT I 'spose).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Agreed that OCPM isn't all that DFM was. &amp;nbsp;We've been able to sleuth out some ways of getting almost the equivalent information we'd get from DFM but some of it is lacking. &amp;nbsp;That said, we've had better luck tuning the alerts like "vol growth rate abnormal" in OCPM than we ever did in OpsMgr/etc. &amp;nbsp;Maybe I never understood it entirely in the 7mode monitoring, but we were able to tweak the std deviation/etc in OCPM in such a way where abnormal really means abnormal (whereas we just stopped using it with OpsMgr/7mode).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2017 16:18:16 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Aggregate-disks-over-utilized-LEGIT/m-p/129438#M23331</guid>
      <dc:creator>colsen</dc:creator>
      <dc:date>2017-03-27T16:18:16Z</dc:date>
    </item>
  </channel>
</rss>

