<?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 BL465c boot from SAN problems with QMH2462 in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372287#M5351</link>
    <description>We have a problem recently where we have some BL465c's where we have boot from SAN working. These are running vmware and after a update and these have rebooted. Some of these have suddenly stopped booting from SAN.&lt;BR /&gt;&lt;BR /&gt;I don't have access to software side of this, i'm only a hardware engineer. Any ideas on what to do would be much apreciated.&lt;BR /&gt;&lt;BR /&gt;I can tell you were running ILO 1.50 and and OA firmware 2.20. I have asked if they can upgrade these, but they can't do this unless I can prove this is a firmware issue.&lt;BR /&gt;&lt;BR /&gt;Also we have found replacing the fibre card and adding the new fibre to the EVA has fixed them. But were expecting to upgrade on over 100 servers, and i'm worried they will expect us to replace 50 odd fibre cards.</description>
    <pubDate>Thu, 05 Mar 2009 10:37:16 GMT</pubDate>
    <dc:creator>Koopa</dc:creator>
    <dc:date>2009-03-05T10:37:16Z</dc:date>
    <item>
      <title>BL465c boot from SAN problems with QMH2462</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372287#M5351</link>
      <description>We have a problem recently where we have some BL465c's where we have boot from SAN working. These are running vmware and after a update and these have rebooted. Some of these have suddenly stopped booting from SAN.&lt;BR /&gt;&lt;BR /&gt;I don't have access to software side of this, i'm only a hardware engineer. Any ideas on what to do would be much apreciated.&lt;BR /&gt;&lt;BR /&gt;I can tell you were running ILO 1.50 and and OA firmware 2.20. I have asked if they can upgrade these, but they can't do this unless I can prove this is a firmware issue.&lt;BR /&gt;&lt;BR /&gt;Also we have found replacing the fibre card and adding the new fibre to the EVA has fixed them. But were expecting to upgrade on over 100 servers, and i'm worried they will expect us to replace 50 odd fibre cards.</description>
      <pubDate>Thu, 05 Mar 2009 10:37:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372287#M5351</guid>
      <dc:creator>Koopa</dc:creator>
      <dc:date>2009-03-05T10:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: BL465c boot from SAN problems with QMH2462</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372288#M5352</link>
      <description>We have had 2 blades with the same fault, and we've swapped the fibre cards in these blades, and both are now working. So any idea what could have caused this?</description>
      <pubDate>Thu, 05 Mar 2009 16:04:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372288#M5352</guid>
      <dc:creator>Koopa</dc:creator>
      <dc:date>2009-03-05T16:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: BL465c boot from SAN problems with QMH2462</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372289#M5353</link>
      <description>without knowing SAN config, zoning, EVA config it's hard to tell anything wise.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Mar 2009 16:14:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl465c-boot-from-san-problems-with-qmh2462/m-p/4372289#M5353</guid>
      <dc:creator>JKytsi</dc:creator>
      <dc:date>2009-03-05T16:14:49Z</dc:date>
    </item>
  </channel>
</rss>

