SUM, SPP and Version Control

[Ian Kirvell]

Hi all!

I'm looking to clarify exactly what I need to be using to help keep our Proliant estate up to date from an HP software/firmware perspective.

This time last year I was using Proliant Support Packs (PSPs) that were either manually uploaded from a disk, or more likely automatically downloaded by the Version Control Repoisitory Manager on my SIM 6.3 server.

As VCRM seems completely flaky and generally stops working once it has created an index file too big for it parse, what should I now be doing?

From what I understand, I now download a "Service Pack for Proliant" from HP manually, and use it to scan servers to see what needs updating? Is this supposed to replace the Version Control Manager? Is SUM not available as a seperate download for managing our server estate?

Thanks for any clarification

[anttipennanen]

The firmware update of HP has always been a mess and now it's even getting messier. I just installed some new blades to our chassis. That took 10 minutes in total. Now I have been trying to find out for 5 HOURS how to find the latest firmware 3.55 for onboard administrator. I downloaded SUM, I searched the web, tried to understand HP website (which by the way is most horrible website ever created). I know that there are people trying to make things better but this is not the way. I'm seriously thinking of moving to Dell blades because they have implemented the firmware update tool straight to the blade management. And no, SUM doesn't work, it connects to OA but doesn't do anything. And I cannot (I'm too lazy to read all the readme files that are kilometers long, sorry) find the correct .bin file to upload it directly to OA by browser. I just cannot understand how this can be so difficult. HP, wake up!

[Goutham_Sabala]

I know it gets messy sometimes, here is the link to 3.55 bin file,

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=3188465&prodNameId=3188475&swEnvOID=1005&swLang=8&mode=2&taskId=135&swItem=MTX-43b201adeda84695aecedcebe3

All I did was to search for onboard administrator , hope this link helped