<?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: iLO 2.5 upgrade to 2.55 issues in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978255#M159403</link>
    <description>&lt;P&gt;For what it's worth...I've been upgrading multiple Gen 8/9/10 servers from 2.50 to 2.55 without any issues or configuration loss.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Sep 2017 14:01:19 GMT</pubDate>
    <dc:creator>EricL2324</dc:creator>
    <dc:date>2017-09-27T14:01:19Z</dc:date>
    <item>
      <title>iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978227#M159385</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have upgraded iLO 2.5 to 2.55 and now I have issues with 30+ servers. iLO configuration got cleared (connection to IRS, iLO advanced license removed, Directory Server Settings, Directory Groups, Local Users, Administrator user password).&amp;nbsp;The Integrated Management Log is empty.&lt;/P&gt;&lt;P&gt;Configuration got cleared only for Gen8 servers but not for all.&lt;/P&gt;&lt;P&gt;UUID,&amp;nbsp;Server Serial Number,&amp;nbsp;System ROM,&amp;nbsp;System ROM Date,&amp;nbsp;Backup System ROM now is shown as&amp;nbsp;Unknown. iLO reset does not resolves an issue.&lt;/P&gt;&lt;P&gt;System Information gives almost no info about servers health.&lt;/P&gt;&lt;P&gt;Can anyone please advise what should I do next? How to fix this mess...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2017 08:56:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978227#M159385</guid>
      <dc:creator>KarolisS</dc:creator>
      <dc:date>2017-09-27T08:56:10Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978236#M159387</link>
      <description>&lt;P&gt;It is a mess.&lt;/P&gt;&lt;P&gt;if you reboot the server or better pull the plugs, ILO will work again, but the settings are lost until you reconfigure.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2017 11:29:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978236#M159387</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2017-09-27T11:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978241#M159390</link>
      <description>&lt;P&gt;you are right, after reboot iLO works, but settings are lost.&lt;BR /&gt;I was planing to upgrade 500+ more servers, but after this issue I will definetly won't going to do it.&lt;/P&gt;&lt;P&gt;Do you know why upgrade for some servers goes successfully and for some not?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2017 12:27:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978241#M159390</guid>
      <dc:creator>KarolisS</dc:creator>
      <dc:date>2017-09-27T12:27:49Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978242#M159391</link>
      <description>&lt;P&gt;KarolisS,&lt;/P&gt;&lt;P&gt;We ran into the same thing when we went to 2.54.&amp;nbsp; On the Gen8 servers only,&amp;nbsp;we had&amp;nbsp;9 ILOs that pretty much lost their configs and needed to be re-done - which for us was about a 15% failure rate. There is a known flake that from your note here apparently wasn't resolved in 2.55 - but I suspect it is a pre-existing condition and the upgrade actally brings that issue to light.&lt;/P&gt;&lt;P&gt;This did not happen with the ILO4's on any of our Gen9 servers, and we have&amp;nbsp;over 200&amp;nbsp;of them.&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2017 12:46:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978242#M159391</guid>
      <dc:creator>KenKrubsack</dc:creator>
      <dc:date>2017-09-27T12:46:57Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978243#M159392</link>
      <description>the related advisory is not 100% clear, but obviously the issue hits te partition table of the ILO NAND, so a reformat occurs. the nodes say it is solved with 2.54, but 2.55 still have the issue. or the issue is already there and is shown during upgrade</description>
      <pubDate>Wed, 27 Sep 2017 12:52:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978243#M159392</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2017-09-27T12:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978255#M159403</link>
      <description>&lt;P&gt;For what it's worth...I've been upgrading multiple Gen 8/9/10 servers from 2.50 to 2.55 without any issues or configuration loss.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2017 14:01:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978255#M159403</guid>
      <dc:creator>EricL2324</dc:creator>
      <dc:date>2017-09-27T14:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978367#M159424</link>
      <description>&lt;P&gt;Torsten,&lt;/P&gt;&lt;P&gt;The people I was working with gave me the impression the second half of your statement is&amp;nbsp;the situation&amp;nbsp;- the issue is already there and the upgrade brings it to light.&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2017 12:47:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978367#M159424</guid>
      <dc:creator>Ken Krubsack</dc:creator>
      <dc:date>2017-09-28T12:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978407#M159426</link>
      <description>&lt;P&gt;How many people are experiencing this serious issue with HP iLO 2.55? Is there an expected fix coming for this firmware? I don't think we can upgrade until this latest problem is fully resolved.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2017 17:27:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978407#M159426</guid>
      <dc:creator>MikeG15</dc:creator>
      <dc:date>2017-09-28T17:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978408#M159427</link>
      <description>&lt;P&gt;Looks like there is also a known issue with ESX and iLo 2.54/2.55. It totally kills ESX:&amp;nbsp;&lt;A href="https://robbeekmans.net/vmware/howto-workaround-fixing-hp-hosts-stuck-reboot-ilo-upgrade-showing-lost-connectivity/" target="_blank"&gt;https://robbeekmans.net/vmware/howto-workaround-fixing-hp-hosts-stuck-reboot-ilo-upgrade-showing-lost-connectivity/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2017 17:30:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978408#M159427</guid>
      <dc:creator>MikeG15</dc:creator>
      <dc:date>2017-09-28T17:30:42Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978417#M159428</link>
      <description>i think this is a different problem with sd cards only. the sd-card is "behind" ilo, if ilo reboots during update, the sd+card is unavailable during this reboot.</description>
      <pubDate>Thu, 28 Sep 2017 20:04:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978417#M159428</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2017-09-28T20:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978455#M159431</link>
      <description>&lt;P&gt;Torsten,&lt;/P&gt;&lt;P&gt;Yeah, we'd never see that particular issue as we have VM installed on local disk rather than the SD cards.&amp;nbsp; We had a few on SD, but as soon as you install a patch or two you're out of space on the SD cards.&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;</description>
      <pubDate>Fri, 29 Sep 2017 13:21:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6978455#M159431</guid>
      <dc:creator>Ken Krubsack</dc:creator>
      <dc:date>2017-09-29T13:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6995375#M160912</link>
      <description>&lt;P&gt;I have upgraded 1.20 to 2.55 and all good no issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 18:07:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6995375#M160912</guid>
      <dc:creator>tux1431</dc:creator>
      <dc:date>2018-01-30T18:07:24Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6995461#M160935</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Please look at following customer advisory&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00026427en_us" target="_blank"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00026427en_us&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2018 01:10:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/6995461#M160935</guid>
      <dc:creator>smokin901</dc:creator>
      <dc:date>2018-01-31T01:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/7015621#M163612</link>
      <description>&lt;P&gt;Did it require any reboot?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 05:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/7015621#M163612</guid>
      <dc:creator>Prashant_7666</dc:creator>
      <dc:date>2018-08-22T05:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: iLO 2.5 upgrade to 2.55 issues</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/7015624#M163613</link>
      <description>as long as you dont run esx from internal sd card - no.</description>
      <pubDate>Wed, 22 Aug 2018 06:09:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo-2-5-upgrade-to-2-55-issues/m-p/7015624#M163613</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2018-08-22T06:09:00Z</dc:date>
    </item>
  </channel>
</rss>

