<?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 Restrict SnapDrive LUN ID from using 0 in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40164#M10502</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri;"&gt;I’m working with SnapDrive for Linux 4.1, installed on Suse Linux 10.2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, Verdana, Helvetica, Arial;"&gt;&lt;SPAN&gt;&lt;BR /&gt; When I issue the command:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;Snapdrive storage create –lun 192.168.1.15:/vol/suseeng/suseq/senglun –lunsize 75g&lt;BR /&gt;&lt;/SPAN&gt; &lt;SPAN style="font-family: Calibri, Verdana, Helvetica, Arial;"&gt;It created the LUN with ID 0, which always fails.&amp;nbsp; I want it to create it with LUN ID 1 (or the next available LUN ID).&lt;BR /&gt; When I specify to create 2 or more LUNS, everything higher than LUN ID 0 works fine.&lt;BR /&gt; I looked on the NetApp communities blog and see several others have the same issue, so I’m thinking a solution would be to have SnapDrive start with LUN ID 1 instead of 0.&lt;BR /&gt;&lt;BR /&gt; Do you know what file I would modify to tell SnapDrive to start with LUN ID 1?&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;!--EndFragment--&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:28:12 GMT</pubDate>
    <dc:creator>peterh</dc:creator>
    <dc:date>2025-06-05T07:28:12Z</dc:date>
    <item>
      <title>Restrict SnapDrive LUN ID from using 0</title>
      <link>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40164#M10502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri;"&gt;I’m working with SnapDrive for Linux 4.1, installed on Suse Linux 10.2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, Verdana, Helvetica, Arial;"&gt;&lt;SPAN&gt;&lt;BR /&gt; When I issue the command:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN&gt;&lt;SPAN style="font-family: 'Courier New';"&gt;Snapdrive storage create –lun 192.168.1.15:/vol/suseeng/suseq/senglun –lunsize 75g&lt;BR /&gt;&lt;/SPAN&gt; &lt;SPAN style="font-family: Calibri, Verdana, Helvetica, Arial;"&gt;It created the LUN with ID 0, which always fails.&amp;nbsp; I want it to create it with LUN ID 1 (or the next available LUN ID).&lt;BR /&gt; When I specify to create 2 or more LUNS, everything higher than LUN ID 0 works fine.&lt;BR /&gt; I looked on the NetApp communities blog and see several others have the same issue, so I’m thinking a solution would be to have SnapDrive start with LUN ID 1 instead of 0.&lt;BR /&gt;&lt;BR /&gt; Do you know what file I would modify to tell SnapDrive to start with LUN ID 1?&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;!--EndFragment--&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:28:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40164#M10502</guid>
      <dc:creator>peterh</dc:creator>
      <dc:date>2025-06-05T07:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict SnapDrive LUN ID from using 0</title>
      <link>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40169#M10503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a workaround you can create a dummy lun and map it to the igroup created/used by SDU, such that it gets the ID 0 and continue to use SDU for other luns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;&amp;gt; &lt;EM&gt;Do you know what file I would modify to tell SnapDrive to start with LUN ID 1?&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;LUN IDs are actually assigned by the filer when a lun is mapped to an igroup. So, SDU has no control over choosing a LUN ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BTW, are you using FCP or iSCSI?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rushi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 May 2009 14:58:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40169#M10503</guid>
      <dc:creator>rushi</dc:creator>
      <dc:date>2009-05-12T14:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict SnapDrive LUN ID from using 0</title>
      <link>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40177#M10504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In fact that is how I did a work-around, but I wasn't really happy with it because I want to demo SnapDrive for Unix with iSCSI to a potential customer, and wish to have everything automated.&amp;nbsp; If I create the first LUN with ID 0, then I must manually show them the steps, i.e. creating the initiator group, LUN, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was hoping their was a way to work around this by telling the OS, SnapDrive or placing a switch in the create snapdrive cli to use a specific LUN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 May 2009 17:56:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40177#M10504</guid>
      <dc:creator>peterh</dc:creator>
      <dc:date>2009-05-12T17:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict SnapDrive LUN ID from using 0</title>
      <link>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40183#M10505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmmm.....what version of Data ONTap?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It sounds similar to mapping a LUN ID in FilerView without specifying a LUN ID -- FilerView just picks the lowest free one for you. So....if the underlying API calls in ONTap have issues with that....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2009 01:42:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40183#M10505</guid>
      <dc:creator>amiller_1</dc:creator>
      <dc:date>2009-05-13T01:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict SnapDrive LUN ID from using 0</title>
      <link>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40189#M10506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Data ONTAP 7.3.1.P1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2009 01:50:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Restrict-SnapDrive-LUN-ID-from-using-0/m-p/40189#M10506</guid>
      <dc:creator>peterh</dc:creator>
      <dc:date>2009-05-13T01:50:45Z</dc:date>
    </item>
  </channel>
</rss>

