<?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 LUN 0 on va7400 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891290#M7254</link>
    <description>I've run into a problem on my va7400 with a "phantom lun 0" that sounds similar to an earlier thread on Nikes w/version 11.0.0;&lt;BR /&gt;(&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc7e4a848deccd61190050090279cd0f9,00.html)" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc7e4a848deccd61190050090279cd0f9,00.html)&lt;/A&gt; &lt;BR /&gt;but I'd like to be sure before I put this system into production.&lt;BR /&gt;I'm running an rp8400 hard partitioned into 2 hosts (11i) connecting to the va7400 via 2 brocade switches. Everything is redundant, hdw paths, controllers, etc. When I first started creating luns, there were none, and I created a 10mb lun 0 (fooling around). I later combined this lun w/100 gb lun into a single volume group; I put both paths into the same pvg. &lt;BR /&gt;I decided to get rid of the 10mb lun, so I used SAM to remove lvol's, vg's, then armcfg -L 0 -d &lt;ARRAY-ID&gt;. OOPs, forgot the pvremove, but I had already rm'd the device files.  I repeated this process for lun 1 (which had been combined w/lun 0).&lt;BR /&gt;When I run an ioscan -fnC disk, both paths show up with "NO HDW". Armdsp -L shows no lun 0. Same when I reboot; on both systems. I also recreated a 100gb lun 1; when I ran insf -C disk, it created device files for both hdw paths. So now, in sam, I get this msg: /opt/sanmgr/commandview/client/sbin/armdsp, did not                    &lt;BR /&gt; provide a Serial Number for device file /dev/dsk/c6t0d0.  (It can't find the lun).&lt;BR /&gt;&lt;BR /&gt;What has me concerned: Before I created the first lun, ioscans never showed lun 0. The prior thread mentions this problem w/hpux 11.0.0 on Nike arrays, but no mention of this os or platform. I've searched quite a few threads looking for this situation.&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;/ARRAY-ID&gt;</description>
    <pubDate>Tue, 28 Jan 2003 19:53:15 GMT</pubDate>
    <dc:creator>Randy Tarrier</dc:creator>
    <dc:date>2003-01-28T19:53:15Z</dc:date>
    <item>
      <title>LUN 0 on va7400</title>
      <link>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891290#M7254</link>
      <description>I've run into a problem on my va7400 with a "phantom lun 0" that sounds similar to an earlier thread on Nikes w/version 11.0.0;&lt;BR /&gt;(&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc7e4a848deccd61190050090279cd0f9,00.html)" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc7e4a848deccd61190050090279cd0f9,00.html)&lt;/A&gt; &lt;BR /&gt;but I'd like to be sure before I put this system into production.&lt;BR /&gt;I'm running an rp8400 hard partitioned into 2 hosts (11i) connecting to the va7400 via 2 brocade switches. Everything is redundant, hdw paths, controllers, etc. When I first started creating luns, there were none, and I created a 10mb lun 0 (fooling around). I later combined this lun w/100 gb lun into a single volume group; I put both paths into the same pvg. &lt;BR /&gt;I decided to get rid of the 10mb lun, so I used SAM to remove lvol's, vg's, then armcfg -L 0 -d &lt;ARRAY-ID&gt;. OOPs, forgot the pvremove, but I had already rm'd the device files.  I repeated this process for lun 1 (which had been combined w/lun 0).&lt;BR /&gt;When I run an ioscan -fnC disk, both paths show up with "NO HDW". Armdsp -L shows no lun 0. Same when I reboot; on both systems. I also recreated a 100gb lun 1; when I ran insf -C disk, it created device files for both hdw paths. So now, in sam, I get this msg: /opt/sanmgr/commandview/client/sbin/armdsp, did not                    &lt;BR /&gt; provide a Serial Number for device file /dev/dsk/c6t0d0.  (It can't find the lun).&lt;BR /&gt;&lt;BR /&gt;What has me concerned: Before I created the first lun, ioscans never showed lun 0. The prior thread mentions this problem w/hpux 11.0.0 on Nike arrays, but no mention of this os or platform. I've searched quite a few threads looking for this situation.&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;/ARRAY-ID&gt;</description>
      <pubDate>Tue, 28 Jan 2003 19:53:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891290#M7254</guid>
      <dc:creator>Randy Tarrier</dc:creator>
      <dc:date>2003-01-28T19:53:15Z</dc:date>
    </item>
    <item>
      <title>Re: LUN 0 on va7400</title>
      <link>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891291#M7255</link>
      <description>For VA management software to function correctly you have to create LUN 0. Recommendations are to have its size = 10mb, security permission = 'WC' and no user data on it.&lt;BR /&gt;If you do not create LUN 0 then array automatically creates phantom LUN to allow server to access all other (may be) existing LUNs on the same virtual SCSI bus.&lt;BR /&gt;If you can not create LUN 0 using arm* command now, please use serial connection to VFP (virtual front panel, serial ports at the back of VA, use one of them)&lt;BR /&gt;Eugeny</description>
      <pubDate>Tue, 28 Jan 2003 20:06:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891291#M7255</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2003-01-28T20:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: LUN 0 on va7400</title>
      <link>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891292#M7256</link>
      <description>&lt;BR /&gt; Hi,&lt;BR /&gt;&lt;BR /&gt; I create and delete LUNs and VGs using the VA'a commands. Logical volumes are created in SAM. No problems so far.</description>
      <pubDate>Tue, 28 Jan 2003 20:06:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891292#M7256</guid>
      <dc:creator>Khalid A. Al-Tayaran</dc:creator>
      <dc:date>2003-01-28T20:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: LUN 0 on va7400</title>
      <link>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891293#M7257</link>
      <description>So I was living right up until I put the first lun 0 in a vg. Live and learn.I recreated it at 10mb, and it can collect dust. Thanks for the responses!</description>
      <pubDate>Tue, 28 Jan 2003 20:14:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/lun-0-on-va7400/m-p/2891293#M7257</guid>
      <dc:creator>Randy Tarrier</dc:creator>
      <dc:date>2003-01-28T20:14:39Z</dc:date>
    </item>
  </channel>
</rss>

