<?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: 10 node AFF Netapp cluster nodes highly utilized and unable to set maintenance window for upgrad in AFF</title>
    <link>https://community.netapp.com/t5/AFF/10-node-AFF-Netapp-cluster-nodes-highly-utilized-and-unable-to-set-maintenance/m-p/465536#M1456</link>
    <description>&lt;P&gt;9.11.1P8 to 9.15.1p16 can be done just in one upgrade, don't need to upgrade to 9.11.1p16. It will save you time and will require less reboots.&lt;BR /&gt;It can be done non disruptively, just to make sure that all checks and preparation are done before upgrade. You can follow Netapp Documentation page or request upgrade Advisor plan if you are using AIQDigitalAdviser&lt;BR /&gt;here is link to documentation page &lt;A href="https://docs.netapp.com/us-en/ontap/upgrade/automated-upgrade-task.html" target="_blank"&gt;https://docs.netapp.com/us-en/ontap/upgrade/automated-upgrade-task.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Feb 2026 20:55:52 GMT</pubDate>
    <dc:creator>yuls</dc:creator>
    <dc:date>2026-02-05T20:55:52Z</dc:date>
    <item>
      <title>10 node AFF Netapp cluster nodes highly utilized and unable to set maintenance window for upgrade</title>
      <link>https://community.netapp.com/t5/AFF/10-node-AFF-Netapp-cluster-nodes-highly-utilized-and-unable-to-set-maintenance/m-p/465315#M1451</link>
      <description>&lt;P&gt;10 node AFF Netapp cluster nodes highly utilized and unable to set maintenance windo for ONTAP upgrade.&lt;/P&gt;&lt;P&gt;Hi friends,&lt;BR /&gt;Need your valuable suggestion as always.&lt;BR /&gt;I have a 10 node cluster which is highly utilized all times. Among those 2 nodes are hitting 80% on regular basis. As this a critical cluster I am unable to set a maintenance window for ONTAP upgrade. Vol move activity are not possible at the moment as need to upgrade cluster by next week. Any valuable suggestions please let me how to proceed with maintenance window. Is there any critical parameter like IOPs, latency which I can look into for performance and decide to set maintenance window. It should be non disruptive upgrade and Host team should not have any downtime during the activity. ONTAP Version upgrade planned from 9.11.1p8 to 9.11.1p16 to 9.15.1p16,it is a multi hop upgrade.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Jan 2026 21:23:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/10-node-AFF-Netapp-cluster-nodes-highly-utilized-and-unable-to-set-maintenance/m-p/465315#M1451</guid>
      <dc:creator>Pkjnetapp</dc:creator>
      <dc:date>2026-01-25T21:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: 10 node AFF Netapp cluster nodes highly utilized and unable to set maintenance window for upgrad</title>
      <link>https://community.netapp.com/t5/AFF/10-node-AFF-Netapp-cluster-nodes-highly-utilized-and-unable-to-set-maintenance/m-p/465536#M1456</link>
      <description>&lt;P&gt;9.11.1P8 to 9.15.1p16 can be done just in one upgrade, don't need to upgrade to 9.11.1p16. It will save you time and will require less reboots.&lt;BR /&gt;It can be done non disruptively, just to make sure that all checks and preparation are done before upgrade. You can follow Netapp Documentation page or request upgrade Advisor plan if you are using AIQDigitalAdviser&lt;BR /&gt;here is link to documentation page &lt;A href="https://docs.netapp.com/us-en/ontap/upgrade/automated-upgrade-task.html" target="_blank"&gt;https://docs.netapp.com/us-en/ontap/upgrade/automated-upgrade-task.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 20:55:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/AFF/10-node-AFF-Netapp-cluster-nodes-highly-utilized-and-unable-to-set-maintenance/m-p/465536#M1456</guid>
      <dc:creator>yuls</dc:creator>
      <dc:date>2026-02-05T20:55:52Z</dc:date>
    </item>
  </channel>
</rss>

