<?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: Map a LUN to multiple ESXi hosts in same Cluster in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454479#M10068</link>
    <description>&lt;P&gt;For NVMe/TCP steps are similar, I have&amp;nbsp;added some nqn to NVMe Subsystem:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Be sure to create a Storage VM with the NVMe/TCP protocol:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We write down the IP address, for example, 192.168.0.13. We remember it. Best practices to use 2 IP adresses.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create a new space in the Storage - NVMe namespaces tab:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In vCenter, we add a controller to each ESXi host for the NVMe TCP Adapter, specify the IP address 192.168.0.13 and port 8009:&lt;/P&gt;&lt;P&gt;On first WSXi:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On second ESXi:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On Cluster we do Rescan Storage:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We add a new Datastore, select our space, and format it:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This space is on both ESXi hosts.&lt;/P&gt;&lt;P&gt;Everything works.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Aug 2024 04:52:14 GMT</pubDate>
    <dc:creator>Sasnet</dc:creator>
    <dc:date>2024-08-14T04:52:14Z</dc:date>
    <item>
      <title>Map a LUN to multiple ESXi hosts in same Cluster</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454423#M10066</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are:&lt;/P&gt;&lt;P&gt;1) AFF-A250 Storage System;&lt;/P&gt;&lt;P&gt;2) VMware vCenter Cluster with many ESXi hosts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Need to map 1 LUN to&amp;nbsp;multiple ESXi hosts in same Cluster, protocol NVMe/TCP. I have find Knowledge Article:&amp;nbsp;&lt;A href="https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Can_we_map_a_lun_to_multiple_ESXi_host_in_different_cluster_managed_by_same_vCenter" target="_blank"&gt;https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Can_we_map_a_lun_to_multiple_ESXi_host_in_different_cluster_managed_by_same_vCenter&lt;/A&gt;&amp;nbsp;. It is possible, but for more information kindly reach out to VMware vendor.&amp;nbsp;&lt;/P&gt;&lt;P&gt;With mapping on 1 ESXi host - there are no problem, link:&amp;nbsp;&lt;A href="https://community.netapp.com/t5/Tech-ONTAP-Blogs/How-to-Configure-NVMe-TCP-with-vSphere-8-0-Update-1-and-ONTAP-9-13-1-for-VMFS/ba-p/445429" target="_blank"&gt;https://community.netapp.com/t5/Tech-ONTAP-Blogs/How-to-Configure-NVMe-TCP-with-vSphere-8-0-Update-1-and-ONTAP-9-13-1-for-VMFS/ba-p/445429&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, how to map 1 LUN to multiple ESXi hosts?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2024 11:59:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454423#M10066</guid>
      <dc:creator>Sasnet</dc:creator>
      <dc:date>2024-08-12T11:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: Map a LUN to multiple ESXi hosts in same Cluster</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454447#M10067</link>
      <description>&lt;P&gt;I think, I have solved request. Solution: SAN Initiator Groups.&lt;/P&gt;&lt;P&gt;Instruction:&lt;/P&gt;&lt;P&gt;Go to the HOSTS tab – SAN Initiator Groups. Click Add:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sasnet_0-1723534308047.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/28825iD6AC69C4A9274BF3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Sasnet_0-1723534308047.jpeg" alt="Sasnet_0-1723534308047.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Add Initiators, example!:&lt;BR /&gt;1) iqn.1998-01.com.vmware:esx1:619845978:65&lt;BR /&gt;2) iqn.1998-01.com.vmware:esx2.demo.netapp.com:619845978:65&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When creating a LUN, specify the created INITIATOR GROUP:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sasnet_1-1723534340030.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/28826iC6C8B09DBB4679CC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Sasnet_1-1723534340030.jpeg" alt="Sasnet_1-1723534340030.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Alternatively, you can edit an existing LUN to specify the desired group:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sasnet_2-1723534362478.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/28827iFCC04DB533337E7C/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Sasnet_2-1723534362478.jpeg" alt="Sasnet_2-1723534362478.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the test environment it worked:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sasnet_3-1723534410867.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/28828i473FD41AF20814D3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Sasnet_3-1723534410867.jpeg" alt="Sasnet_3-1723534410867.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sasnet_4-1723534416698.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.netapp.com/t5/image/serverpage/image-id/28829i44B41DC45EEDF81B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Sasnet_4-1723534416698.jpeg" alt="Sasnet_4-1723534416698.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Lab on Demand lab "Provisioning Desktops with NetApp and VMware Horizon v1.0".&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 07:34:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454447#M10067</guid>
      <dc:creator>Sasnet</dc:creator>
      <dc:date>2024-08-13T07:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: Map a LUN to multiple ESXi hosts in same Cluster</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454479#M10068</link>
      <description>&lt;P&gt;For NVMe/TCP steps are similar, I have&amp;nbsp;added some nqn to NVMe Subsystem:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Be sure to create a Storage VM with the NVMe/TCP protocol:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We write down the IP address, for example, 192.168.0.13. We remember it. Best practices to use 2 IP adresses.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create a new space in the Storage - NVMe namespaces tab:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In vCenter, we add a controller to each ESXi host for the NVMe TCP Adapter, specify the IP address 192.168.0.13 and port 8009:&lt;/P&gt;&lt;P&gt;On first WSXi:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On second ESXi:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On Cluster we do Rescan Storage:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We add a new Datastore, select our space, and format it:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This space is on both ESXi hosts.&lt;/P&gt;&lt;P&gt;Everything works.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2024 04:52:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454479#M10068</guid>
      <dc:creator>Sasnet</dc:creator>
      <dc:date>2024-08-14T04:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: Map a LUN to multiple ESXi hosts in same Cluster</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454547#M10069</link>
      <description>&lt;P&gt;Unlike LUN one cannot map NVMe to multiple Subsystem but instead we need to add multiple nqns to the same NVMe Subsystem and map the NVMe Namespace to the Subsystem.&lt;/P&gt;&lt;P&gt;--&lt;BR /&gt;Given that NetApp NVMe doesnt support Persistent Reservation , what is the Use case for NVMe Namespace to be shared between two ESXi Hosts in Cluster.&lt;/P&gt;</description>
      <pubDate>Sat, 17 Aug 2024 20:48:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Map-a-LUN-to-multiple-ESXi-hosts-in-same-Cluster/m-p/454547#M10069</guid>
      <dc:creator>jaikumar</dc:creator>
      <dc:date>2024-08-17T20:48:56Z</dc:date>
    </item>
  </channel>
</rss>

