Support Pack for Proliant Firmware Update over PXE

[vuster]

Great work. Thanks to smart guys like you it makes us dumb guys look good.

[shocko]

Thank you to Gerardo_Arceri,

I was able to get it booting using your config line. I was missing the following params:

• pci=bfsort
• iappend=2

I wish HP would document this! Their documentation points to PXE booting the FW CD v 9.10 for some reason.

[Peter Capriccio]

Gerardo,

Thanks for the patches and for the ipappend idea -- nice!

One thing, however, is that I think that the module list in your "initrd.functions.patch" file has a typo:

  NET_MODULES="e100 e1000 e100e igb qlcnic bnx2x be2net bnx2 tg3"

Shouldn't that be "e1000e"?

Pete C.

[sascha08]

Thanks for the great Support here, i was able get it to work with nfs and cifs.

This post helped a lot.

But we use windows server as pxe/dhcp so it better to use cifs.

So i tried around with the mount_url.sh in /sbin to solve the problem with colon in username.

You can follow the instructions from the patch to unpack and repack the initrd.img with a correct mount_url.sh.

To solve the the bug with username string change in line 80 of mount_url.sh code to:

USER=${user_n_pass:0:$(($colonindex - 1))}

After that i still got an error and next guess was password line is wrong too.

I added a output line to the mount scirpt and found out that the first charackter was missing and at the end of the password was @ sign ;-(. 

To solve the bug in password string change line 82 of mount_url.sh code to:

PASSWORD=${user_n_pass:$(($colonindex)):$(($atindex- $(($colonindex+1))))}

Maybe someone who is good in scripting can add this fix to the patch here.

I'm a beginner in shell scripting ;-).

Thanks for posting the patch here and to all the other comments.

Sascha

[Gerardo_Arceri]

You're right, thanks for noticing this.
I updated the zip file with this fix.

[dcolpitts]

Peter - would you please consider sharing your "langsel.htm.wbu" here?

Thanks

dcc

[dcolpitts]

Peter - with regards to your langsel.htm.wbu, correct me if I am wrong here in what you did....

1. You mounted initrd.img to /tmp/initrd.
2. You extracted /system/squashfs.img from the ISO image.
3. Then you extracted /opt/hp/hp-phoenix/srv/www/langsel.htm from squashfs.img and saved it as /tmp/initrd/langsel.htm.wbu.
4. You edited /tmp/initrd/langsel.htm.wbu.
5. Immediately below line 13 (the entry for "HP_Localize();"), you added:
   
   

   HP_SystemCommand("bash", "-c 'export HDU_BOOTENV_SMPJTB=yes && cd /mnt/cdrom/hp/swpackages && ./hpsum'");

6. You edited /tmp/initrd/init and immediately under the command "mount_fs" (line 40), you added the following two lines:
   
   

   cp /langsel.htm.wbu "${CHROOT_DIR}"/opt/hp/hp-phoenix/srv/www/langsel.htm
   sed -i 's|/mnt/cdrom|/mnt/bootdevice|g' "${CHROOT_DIR}"/opt/hp/hp-phoenix/srv/www/langsel.htm

7. You then created a new initrd.img and use that initrd.img to boot from.

This has the effect of bypassing the language prompt and EULA and immediately starting HPSUM upon boot - or atleast in my test environment.

Correct?

dcc

[Michael Leu]

FYI: I have sent a link to this thread to the SUM guy at HP and he has forwarded it to the person responsible for the boot environment for the SPP. So hopefully that person will participate here or the fixes will be in the next official SPP.

Additional question: does adding a CPxxxxxx.scexe to the root directory of HPSUM still work for you?

I just can't seem to get it to work. The new scexe shows up in the repository contents as a unbundled component but somehow doesn't get selected during installation (the older firmware that is in the bundle gets installed). I have tried all kinds of variations of -express_install, -allow_non_bundle_components and -allow_update_to_bundle as hpsum flags...

[shocko]

Good stuff Michael,

In my opinion HP were slow to recognize what the community wanted in terms of PXE delivery of firmware/smart start/SPP. Also, when it was delivered it seemed very buggy which kind of negated it's use. I've spent hour tinkering with builds to get it working on different platforms which really defeats the purpose. Hopefully the next couple of releases will be more stable :)

[KSattler]

Have anything changed regarding to the new SPP 2012.08.0 (released on 4 Sep 2012) ?