<?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: Netapp Management Console 3.0: misleading no_atime_update recommendation and network graph problem in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Netapp-Management-Console-3-0-misleading-no-atime-update-recommendation-and/m-p/54226#M11271</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Had the same problem as 2 above, however from the manual:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Top Storage Systems by Network Throughput&lt;/P&gt;&lt;P&gt;This panel displays the load_total_mbps counter, which is calculated using the following formula:&lt;/P&gt;&lt;P&gt;load_total_mbps = load_inbound_mbps + load_outbound_mbps&lt;/P&gt;&lt;P&gt;load_inbound_mbps = system:system:net_data_recv + fcp:fcp:fcp_write_data +&lt;/P&gt;&lt;P&gt;iscsi:iscsi:iscsi_write_data&lt;/P&gt;&lt;P&gt;load_outbound_mbps = system:system:net_data_sent + fcp:fcp:fcp_read_data +&lt;/P&gt;&lt;P&gt;iscsi:iscsi:iscsi_read_data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We had stopped collecting FCP stats since it was not in use, therefore the "load" counters could not be calculated. Once we started collecting these again, the Network Throughput graph started to update again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Apr 2012 12:53:55 GMT</pubDate>
    <dc:creator>sgrant</dc:creator>
    <dc:date>2012-04-05T12:53:55Z</dc:date>
    <item>
      <title>Netapp Management Console 3.0: misleading no_atime_update recommendation and network graph problem</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Netapp-Management-Console-3-0-misleading-no-atime-update-recommendation-and/m-p/54220#M11269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I recently upgraded Operations manager to 4.0 and installed Netapp Management Console 3.0.The new features are very useful, especially client statistics, I'd like to be able to collect them at the volume level too.&lt;/P&gt;&lt;P&gt;I have noticed only 2 problems:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 - in the NAS Issues health check section of Diagnosis tool I get this recommendation&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Enable the no_atime_update option for volumes. This is recommended if you can tolerate losing a few seconds of access time information when a storage system crashes.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as I know if you enable no_atime_update the access time information is NEVER updated, while the recommendation seems to mean that it isn't updated only in case of storage crash. Do you have any idea of the rationale behind it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 - network throughput graphs are no longer updated, because the corresponding counters (load_inbound_mbps, load_outbound_mbps...) are missing. In the Data collection configuration wizard I can't find these counters. Is there a workaround other than create my custom graphs with the available counters?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="file:/C:/DOCUME%7E1/d6464/IMPOST%7E1/Temp/moz-screenshot.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:10:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Netapp-Management-Console-3-0-misleading-no-atime-update-recommendation-and/m-p/54220#M11269</guid>
      <dc:creator>cambiasso</dc:creator>
      <dc:date>2025-06-05T07:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: Netapp Management Console 3.0: misleading no_atime_update recommendation and network graph problem</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Netapp-Management-Console-3-0-misleading-no-atime-update-recommendation-and/m-p/54226#M11271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Had the same problem as 2 above, however from the manual:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Top Storage Systems by Network Throughput&lt;/P&gt;&lt;P&gt;This panel displays the load_total_mbps counter, which is calculated using the following formula:&lt;/P&gt;&lt;P&gt;load_total_mbps = load_inbound_mbps + load_outbound_mbps&lt;/P&gt;&lt;P&gt;load_inbound_mbps = system:system:net_data_recv + fcp:fcp:fcp_write_data +&lt;/P&gt;&lt;P&gt;iscsi:iscsi:iscsi_write_data&lt;/P&gt;&lt;P&gt;load_outbound_mbps = system:system:net_data_sent + fcp:fcp:fcp_read_data +&lt;/P&gt;&lt;P&gt;iscsi:iscsi:iscsi_read_data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We had stopped collecting FCP stats since it was not in use, therefore the "load" counters could not be calculated. Once we started collecting these again, the Network Throughput graph started to update again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Apr 2012 12:53:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Netapp-Management-Console-3-0-misleading-no-atime-update-recommendation-and/m-p/54226#M11271</guid>
      <dc:creator>sgrant</dc:creator>
      <dc:date>2012-04-05T12:53:55Z</dc:date>
    </item>
  </channel>
</rss>

