<?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: reassigning LUN IDs in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/reassigning-LUN-IDs/m-p/104086#M8172</link>
    <description>&lt;P&gt;In a world where everything is 100% perfectly configured, you might be able to unmap the LUN, remap the LUN with a new ID, rescan for disks and datastores at all the ESX hosts, and get by with your guests not noticing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;U&gt;&lt;STRONG&gt;DON'T TRY IT.&lt;/STRONG&gt; &lt;/U&gt;&lt;/EM&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something in your environment isn't setup get through that procedure, and by definition it will cause a problem with what you can least afford to lose.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pick a LUN - shutdown the guests that use the LUN, unmap, remap, rescan for disks and datastores, restart the affected guests. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Alternatively, vMotion all the guests that use the&amp;nbsp;LUN onto the host or hosts that has the same LUN with the ID you want. &amp;nbsp;Then do the unmap/remap/rescan bit on just the one host that isn't using the LUN. &amp;nbsp;Then you can rebalance back. &amp;nbsp;But be sure you know what you are doing - you need to turn off anything that might automatically try to migrate load back to the one host while you are messing with it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I prefer the shutdown mechanism for this, since you can then fix up all ESX hosts that might need changing in one go.&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>Mon, 04 May 2015 20:55:45 GMT</pubDate>
    <dc:creator>bobshouseofcards</dc:creator>
    <dc:date>2015-05-04T20:55:45Z</dc:date>
    <item>
      <title>reassigning LUN IDs</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/reassigning-LUN-IDs/m-p/104081#M8171</link>
      <description>&lt;P&gt;Is it ok to reassign lun IDs with the lun online or would that cause an issue in vmware?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;when I do lun show -m&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I see some luns dont have the same LUN ID used and I think best practice is to use same lun ID across all initiators groups for each lun?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 04:23:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/reassigning-LUN-IDs/m-p/104081#M8171</guid>
      <dc:creator>TDUBB1234</dc:creator>
      <dc:date>2025-06-05T04:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: reassigning LUN IDs</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/reassigning-LUN-IDs/m-p/104086#M8172</link>
      <description>&lt;P&gt;In a world where everything is 100% perfectly configured, you might be able to unmap the LUN, remap the LUN with a new ID, rescan for disks and datastores at all the ESX hosts, and get by with your guests not noticing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;U&gt;&lt;STRONG&gt;DON'T TRY IT.&lt;/STRONG&gt; &lt;/U&gt;&lt;/EM&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something in your environment isn't setup get through that procedure, and by definition it will cause a problem with what you can least afford to lose.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pick a LUN - shutdown the guests that use the LUN, unmap, remap, rescan for disks and datastores, restart the affected guests. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Alternatively, vMotion all the guests that use the&amp;nbsp;LUN onto the host or hosts that has the same LUN with the ID you want. &amp;nbsp;Then do the unmap/remap/rescan bit on just the one host that isn't using the LUN. &amp;nbsp;Then you can rebalance back. &amp;nbsp;But be sure you know what you are doing - you need to turn off anything that might automatically try to migrate load back to the one host while you are messing with it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I prefer the shutdown mechanism for this, since you can then fix up all ESX hosts that might need changing in one go.&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>Mon, 04 May 2015 20:55:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/reassigning-LUN-IDs/m-p/104086#M8172</guid>
      <dc:creator>bobshouseofcards</dc:creator>
      <dc:date>2015-05-04T20:55:45Z</dc:date>
    </item>
  </channel>
</rss>

