Blade reported an abnormally low power requirement

[Frederic Martin GSP]

We have 2 c7000 enclosures in production.
Today we received an alert with
"EVENT (24 Jul 08:06): Enclosure Status has changed to: Degraded"

and after, we received an alert for each blade inside the enclosure with
"EVENT (24 Jul 08:09): Blade reported an abnormally low power requirement."

And after some time, we received last mail with
"EVENT (24 Jul 08:09): Enclosure Status has changed to: OK"

We check, there is no log in OA adminsitration website

The iLO Firmware Version is 1.78 Jun 10 2009
The Power Management Controller Version is 3.4

[Michal Kapalka (mikap)]

hi,

check the official manual :

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00705292/c00705292.pdf

and search in the document :

Low Power Request

mikap

[Frederic Martin GSP]

Hi,

I already check before posting here, and it says
"The blade reported an abnormally low power requirement. The blade was powered
off and did not release all of the power. The blade will continue to operate properly
but a service representative needs to be contacted to correct the issue."

But no blade were powered off, and I still have received theses messages

[Michal Kapalka (mikap)]

hi,

thats strange, if i would be in your situation would call to HP support, to check if its some bug in the firmware.

mikap

[Aiman]

I face the same issue; any advice was received for this case??!!

[Torsten.]

You should update iLO (to 2.00) first. Check the OA firmware too.

[Aiman]

We made frimware upgarde a month back:
Product Name ProLiant BL460c G1
ROM Version I15 07/10/2009
Model iLO2
Firmware Version 2.00 Jun 21 2010

Device Name BladeSystem c7000 Onboard Administrator
Firmware Version 3.00 Mar 19 2010

the error is old one and still coming

[Michal Kapalka (mikap)]

hi,

if the error still present after formware update, open a HW call directly in HP if you have support, it could be made by the phone call or on the ITRC ==> Support Case Manager,
we always do it this way.

If the support will find out they will forward it to the higher level and maybe also to same LAB.

mikap

[Aiman]

Thank you Michal, I will update this case when reaching root cause.

[Server-Support]

Hi @Aiman,

How did you go with the software update ?

I'm also having this problem as well this morning:

Enclosure, "..", has detected the that Blade ".." has reported an abnormally low power requirement

Here's the software version:

ROM Version A26 11/02/2014
iLO4 Firmware Version 2.30 Aug 19 2015

[Server-Support]

@Frederic Martin GSP so how did you go with this issue ?

I'm still receiving this false alert once in a month at least.

[RICHARD JR. CUSSON]

Hi,

For me, reset the active OA solved the problem. Probably the OA was not communicating properly with the blade.

I hope it will solve the problem on your side.

Richard

[Server-Support]

@RICHARD JR. CUSSON so how do we reset the OA without causing massive production outage ?

For me, the suggested course of action by HPE team was performing the firmware update of the below:

HPE BL 465c G8 BIOS ROM version to A26 – 2016.03.07

HPE BL 465c G8 iLO version to iLO4 – 2.40

[RICHARD JR. CUSSON]

We have several C7000 enclosure with onboard administrator and virtual connect. The onboard administrator and virtual connect modules are redudant in each enclosure (active and stanby modules). This is the key and it is essential if you want to avoid massive production outage.

All our C7000 enclosures are at version 4.50. 

Our BL-460c Gen8 servers are at bios version I31 06/01/2015.

Our ILO 4 at version 2.30 and our virtual connect at version 4.45.

For me, a reset of the active OA worked. And I'm not talking about a reset to factory default, of course.

Maybe for those who have the problem, another solution is more appropriate.

I hope these clarifications will help. =)

Richard

[Server-Support]

@RICHARD JR. CUSSON thanks for the clarification.

C7000 enclosure firmware on version 4.40 Dec 08 2014
ProLiant BL465c Gen8 BIOS is on A26 11/02/2014 with the iLO4 firmware 2.30 Aug 19 2015 --> this compnent have all been updated to the above recomendation as per HPE recipe http://vibsdepot.hpe.com/hpq/recipes/HPE-VMware-Recipe.pdf 

While our Virtual Connect module is set as Active/Passive HP VC Flex-10 Enet Module running firmware 4.01. The reason I stay on this firmware is because, it is too much of risk impacting the production server when updating the virtual connect module for no obvious benefits.

Are you running VMware ESXi ?, my impacted Blade is running ESXi 5.1U3.

[wilysanz]

Another test, will be, that blade shutdown and remove out from chassis around 20 or 30 seconds, then re-enter the blade into chasis and wait to you can turn on the same. This issue is sourced because the blade don't receive the adequate energy or is there any variation that cause this reation in the blade. About it last, sould review carefully the electrical conections.

This procedure has allowed me keep the blade with out this message during 3 month at least.