<?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: Booting SUSE Linux From EVA3000 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894239#M22191</link>
    <description>Did you enable the bios in the Configuration Options? and Save the Config? then go to boot options and scan.&lt;BR /&gt;&lt;BR /&gt;Not sure what you mean by SSP.  There is no "SSP" on the EVA even though the concept is very similar.  Compared to the MSA where ALL Logical Drives are presented to ALL hosts by default.. the EVA presents NOTHING by default and you can only Select which hosts can see the Virtual Disks.&lt;BR /&gt;&lt;BR /&gt;Does your host definition on the EVA contrin the right World Wide ID?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steven</description>
    <pubDate>Tue, 07 Nov 2006 17:24:32 GMT</pubDate>
    <dc:creator>Steven Clementi</dc:creator>
    <dc:date>2006-11-07T17:24:32Z</dc:date>
    <item>
      <title>Booting SUSE Linux From EVA3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894238#M22190</link>
      <description>I have an EVA3K with VCS 3.028 and am trying to boot a Proliant DL380 with Qlogic HBA's to this array. I have created a LUN on the array with SSP to the HBA in the server (single HBA), but when I boot the server and hit ctrl Q to go into the HBA's active bios, I can see the EVA controller but not the LUN I assigned to the HBA. How can I get this LUN visible to the HBA so i can install Linux on the SAN for as a boot device?</description>
      <pubDate>Tue, 07 Nov 2006 17:14:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894238#M22190</guid>
      <dc:creator>mpierro</dc:creator>
      <dc:date>2006-11-07T17:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Booting SUSE Linux From EVA3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894239#M22191</link>
      <description>Did you enable the bios in the Configuration Options? and Save the Config? then go to boot options and scan.&lt;BR /&gt;&lt;BR /&gt;Not sure what you mean by SSP.  There is no "SSP" on the EVA even though the concept is very similar.  Compared to the MSA where ALL Logical Drives are presented to ALL hosts by default.. the EVA presents NOTHING by default and you can only Select which hosts can see the Virtual Disks.&lt;BR /&gt;&lt;BR /&gt;Does your host definition on the EVA contrin the right World Wide ID?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Tue, 07 Nov 2006 17:24:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894239#M22191</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2006-11-07T17:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: Booting SUSE Linux From EVA3000</title>
      <link>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894240#M22192</link>
      <description>Thanks for the response. What I meant by SSP was selective storage presentation. It's part of the VCS code for "LUN masking" within the storage. &lt;BR /&gt;&lt;BR /&gt;I fixed the issue. It was pilot error. I had the host definition operating system type set to "unknown". Once I chaged it to Solaris, it worked fine.&lt;BR /&gt;&lt;BR /&gt;Thanks for the help!</description>
      <pubDate>Tue, 07 Nov 2006 17:57:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/booting-suse-linux-from-eva3000/m-p/3894240#M22192</guid>
      <dc:creator>mpierro</dc:creator>
      <dc:date>2006-11-07T17:57:54Z</dc:date>
    </item>
  </channel>
</rss>

