<?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: SAN in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712781#M2756</link>
    <description>Ours servers is Win2003 servers</description>
    <pubDate>Thu, 19 Jan 2006 03:09:38 GMT</pubDate>
    <dc:creator>PProcopi_1</dc:creator>
    <dc:date>2006-01-19T03:09:38Z</dc:date>
    <item>
      <title>SAN</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712780#M2755</link>
      <description>We have configure MSA1000/4 SCSI disks as Raid5 and connect to 4 blades servers with fibre cables via 2 SAN switches 2/8V.We have Enabling Windows basic failover so now blades servers works fine. My Q is what happen if i have hardware problem and i have to replace QLogic Fibre cards on one Blade ( Blade1 )server. How Blade1 server with new QLogic Fibre card will access Blade1's data on SAN disks???</description>
      <pubDate>Thu, 19 Jan 2006 03:06:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712780#M2755</guid>
      <dc:creator>PProcopi_1</dc:creator>
      <dc:date>2006-01-19T03:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: SAN</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712781#M2756</link>
      <description>Ours servers is Win2003 servers</description>
      <pubDate>Thu, 19 Jan 2006 03:09:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712781#M2756</guid>
      <dc:creator>PProcopi_1</dc:creator>
      <dc:date>2006-01-19T03:09:38Z</dc:date>
    </item>
    <item>
      <title>Re: SAN</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712782#M2757</link>
      <description>Since you should be using SSP, you would just power on the server with the new HBA, open up the ACU on another server and change the SSP to present the original LUN's to the new WWID of the new HBA.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steven&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jan 2006 22:39:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712782#M2757</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2006-01-23T22:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: SAN</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712783#M2758</link>
      <description>Hi,&lt;BR /&gt;In a SAN environment all your setup info is stored on you Fcard. So if you end up with a faulty card, you would have to once again run through fcard BIOS setup and do what you had done the first time you connected your blades to SAN. But before you could see a connectivity to your blades through this BIOS you would need to change WWID in your SAN settings to the new ones on your fcard. Such as Comand View for an example.</description>
      <pubDate>Thu, 02 Feb 2006 06:35:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/san/m-p/3712783#M2758</guid>
      <dc:creator>Albert Austin</dc:creator>
      <dc:date>2006-02-02T06:35:56Z</dc:date>
    </item>
  </channel>
</rss>

