<?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: insf -e doesn't create device files in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974071#M2568</link>
    <description />
    <pubDate>Thu, 15 May 2003 13:13:56 GMT</pubDate>
    <dc:creator>Tim Killinger</dc:creator>
    <dc:date>2003-05-15T13:13:56Z</dc:date>
    <item>
      <title>insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974067#M2564</link>
      <description>Both before and after I did a cold install of UX on our rp5450, insf -e does not create the device files for the 13 luns on our locally attached va7100. armdsp -i diplays the existing LUNS beautifully. A fresh install of commandview 1.06 on a fresh install of UX, the VA7100 is at HP16 (HP18 next week).&lt;BR /&gt;&lt;BR /&gt;We had this exact problem before the cold install...&lt;BR /&gt;&lt;BR /&gt;Any ideas??  Thanks in advance!!!</description>
      <pubDate>Thu, 15 May 2003 10:14:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974067#M2564</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2003-05-15T10:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974068#M2565</link>
      <description>If you do an ioscan -e, can you see your LUN's?&lt;BR /&gt;If you can, devices are showing NOHW, UNCLAIMED ?&lt;BR /&gt;&lt;BR /&gt;David.</description>
      <pubDate>Thu, 15 May 2003 10:38:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974068#M2565</guid>
      <dc:creator>David Navarro</dc:creator>
      <dc:date>2003-05-15T10:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974069#M2566</link>
      <description />
      <pubDate>Thu, 15 May 2003 11:40:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974069#M2566</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2003-05-15T11:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974070#M2567</link>
      <description>Actually here's only LUN 0 listed. I would recommend to:&lt;BR /&gt;- check host behavior table and/or default host behavior to be hpux;&lt;BR /&gt;- check VA security table (if security is turned on). Remember: if host's HBA is not listed in security table then it means that host will have no access to LUNs. But what about LUN 0 host sees? In usual configurations LUN 0 is assigned 'WC' access for all hosts, thus visible for everyone.&lt;BR /&gt;More information needed? Attach 'armdsp -a' output to your next reply&lt;BR /&gt;Eugeny</description>
      <pubDate>Thu, 15 May 2003 12:52:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974070#M2567</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2003-05-15T12:52:56Z</dc:date>
    </item>
    <item>
      <title>Re: insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974071#M2568</link>
      <description />
      <pubDate>Thu, 15 May 2003 13:13:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974071#M2568</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2003-05-15T13:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974072#M2569</link>
      <description>Very good. Security is enabled. Run&lt;BR /&gt;armsecure -r -f sec_tbl.txt -p &lt;PASSWD&gt; va7100&lt;BR /&gt;and look into sec_tbl.txt file contents. If you wish your hpux host to see, for example, LUN 5, you should insert a string&lt;BR /&gt;NODEWWN 50060b0000021b49    5 WC&lt;BR /&gt;with hosts's HBA WWN and download it back to VA using&lt;BR /&gt;armsecure -w -f sec_tbl.txt -p &lt;PASSWD&gt; va7100&lt;BR /&gt;Eugeny&lt;BR /&gt;PS. &lt;PASSWD&gt; is VA's security password&lt;/PASSWD&gt;&lt;/PASSWD&gt;&lt;/PASSWD&gt;</description>
      <pubDate>Thu, 15 May 2003 21:22:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974072#M2569</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2003-05-15T21:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: insf -e doesn't create device files</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974073#M2570</link>
      <description>Eugeny,&lt;BR /&gt;&lt;BR /&gt;That was it(security enabled) ! thanks so much!</description>
      <pubDate>Mon, 19 May 2003 18:06:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/insf-e-doesn-t-create-device-files/m-p/2974073#M2570</guid>
      <dc:creator>Tim Killinger</dc:creator>
      <dc:date>2003-05-19T18:06:18Z</dc:date>
    </item>
  </channel>
</rss>

