DL380p Gen8 Unexpected Shutdown

[technologist36]

Dears,

I am new to HP and i am facing up to 7 unexpected shutdowns a day. I searched the web and found it is something to do with CPLD version earlier than version 32. I downloaded CPLD version 32 for Windows 64-bit and placed it in a USB key along with SPP using USB key creator. But before i boot from the USB key, i want first to check if CPLD version is causing the shutdowns.

Which tool/utility to use to check the system logs? .. I read about iLO and Insight Diag but not sure which one to start with first.

One last question, do i need to install SPP every release to fix issues? .... Sadly, the firmwares haven't been updated for years, may this be what causes the shutdown problem?

Appreciate your help

[Torsten.]

It is always a good idea to keep the firmware up to date.

I would create an USB stick from SPP 2015.06 using the USB creator tool inside the ISO (version 2.0) and boot from it.

Connect to ILO web page and inspect the IML - any related messages there?

Add the following file to hp/swpackages on the USB stick:

ftp://ftp.hp.com/pub/softlib2/software1/sc-linux-fw/p872484366/v87741/ 

see

http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c04148912&utm_source=affiliate&utm_medium=cpa&utm_campaign=adgoal+DE+%28ehem.+oxono%29&utm_content=0&jumpid=af_zky3rxgb21/site:adgoal+DE+%28ehem.+oxono%29

[technologist36]

IML reported "POST Error: 1615 Power Supply Input Failure in Bay 1"

Also, checked the CPLD version and found that it is already on version 32 (CPLD PAL0: 0x32)

Please check the firmware info in the attached screenshot.

[Torsten.]

Since the installed versions are really old, I would first create the SPP USB stick and boot from in order to update the firmware.

http://www.hp.com/go/spp

[technologist36]

The USB utility stopped working whenever i select the SPP ISO image and the USB key as the target. I've tried on 7 machines and the same frustrating windows error, I cannot create it.

Is there any alternatives?

[Torsten.]

Did you use version 2 from the ISO file? Older versions will not work.

[technologist36]

Sorry, didn't get what you mean. Did you mean the version of the utility? i am using 1.7

[Torsten.]

This is the problem. It will fail because the ISO is too large.

Inside the ISO in USB directory you can find version 2.0, this will work.

[technologist36]

WOW, you are right. It is now being created. Thank you so much for that. Will let you know when i boot from the key and post the results. :))))

[technologist36]

Ok, i booted sucessfully and deployed SPP components. After deployment, the SPP freezes at "Please Wait, analyzing the system....".

Is this normal?

[technologist36]

Firemware are updated and server still shuts down.

Any Clue?

[MohammedAzas]

Am also getting the same issue, from abt 3hrs it is showing the same screen "Please wait,anasyzing system". any clue how u have resolved.

[Van Geem]

Hi,

I am facing this "please wait, anaylising system" issue while upgrading to SPP2016.04.0 on a Proliant DL380p Gen8. Did you ever managed to resolve this issue? Is it just a metter of waiting long enough?

Cheers

[Torsten.]

Booted from SPP?

This step normally takes ~5 min.

Bad image on that USB device?

[Corbin OReilly]

Hello. I have a DL360P Gen8 and after 1 hour it still says, "Please wait, analyzing system ...." Did you ever get past this point? Did you have to wait a long time for it to complete? Thanks for the help

[Jimmy Vance]

---

@Corbin OReilly wrote:

Hello. I have a DL360P Gen8 and after 1 hour it still says, "Please wait, analyzing system ...." Did you ever get past this point? Did you have to wait a long time for it to complete? Thanks for the help

---

I'd say the system is hung if it has been likethat for an hour.  Assuming you booted from USB media. How did you create the USB key?  Try using the USB key utility that is included with the ISO image

[Corbin OReilly]

Hi. I downloaded and installed the HPE USB Key Utility v2.1 from the HP website. I then downloaded the Proliant SPP iso. I installed the utility, ran it, pointed to the SPP iso, it created successfully then I booted the server with the USB Key. Chose Automatic and it successfully upgraded the BIOS, RAID Controller, iLO, etc then went to the "Please wait, analyzing system" screen where it has been sitting for over 2 hours. Do you think it is safe to power off the server, boot up with the USB Key again, choose Automatic and see if it applies any more updates? I didn't see it upgrade the firmware on the individual hard drives which I think are also out of date. Thanks.

[Jimmy Vance]

v2.1 is the version that is included on the current SPP media. At this point I don't think you have any other option but to reboot and run the SPP again. I'd run it in manual mode so you can see what firmware versions are installed

[Threonine]

I've had this too on a DL380 G7 and a DL380p Gen8.  Not too fun when you've got an entire customer environment shut down and waiting for it to finish and it never does.  The first time I had this I waited half an hour and finally rebooted and found the firmware was all up to date.  The latest one I've waited over an hour with no progress.  The SPP is running Mozilla Firefox for Linux, and I was hoping I could force the browser to just reload the page and see if anything changes, but the keyboard shortcut doesn't work and there's no way to do it with the mouse.  The only thing I can get it to do is move the window around (Alt+F11).  This is happening on SPP 2016.10.0.  What's going on with this, HP?  See screenshot.

Permanent hang

[Corbin OReilly]

I powered off the server, booted with the USB drive again and all firmware was up-to-date. My server is working fine. Thanks for the help.

[iisti]

I had same problem as Threonine with ProLiant DL360e Gen8. I used HPE USB Key Utility 2.1 to make bootable USB key of SPP 2016.10.0 iso. I  booted with the key and used Automatic mode to update the firmawres. After updating the SPP stuck to "Please wait, analyzing system...." screen. I waited about 45 mins and booted the server forcefully. During booting I could see that iLO was updated.

Now ran the SPP in Interactive mode. All the other things were updated expect Power management. I updated that and rebooted again to SPP in Interactive mode. Now SPP showed that everything is up to date.

Originally I started to update the firmware because the ESXi was complaining of loosing connect to /bootbank

[Fritsch James]

I recommend to always use interactive firmware update. Automatic update does behave strange sometimes. The "Please wait, analyzing system" indeed lasts for quite a long time in soime configurations - just be patient. It shouldn't take hours though.

[pcTechs]

Hold CTRL+ALT+SysRq,

tap R, E, I, S, U, ......  (watch the options on screen)

once B is pressed, the system will immediately reBoot.

B

Raising Elephants Is So Utterly Boring.

[clusterman]

Sorry to dredge up an old thread, but I had the same problem with an old used dl380p gen8. It had iLO 4 v1.4 and Intelligent Provisioning v1.3.  I used an SPP 2017.04.0 iso on a HP usb utility created usb drive to update all the firmware in one go, including ilo 4 to v2.55. I used automatic update, and it seemed to install everything, but on reboot, it hung on the same analyzing system message that everyone else was having. I tried force rebooting to the SPP, and the automatic update hung on analyzing again. I couldn't access ilo 4 through the web interface.

I updated Intelligent Provisioning, and could access ilo 4 through that, but no amount of resetting or setting changes seemed to help. I could also access iLO 4 configurator through hitting F8 during boot, but no matter what network settings I used, I couldn't access ilo 4 through the web interface. Pulling power cords and rebooting also didn't help.

I then hit reset to factory default in the ilo 4 configurator (F8 during boot), noted the ipv6 address that showed up during boot, and tried logging in with that, which worked. I then booted into the SPP usb interactive mode, went to firmware, and it showed everything was updated. 

I think the key here is to somehow force a reset of ilo 4/the embedded flash, and resetting to factory defaults through the configurator (F8 at boot) seemed to do the trick. There's probably a script way of doing it, too.

I could then use the web interface to change the ipv4 settings, do a reset of ilo 4, and then use the web interface with the static ipv4 address to log in again.