Re: HMC firmware update policy

[Larry Bolhuis <lbolhuis@xxxxxxxxxx>]

A few things right off:

1) If you don't keep your HMC code up to date a PTF in the partition 
could update the code in the FSP leaving it disconnected due to version 
mismatch. This is a *LANDMINE.

2) With HMC updates you can do on the fly fixes, known as non-disruptive 
to your FSP while the system stays running.

3) With HMC updates you can have the "T" (temporary) and "P" permanent 
sides of the FSP at different levels. Only once you decide the T level 
is good and you want to keep it do you Accept it (effectively a 
Permanent Apply) and copy that code to the "P" side.

4) You better control when these things happen. You could do a PTF that 
loads firmware and bounce the machine for a quick IPL but find out that 
the thing is doing a pair of Deep IPLs to do the firmware fix and your 
downtime is extended by 30 minutes or more.

Yes it sounds like a simple thing but if you have an HMC, I would 
certainly leverage it.

 - Larry

MKirkpatrick@xxxxxxxxxxxxxxxxx wrote:
> We have an HMC on our 9406-520.  We have only one partition (no LPARs) and 
> will never have any others.  The firmware update policy is set to HMC 
> managed.  This is how it was set up by the BP during the system 
> installation.  Why do I care?  It seems that it would be much easier for 
> me to have firmware updates managed by the OS through the PTF process 
> instead of messing with the HMC.  What am I missing?  Thanks.
>