BladeSystem Server Blades
Showing results for 
Search instead for 
Did you mean: 

Patching a enclosure using HPSUM or the old fashioned way?

Ralf Seefeldt
Valued Contributor

Patching a enclosure using HPSUM or the old fashioned way?

Hi all,

I have a customer, that runs two C3000 Enclosures with 7 BL460c G6 Servers each. The servers run RedHat or ESX.
We have to patch this environment (BIOS, ILO, OA, internal Disks, internal NICs, internal RAID controller, ...) The systems are some 4 years old.
It is requested to apply only those patches, that are absolutely required, which raises the questions, which of the 500 Patches listed by HPSUM are required and which are dependdnt on each other?

All patched servers will unmount all external disks and not run any application during all patchtasks.
In addition, there are two MSAs connected, which have to be patched too. Some of the MSA Disks will be patched too, some will not be patched as they are not in our responsibility.
The LAN Switches in the Enclosure will be patched by someone else prior to our patchsessions. They are not in our responsibility.
The FC Switches seem to be up to date.
RedHat and ESX will not be touched.
Two servers in each Enclosure are not in our responsibility and will not be touched.
SMH is not working right now. It seems to require some patches.
Not all servers can see each other through the lan as there are blocked routes.

The Environment holds some testservers, which should be patched remotely in a first step.
The productive servers and everything belonging to the enclosure and MSA will patched in a second (and probably third) session.

Now, I got two different advices from HP:

1) manually install several patches on the servers / on the enclosure in a distinct order which updates the Environment step by step from the oldest firmware to a up-to-date release.

2) use HPSUM and do all updates in one step.

Which one will be the recomended way to patch the systems?

Thank you for your support.
Any help will be greately appreciated.

The present status is:

System ROM                I24 2009.10.01  through I24 2011.05.05
FW OA                    3.00 Mar 19 2010
FW ILO                    1.81 through 2.07
Array Controler    P410i            2.74 through 3.52
NC532i Dual Port 10GbE Multifunction BL-C Adapter    Bootcode 5.0.11 through 5.2.7;  
ISCSI 3.1.5 through 4.2.10
NC326m PCIe Dual Port Adapter        Bootcode 111A5
 through 201A4; ROM 603A7 through 610A7

FW SAN Switch                7.0.0a
FW Ventilator                2.3.4
BladeSystem c3000 Insight Display    2.5.3
c3000 Tray w. embedded DDR2 OA        2.9
HBA FW                    1.11a5  NOT SCEDULED FOR UPDATE



P.S. This thread has been moved BladeSystem  > Management Software to HP BladeSystem Server Blades. -HP Forum Moderator