<?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 Unknown Blade after OBA firmware upgrade to version 2.25 in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287969#M4111</link>
    <description>We had performed an OBA firmware upgrade ( version 2.25 )&lt;BR /&gt;The upgrade was successful, however after the OBA upgrade,&lt;BR /&gt;the blades are appearing as "Unknown" with Critical Error.&lt;BR /&gt;iLo2 are inaccessible.&lt;BR /&gt;&lt;BR /&gt;We missed to perform the following warning before the OBA update.&lt;BR /&gt;&lt;BR /&gt;Important: &lt;BR /&gt;WARNING: &lt;BR /&gt;&lt;BR /&gt;iLO2 version 1.60 for HP ProLiant blade servers is recommended with Onboard Administrator v2.25.&lt;BR /&gt;Please upgrade the iLO2 version to v1.60 or greater before attempting to upgrade the Onboard &lt;BR /&gt;&lt;BR /&gt;There are only two blades, one of them is already running 1.6 version of iLo2, however the other was not upgraded. However both became "unknown" after the upgrade.&lt;BR /&gt;&lt;BR /&gt;We had tried rebooting the enclosure ( blade and OBA ) but still problem persists. Any fix on this? Thanks for you help.</description>
    <pubDate>Thu, 16 Oct 2008 05:12:51 GMT</pubDate>
    <dc:creator>ArjEE</dc:creator>
    <dc:date>2008-10-16T05:12:51Z</dc:date>
    <item>
      <title>Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287969#M4111</link>
      <description>We had performed an OBA firmware upgrade ( version 2.25 )&lt;BR /&gt;The upgrade was successful, however after the OBA upgrade,&lt;BR /&gt;the blades are appearing as "Unknown" with Critical Error.&lt;BR /&gt;iLo2 are inaccessible.&lt;BR /&gt;&lt;BR /&gt;We missed to perform the following warning before the OBA update.&lt;BR /&gt;&lt;BR /&gt;Important: &lt;BR /&gt;WARNING: &lt;BR /&gt;&lt;BR /&gt;iLO2 version 1.60 for HP ProLiant blade servers is recommended with Onboard Administrator v2.25.&lt;BR /&gt;Please upgrade the iLO2 version to v1.60 or greater before attempting to upgrade the Onboard &lt;BR /&gt;&lt;BR /&gt;There are only two blades, one of them is already running 1.6 version of iLo2, however the other was not upgraded. However both became "unknown" after the upgrade.&lt;BR /&gt;&lt;BR /&gt;We had tried rebooting the enclosure ( blade and OBA ) but still problem persists. Any fix on this? Thanks for you help.</description>
      <pubDate>Thu, 16 Oct 2008 05:12:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287969#M4111</guid>
      <dc:creator>ArjEE</dc:creator>
      <dc:date>2008-10-16T05:12:51Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287970#M4112</link>
      <description>Are you seeing any Suspicious entry in OA syslog related to the Blades or IlO's??&lt;BR /&gt;&lt;BR /&gt;Try to Do a "Reset server" from the OA CLI. This will work most of the times.</description>
      <pubDate>Thu, 16 Oct 2008 13:52:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287970#M4112</guid>
      <dc:creator>Raghuarch</dc:creator>
      <dc:date>2008-10-16T13:52:47Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287971#M4113</link>
      <description>Do the BIOS upgrade as well.&lt;BR /&gt;That fixes it.</description>
      <pubDate>Thu, 16 Oct 2008 14:06:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287971#M4113</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2008-10-16T14:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287972#M4114</link>
      <description>Jun&lt;BR /&gt;&lt;BR /&gt;The server name here relates to the bios server name - see this from help page in OA &amp;gt; Device Bay &amp;gt; UNKNOWN &amp;gt; information:&lt;BR /&gt;"BIOS Server Name - If configured, this is the server name of the installed server blade. This is not the OS server name." &lt;BR /&gt;&lt;BR /&gt;However, when you look at the ILO &amp;gt; system status &amp;gt; server status help they say "System Information&lt;BR /&gt;The Server Host Name, Rack UID, and Bay are not user-configurable fields. The Server Host Name is set by the server OS, provided the OS supports that feature."&lt;BR /&gt;&lt;BR /&gt;We have 2.25 and have a UNKNOWN label on one of our blades. No problem getting on the ILO though. Check your ebipa addressing is ok.&lt;BR /&gt;&lt;BR /&gt;As a matter of interest, what flavour are your blades? Proliant or Integrity?</description>
      <pubDate>Thu, 16 Oct 2008 14:15:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287972#M4114</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2008-10-16T14:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287973#M4115</link>
      <description>This page tells you the BIOS version your servers should have:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18004.www1.hp.com/products/blades/components/c-class-compmatrix.html" target="_blank"&gt;http://h18004.www1.hp.com/products/blades/components/c-class-compmatrix.html&lt;/A&gt;</description>
      <pubDate>Thu, 16 Oct 2008 14:20:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287973#M4115</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2008-10-16T14:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287974#M4116</link>
      <description>Thanks Raqhuarch. I will try to Do a "Reset server" from the OA CLI.&lt;BR /&gt;&lt;BR /&gt;There were no suspicious entry in the syslog aside from stating that the servers affected  appears to be unresponsive. (OA: Management Processor on Blade X appears unresponsive ).&lt;BR /&gt;&lt;BR /&gt;Will try to do BIOS update on the ILO as well.ILO addresses are not accessible, however the server OS is reachable.</description>
      <pubDate>Thu, 16 Oct 2008 14:32:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287974#M4116</guid>
      <dc:creator>ArjEE</dc:creator>
      <dc:date>2008-10-16T14:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287975#M4117</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Performed that " Reset Server" command on OBA CLI then rebooted the OA but the problem still persist.&lt;BR /&gt;&lt;BR /&gt;Blades are still appearing with "Critical Error" status and still displaying as "Unknown".ILO are still inacessible " Management processor information not available."&lt;BR /&gt;&lt;BR /&gt;Current IP address is not showing also when doing the show EBIPA command.&lt;BR /&gt;&lt;BR /&gt;Your inputs is highly appreciated.</description>
      <pubDate>Sat, 18 Oct 2008 21:51:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287975#M4117</guid>
      <dc:creator>ArjEE</dc:creator>
      <dc:date>2008-10-18T21:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Blade after OBA firmware upgrade to version 2.25</title>
      <link>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287976#M4118</link>
      <description>Sounds like its all got confused on the firmware upgrade. If you attempt to download your config script (enclosure info &amp;gt; reset factory defaults &amp;gt; 'click here' to download a script..) does it work? If so is you config correct? &lt;BR /&gt;&lt;BR /&gt;One thing we have done is to update the firmware a second time (same version). It sorted an issue unrelated to this, but could be worth a try?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Oct 2008 11:55:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/unknown-blade-after-oba-firmware-upgrade-to-version-2-25/m-p/4287976#M4118</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2008-10-21T11:55:36Z</dc:date>
    </item>
  </channel>
</rss>

