<?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: NVMe load balancing between nodes in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/454548#M10070</link>
    <description>&lt;P&gt;Only way is to loadbalance between NVMe TCP IO workloads between 2 Nodes is use of Volume Move, Volume is NonDisruptive ( we set ana transition ).&lt;/P&gt;&lt;P&gt;--&lt;BR /&gt;Note:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;NVMe is still Active/Passive on both ASA and AFF.&lt;/LI&gt;&lt;LI&gt;Minimum 1 NVMe TCP LIF on Namespace owning Node and its HA Partner&lt;/LI&gt;&lt;LI&gt;We can use NVMe Host Priority If wanted throttle the IO or QoS&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;We dont Support NVMe Namespace Move&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;And may be use namespace statistics to IO workload between the Node.&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Sat, 17 Aug 2024 21:22:40 GMT</pubDate>
    <dc:creator>jaikumar</dc:creator>
    <dc:date>2024-08-17T21:22:40Z</dc:date>
    <item>
      <title>NVMe load balancing between nodes</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453056#M10050</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we have a 2-node AFF-A250 running ontap 9.14.1. I'm experimenting with NVMe over TCP and have a question:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;how can you load balance namespaces between the 2 nodes? When creating a namespace it's creates the volume automatically and chooses the aggregate by itself. How can you ensure that the NVMe namespace load is evenly distributed between the 2 nodes in the cluster?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2024 11:40:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453056#M10050</guid>
      <dc:creator>FrankWest</dc:creator>
      <dc:date>2024-06-04T11:40:19Z</dc:date>
    </item>
    <item>
      <title>Re: NVMe load balancing between nodes</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453058#M10051</link>
      <description>&lt;P&gt;&amp;gt; NVMe LIFs and namespaces must be hosted on the same node.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.netapp.com/us-en/ontap/nvme/support-limitations.html#additional-limitations" target="_blank"&gt;https://docs.netapp.com/us-en/ontap/nvme/support-limitations.html#additional-limitations&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2024 14:07:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453058#M10051</guid>
      <dc:creator>elementx</dc:creator>
      <dc:date>2024-06-04T14:07:34Z</dc:date>
    </item>
    <item>
      <title>Re: NVMe load balancing between nodes</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453060#M10052</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 4 lifs. 2 lifs per node for NVMe. Those were created after entering the 4 IP addresses when creating the SVM.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2024 14:34:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453060#M10052</guid>
      <dc:creator>FrankWest</dc:creator>
      <dc:date>2024-06-04T14:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: NVMe load balancing between nodes</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453085#M10053</link>
      <description>&lt;P&gt;That still fits within limitations described in that limitation, IMO.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*Within* a node load balancing to the same volume may be possible and happening (I haven't used NVMe/TCP, so I don't know for sure), but that wouldn't be your ask which is load-balancing to the same namespace *across* different nodes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2024 03:08:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/453085#M10053</guid>
      <dc:creator>elementx</dc:creator>
      <dc:date>2024-06-05T03:08:46Z</dc:date>
    </item>
    <item>
      <title>Re: NVMe load balancing between nodes</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/454548#M10070</link>
      <description>&lt;P&gt;Only way is to loadbalance between NVMe TCP IO workloads between 2 Nodes is use of Volume Move, Volume is NonDisruptive ( we set ana transition ).&lt;/P&gt;&lt;P&gt;--&lt;BR /&gt;Note:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;NVMe is still Active/Passive on both ASA and AFF.&lt;/LI&gt;&lt;LI&gt;Minimum 1 NVMe TCP LIF on Namespace owning Node and its HA Partner&lt;/LI&gt;&lt;LI&gt;We can use NVMe Host Priority If wanted throttle the IO or QoS&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;We dont Support NVMe Namespace Move&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;And may be use namespace statistics to IO workload between the Node.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Sat, 17 Aug 2024 21:22:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/NVMe-load-balancing-between-nodes/m-p/454548#M10070</guid>
      <dc:creator>jaikumar</dc:creator>
      <dc:date>2024-08-17T21:22:40Z</dc:date>
    </item>
  </channel>
</rss>

