<?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 OM CPU report and alarm inaccurate on new hardware platforms in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63710#M13292</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear NetApp Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The current OM CPU alarm and report takes it's value from the ANY1+ counter in Data ONTAP, as does sysstat -x 1.&amp;nbsp;&amp;nbsp; On multi-processor /&amp;nbsp; multi-core storage systems such as the FAS6210A storage system which has eight processing cores, the OM CPU threshold is often breached (95%) causing undue concern to customers when OM issues an alarm. ANY1+ exceeds 95% when processes such as deduplication kick in. However when you look at the output of sysstat -M, each individual processor cores isless than 50% utilized, and processing domains are not stretched.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is to the OnCommand UM experts - is there a more intelligent way to monitor CPU utilization and produce an alarm or report when a threshold on an individual processor or core is breached? Thus far I can't see how to do this in OnCommand UM 5.0.2 or 5.1, which have great customized reporting capabilities but not for performance counters as far as I can see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greg Davis&lt;/P&gt;&lt;P&gt;PSC, ASEAN&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:20:24 GMT</pubDate>
    <dc:creator>dgreg</dc:creator>
    <dc:date>2025-06-05T06:20:24Z</dc:date>
    <item>
      <title>OM CPU report and alarm inaccurate on new hardware platforms</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63710#M13292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear NetApp Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The current OM CPU alarm and report takes it's value from the ANY1+ counter in Data ONTAP, as does sysstat -x 1.&amp;nbsp;&amp;nbsp; On multi-processor /&amp;nbsp; multi-core storage systems such as the FAS6210A storage system which has eight processing cores, the OM CPU threshold is often breached (95%) causing undue concern to customers when OM issues an alarm. ANY1+ exceeds 95% when processes such as deduplication kick in. However when you look at the output of sysstat -M, each individual processor cores isless than 50% utilized, and processing domains are not stretched.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is to the OnCommand UM experts - is there a more intelligent way to monitor CPU utilization and produce an alarm or report when a threshold on an individual processor or core is breached? Thus far I can't see how to do this in OnCommand UM 5.0.2 or 5.1, which have great customized reporting capabilities but not for performance counters as far as I can see.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greg Davis&lt;/P&gt;&lt;P&gt;PSC, ASEAN&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:20:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63710#M13292</guid>
      <dc:creator>dgreg</dc:creator>
      <dc:date>2025-06-05T06:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: OM CPU report and alarm inaccurate on new hardware platforms</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63716#M13293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Davis,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The value show in OnCommand for cpu utilization is the value return by snmp which includes all processors. If you would like to have individual processors cpu utilization, pls take a look at the Performance Advisor which gives the breakdown at individual processor level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;adai&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Aug 2012 06:24:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63716#M13293</guid>
      <dc:creator>adaikkap</dc:creator>
      <dc:date>2012-08-27T06:24:11Z</dc:date>
    </item>
    <item>
      <title>Re: OM CPU report and alarm inaccurate on new hardware platforms</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63726#M13294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your email and reply. Yes I agree, I've now found out how to set up a Threshold and Alarm for per processor CPU utilization in Performance Advisor, which is a much more useful counter to user for multicore / multiprocessor storage controllers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greg Davis&lt;/P&gt;&lt;P&gt;NetApp PSC, ASEAN&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Aug 2012 09:43:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OM-CPU-report-and-alarm-inaccurate-on-new-hardware-platforms/m-p/63726#M13294</guid>
      <dc:creator>dgreg</dc:creator>
      <dc:date>2012-08-27T09:43:26Z</dc:date>
    </item>
  </channel>
</rss>

