RE: Upgrade HMC 7042CR8 from 8.8.3 to 8.8.4 and 8286 41A&42A from FW830.10 (68) to FW 840_056

Upgraded 7042 CR6 from 8820 to 8824 using iso download burned to DVD.

http://www-912.ibm.com/systems/electronic/support/s_dir/SLKBase.nsf/DocNumber/762471778

Upgrade was smooth, but long, about 1 hour.
Note 1: During the upgrade to V8 R8.4.0, the local session will display a list of environment variables for hmcmanager (last line is "END ENV" ) for as long as 20 to 40 minutes without a screen change. Do not reboot HMC or power off; wait for the upgrade to complete.

Applied both MH01560 and MH01588 from iso downloads copied to USB drive.
HMC IPL is about 15 minutes per each update.

http://www-912.ibm.com/s_dir/SLKBase.nsf/82a337f562831d2986256839005c83c7/e4bed409d19db2aa86257f08007b0f70?OpenDocument

mount /media/sdb1
updhmc -t usb -f /media/sdb1/MH01560.iso

HMC did not auto restart per IBM tech doc 762485069.
Note - the -r was missing from this in the USB portion, IBM tech doc 762485069 is being updated to include the -r.

I did have HMC service events during this process.
E35F0012 - SRC messages you received are related to scheduled operations and Electronic Service Agent transmissions being out of sync while the upgrade is performed
E3550101 - Licensed Internal Code failure on the Hardware Management Console (HMC).
E3550103 - Licensed Internal Code failure on the Hardware Management Console (HMC).
E3550996 - Licensed Internal Code failure on the Hardware Management Console (HMC).
E35F0012 - Licensed Internal Code failure on the Hardware Management Console (HMC).
B3030001 - The communication link between the service processor and the Hardware Management Console (HMC) failed.
B3020001 - Management Console (MC) RMC connection to partition monitoring fault
B3030001 - The communication link between the service processor and the Hardware Management Console (HMC) failed.

From IBM support:

"I found the SRC messages you received are related to scheduled operations and Electronic Service Agent transmissions being out of sync while the upgrade is performed. These issues should have automatically been corrected but if they persist we will want to get the call home data. Please monitor for a few days and let us know if you see any more instances of these messages."

The hardest part was finding these tech docs.
When I started this upgrade process the HMC Code Updates under Recommended Fixes was not up to date, since has been updated.

Also, IBM has a new HMC link for upgrades - Fix Level Recommendation Tool

https://www14.software.ibm.com/webapp/set2/flrt/home

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 15, 2016 1:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Upgrade HMC 7042CR8 from 8.8.3 to 8.8.4 and 8286 41A&42A from FW830.10 (68) to FW 840_056

Did second hmc.
Used putty client to get session.

saveupgdata -r diskusb
Ran in under a minute.

getupgfiles -h public.dhe.ibm.com -u anonymous --passwd anonymous -d
/software/server/hmc/network/v8840
9:27:45 - 9:43 ran errand, still running 9:53 returned from errand and it was done.

chhmc -c altdiskboot -s enable --mode upgrade hmcshutdown -r -t now This ran from 11:02~11:45

updhmc -t ftp -h public.dhe.ibm.com -u anonymous --passwd anonymous -f /software/server/hmc/fixes/MH01560.iso
12:05~12:23

hmcshutdown -r -t now
12:25~12:44

updhmc -t ftp -h public.dhe.ibm.com -u anonymous --passwd anonymous -f /software/server/hmc/fixes/MH01588.iso
12:49~12:57

hmcshutdown -r -t now
lost track of time. I remember it being close to the last reboot.

Started sessions. Seems to work.

The first reboot after the getupgfiles may initiate a hardware service call. It did on both of my hmc upgrades.


Rob Berendt