<?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: ILO2 Problem in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344238#M87412</link>
    <description>all,&lt;BR /&gt;&lt;BR /&gt;please include as many details you can, like when started to happen, what was change prior to the error (if any), screen shoots, version being used and exact error messages so I can go to the lab and re-create the issue&lt;BR /&gt;&lt;BR /&gt;thanks</description>
    <pubDate>Wed, 18 Mar 2009 13:07:14 GMT</pubDate>
    <dc:creator>juan quesada</dc:creator>
    <dc:date>2009-03-18T13:07:14Z</dc:date>
    <item>
      <title>ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344234#M87408</link>
      <description>Sytem information -&amp;gt; Power Section gives the following error.&lt;BR /&gt;&lt;BR /&gt;Error reading power values from microcontroller. No valid reading can be gathered. &lt;BR /&gt;&lt;BR /&gt;License Type: iLO 2 Advanced  &lt;BR /&gt;iLO 2 Firmware Version:  1.70   12/02/2008 &lt;BR /&gt;&lt;BR /&gt;Waiting for your help.</description>
      <pubDate>Sat, 24 Jan 2009 13:27:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344234#M87408</guid>
      <dc:creator>Ali VARGONEN</dc:creator>
      <dc:date>2009-01-24T13:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344235#M87409</link>
      <description>Was it after the ILO2 upgrade to 1.70 this appeared? There is a new function with the ILO2 1.70 that's called Power capping and a new licens model.&lt;BR /&gt;&lt;BR /&gt;Also for full support with power capping you need to upgrade your bios on the server.&lt;BR /&gt;&lt;BR /&gt;I'm just guessing here but maybe the have altered the power information gathering with 1.70 that need the new bios..</description>
      <pubDate>Sat, 24 Jan 2009 15:43:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344235#M87409</guid>
      <dc:creator>Cederberg</dc:creator>
      <dc:date>2009-01-24T15:43:44Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344236#M87410</link>
      <description>Is was shown before bu disappered. I am using the latests versions.</description>
      <pubDate>Tue, 27 Jan 2009 12:18:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344236#M87410</guid>
      <dc:creator>Ali VARGONEN</dc:creator>
      <dc:date>2009-01-27T12:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344237#M87411</link>
      <description>I'm also seeing this problem on a Dl380 G5 with the latest ROM (2008.11.01).  All was well with an old iLO 2.?? with the advanced licence installed, after upgrading to iLO 1.70 I now see the same error described above.&lt;BR /&gt;&lt;BR /&gt;I've now upgraded all firmware in the box to the latest and am still seeing the error following multiple server and iLO reboots.&lt;BR /&gt;&lt;BR /&gt;Logging power usage is something we are required to do, so this is BAD.&lt;BR /&gt;&lt;BR /&gt;A prompt solution to this problem would be greatly appreciated.</description>
      <pubDate>Wed, 18 Mar 2009 12:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344237#M87411</guid>
      <dc:creator>Ian Y</dc:creator>
      <dc:date>2009-03-18T12:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344238#M87412</link>
      <description>all,&lt;BR /&gt;&lt;BR /&gt;please include as many details you can, like when started to happen, what was change prior to the error (if any), screen shoots, version being used and exact error messages so I can go to the lab and re-create the issue&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Wed, 18 Mar 2009 13:07:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344238#M87412</guid>
      <dc:creator>juan quesada</dc:creator>
      <dc:date>2009-03-18T13:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344239#M87413</link>
      <description>The problem started immediately following upgrade from iLO 1.2 to iLO 1.70&lt;BR /&gt;&lt;BR /&gt;RIBCL power queries return:&lt;BR /&gt;&lt;GET_POWER_READINGS&gt;&lt;BR /&gt;&lt;PRESENT_POWER_READING value="0" unit="Watts"&gt;&lt;/PRESENT_POWER_READING&gt;&lt;BR /&gt;&lt;AVERAGE_POWER_READING value="0" unit="Watts"&gt;&lt;/AVERAGE_POWER_READING&gt;&lt;BR /&gt;&lt;MAXIMUM_POWER_READING value="0" unit="Watts"&gt;&lt;/MAXIMUM_POWER_READING&gt;&lt;BR /&gt;&lt;MINIMUM_POWER_READING value="0" unit="Watts"&gt;&lt;/MINIMUM_POWER_READING&gt;&lt;BR /&gt;&lt;/GET_POWER_READINGS&gt;&lt;BR /&gt;&lt;BR /&gt;Administration -&amp;gt; Licencing section in iLO reports:&lt;BR /&gt;"iLO 2 Advanced features have been activated."</description>
      <pubDate>Wed, 18 Mar 2009 13:14:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344239#M87413</guid>
      <dc:creator>Ian Y</dc:creator>
      <dc:date>2009-03-18T13:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344240#M87414</link>
      <description>After leaving the server alone for about an hour the error has gone away and I'm now seeing power readings and am able to get sensible readings via RIBCL as well?!&lt;BR /&gt;&lt;BR /&gt;I've not seen this kind of behaviour before, but I'm just happy it's working!</description>
      <pubDate>Wed, 18 Mar 2009 15:46:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344240#M87414</guid>
      <dc:creator>Ian Y</dc:creator>
      <dc:date>2009-03-18T15:46:20Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344241#M87415</link>
      <description>???</description>
      <pubDate>Sat, 21 Mar 2009 09:41:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344241#M87415</guid>
      <dc:creator>zm27980</dc:creator>
      <dc:date>2009-03-21T09:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344242#M87416</link>
      <description>I just recently upgraded my DL380 G5 system firmware to P56 (11/01/2008) and Power Meter worked great all the time.  Only after upgrading to the latest iLO 2 firmware did I also run into the above error message.&lt;BR /&gt;&lt;BR /&gt;My server has been operating for more than 24 hours with the new iLO2 1.70 (12/02/2008) firmware and I still get this error message.&lt;BR /&gt;&lt;BR /&gt;Can we get some help out here?  My iLO 2 advanced features are activated, but I can't use them to their full potential without power readings!&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;--Chris</description>
      <pubDate>Tue, 21 Apr 2009 12:13:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344242#M87416</guid>
      <dc:creator>Christopher D</dc:creator>
      <dc:date>2009-04-21T12:13:02Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344243#M87417</link>
      <description>Did you try powering the server off and then unplugging the power cables for a good 5 minutes?&lt;BR /&gt;&lt;BR /&gt;In a related thread once I got this fixed I was then getting invalid power readings (80 watts instead of around 300), however HP sent me a new version of iLO (1.75) which seems to have fixed the problem.</description>
      <pubDate>Tue, 21 Apr 2009 12:20:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344243#M87417</guid>
      <dc:creator>Ian Y</dc:creator>
      <dc:date>2009-04-21T12:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: ILO2 Problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344244#M87418</link>
      <description>I downgraded iLO 2 firmware to version 1.61 (B) as provided on the Drivers/Download page - now I'm getting this message:&lt;BR /&gt;&lt;BR /&gt;Present power reading: 0 Watts at 09:53:36, 04/21/2009&lt;BR /&gt;&lt;BR /&gt;Powering down and unplugging a server in a remote datacenter is highly inconvenient since it must be coordinated with remote hands assistance that's likely to cost me more than $100 per hour for assistance during an off-peak time so that it's convenient for my customers - not to mention annoying my wife.  This is precisely why iLO was invented and why I spent the money for it.  HP needs to provide a way to remotely reset whatever is in my power supply which has stopped responding to power management calls.&lt;BR /&gt;&lt;BR /&gt;--Chris</description>
      <pubDate>Tue, 21 Apr 2009 12:59:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ilo2-problem/m-p/4344244#M87418</guid>
      <dc:creator>Christopher D</dc:creator>
      <dc:date>2009-04-21T12:59:49Z</dc:date>
    </item>
  </channel>
</rss>

