<?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: OCUM Management console volume stats not updating in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Management-console-volume-stats-not-updating/m-p/123546#M22179</link>
    <description>&lt;P&gt;I found a command to enable counters - dfm perf data enable.&amp;nbsp; Even though perf data describe showed all counters enabled for the volume group, I tried enabling them again with dfm perf data enable &amp;lt;host&amp;gt; volume all, which failed for "unknown reasons".&amp;nbsp; I found in dfmserver.log:&lt;/P&gt;&lt;P&gt;Failed to add columns to &amp;lt;path&amp;gt;/perf_103_3801_178: No space left on device, even though there was plenty of space in the filesystem.&amp;nbsp; The file in question is the file that perf data describe shows as belonging to the volume data for the host in question, and was 4.3G.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thinking I'd hit a file size max, I reduced the retention for the group with dfm perf data modify&amp;nbsp; -f -G volume -o &amp;lt;host&amp;gt; -r 20days (from 30 days), which worked - perf data describe shows the oldest record 10 days newer than before, and the file shrank to just over 3G.&amp;nbsp; I ran dfm perf data enable again, which came back successful, but I still don't seem to be updating that group - perf data describe still shows the newest record as July 31.&amp;nbsp; I've restarted DFM.&lt;/P&gt;</description>
    <pubDate>Fri, 23 Sep 2016 18:32:06 GMT</pubDate>
    <dc:creator>billshaffer</dc:creator>
    <dc:date>2016-09-23T18:32:06Z</dc:date>
    <item>
      <title>OCUM Management console volume stats not updating</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Management-console-volume-stats-not-updating/m-p/123545#M22178</link>
      <description>&lt;P&gt;I'm running OCUM 5.2P1 on RHEL 5.11 against 4 HA Pairs of various hardware, all running 8.2.3P3 7-mode.&amp;nbsp; I see this issue on one controller of one HA pair - all other controllers look fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I went into the management console to look at volume performance for this one controller, and the latest info displayed was from several months ago (Jul 31).&amp;nbsp; All the physical components (aggrs, vifs, procs) for this controller have current data.&amp;nbsp; All the components of all the other controllers DFM monitors (including volumes) have current data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran dfm host diag for the controller, everything looks fine.&amp;nbsp; Perf Advisor Transport shows HTTPS Ok and a green data collection status.&amp;nbsp; Although, because the controller is getting other stats, I don't really suspect a communications issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I check the enabled volume counters between this controller and one that is working, they match.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I run dfm perf data list for the controller, and all counter groups have current records except for the volume group, whose newest record is July 31.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On July 31 we upgraded this HA pair from 8.1.2P3.&amp;nbsp; it seems something happened during that upgrade (on just that one controller) to stop volume stats from updating.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have any idea how I would re-enable those?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I appreciate any input...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bill&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 18:56:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Management-console-volume-stats-not-updating/m-p/123545#M22178</guid>
      <dc:creator>billshaffer</dc:creator>
      <dc:date>2025-06-04T18:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: OCUM Management console volume stats not updating</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Management-console-volume-stats-not-updating/m-p/123546#M22179</link>
      <description>&lt;P&gt;I found a command to enable counters - dfm perf data enable.&amp;nbsp; Even though perf data describe showed all counters enabled for the volume group, I tried enabling them again with dfm perf data enable &amp;lt;host&amp;gt; volume all, which failed for "unknown reasons".&amp;nbsp; I found in dfmserver.log:&lt;/P&gt;&lt;P&gt;Failed to add columns to &amp;lt;path&amp;gt;/perf_103_3801_178: No space left on device, even though there was plenty of space in the filesystem.&amp;nbsp; The file in question is the file that perf data describe shows as belonging to the volume data for the host in question, and was 4.3G.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thinking I'd hit a file size max, I reduced the retention for the group with dfm perf data modify&amp;nbsp; -f -G volume -o &amp;lt;host&amp;gt; -r 20days (from 30 days), which worked - perf data describe shows the oldest record 10 days newer than before, and the file shrank to just over 3G.&amp;nbsp; I ran dfm perf data enable again, which came back successful, but I still don't seem to be updating that group - perf data describe still shows the newest record as July 31.&amp;nbsp; I've restarted DFM.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Sep 2016 18:32:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OCUM-Management-console-volume-stats-not-updating/m-p/123546#M22179</guid>
      <dc:creator>billshaffer</dc:creator>
      <dc:date>2016-09-23T18:32:06Z</dc:date>
    </item>
  </channel>
</rss>

