Below two links are included in my HMC update instructions.
Below are my notes/instructions from last upgrade
HMC firmware updates
Download from fix central HMC Firmware to either PC or shared drive.
Then log into BMC,
BMC update, and you can browse to where ever this was downloaded.
PNOR update, and you can browse to where ever this was downloaded.
Follow the update wizard, fairly quick.
HMC code updates.
Log into HMC,
Reboot HMC if not done for a while.
Backup Management Console data and Save Upgrade data before each, fix, update, etc
Update the internal code of the management console
Updates and/or fixes can be downloaded directly from IBM site, only changing the remote directory, either updates or fixes.
Updates are a sub release update.
Fixes are MH PTFs.
Each download / install can be 1 to 2 hours
Reboot HMC after each fix/update, etc
Remote Server: public.dhe.ibm.com
User ID: anonymous
Password: [your email address]
Remote directory: /software/server/hmc/updates or fixes
Save Upgrade Data to Pencor05 IFS instead of USB
Either via HMC command line or HMC GUI
Remote Server IP of IBM I LPAR
Remote Directory /HMC
HMC code update to new version,
downloaded from a different site using getupgiles using a putty session on the HMC.
This download can take 2 hours, be patient.
hscroot@hmcwho:~> getupgfiles -h public.dhe.ibm.com -u anonymous --passwd anonymous -d /software/server/hmc/network/v950/ppc
Fetching network installation images../
Using a 2nd putty session, you can monitor the download with
while true; do ls -l /dump/efix ; sleep 30; done
Set the HMC to do the next reboot from the special location on the hard drive where the downloaded V9 files are stored by typing the following command:
chhmc -c altdiskboot -s enable --mode upgrade
Reboot the HMC
Upgrade 9009-42A firmware to same release or new release
System saves should be done on all LPARs
Check firmware compatibility chart/link
All LPARs must be shutdown if pervasive
Log into HMC,
Reboot HMC if not done for while.
Change license Internal code to same release/new release.
Follow the wizard, firmware will be download, installed, applied all via the wizard.
FSP, flexible service processor will be rebooted.
Allow 45 minutes minimum for entire process.
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Pete Helgren
Sent: Thursday, December 30, 2021 10:20 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: HMC V9 vs V10, Was: Bringing IBM i up to the "latest" OS patches
In my case, there isn't much customization at all. I am still relatively new to the HMC so I use it sparingly. So, if I understand you correctly, just creating a new VMWare instance using the provided vHMC image would be relatively easy? I would just have to use the correct network settings so it can find my existing partitions (2 - 1 IBMi and 1 Linux) ?
Right now my biggest question is the install media for an upgrade vs update. I can find the install image (iso) to update the current vHMC to the latest v9r1 fix level. But I can't seem to find an iso that is an "upgrade" from v9r1 to v9r2. I can find VMWare images for v9r2 and also can find an "update" image to take an existing v9r2 to the latest fix levels. But I haven't found "upgrade" images for v9r1 to v9r2.
Maybe I'll try the VMWare image and see if I can get it connected and working.....
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Microsoft Certified: Azure Fundamentals
Twitter - Sys_i_Geek IBM_i_Geek
On 12/30/2021 9:01 AM, Roberto José Etcheverry Romero wrote:
IMHO, if the target HMC version supports your hardware and firmware
(v10 supports P10, P9 and P8) I would see no problem in moving to
that. And unless you have a lot of customization on the HMC (users,
groups, permissions, that kind of stuff) you could just spin up new
HMCs and move the machines to them.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.