One thing I've noticed for both of you gentlemen is the following:
Firmware update policy . . . . . . . . . . . . . . : *HMC
If you have an HMC then your policy SHOULD be this. To do otherwise is to risk your HMC code becoming incompatible with your firmware.
So you are good.
Armed with this information then you need to follow this procedure:
On your HMC:
Pick Systems Management. Pick your system (NOT your lpar).
Actions, Updates, Change licensed internal code, for the current release.
"Select advanced features"
Accept - Copy Temporary to Permanent
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul via MIDRANGE-L
Sent: Monday, February 25, 2019 11:58 AM
To: 'midrange-l@xxxxxxxxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: Perm Apply of Firmware....
Andrew,
I just applied VL910_122 FW910.20 MH01799 firware.
I did a power down of the server to apply the "disruptive" firmware.
However, I'm not sure if they applied.
This is my first firmware apply on P9 and 7063-CR1.
Did the process change for applying "disruptive" firmware?
Service partition . . . . . . . . . . . . . . . . : No
Firmware update policy . . . . . . . . . . . . . . : *HMC
Server IPL source . . . . . . . . . . . . . . . . : Temporary
Firmware product ID/release . . . . . . . . . . . : 5733909 V1R1M0
Update access key expiration date . . . . . . . . : 01/16/22
---Server firmware----
Fix PTF
Copy pack ID
*ACTIVE VL910_122 MH01799 FW910.20
*TEMP VL910_122 MH01799 FW910.20
*PERM VL910_115 MH01798 FW910.11
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Andrew Lopez (SXS US)
Sent: Monday, February 25, 2019 11:44 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Perm Apply of Firmware....
There's plenty of comments in the archives (and on-line) about the need for a power down being needed when applying disruptive firmware upgrades from an HMC. I may be missing it, but now that I have done that, and I have the new firmware on both the *ACTIVE and *TEMP copies, will I need that deep reboot for the *PERM apply?
For the record, our DSPFMWSTS on the sole partition shows:
Service Partition Yes
Firmware update policy *HMC
Server IPL source *Temporary
Firmware product ID/Release 5733909 V1R1M0
Update access key expiration date 07/21/21
*ACTIVE VL910_122 FW910.20 MH01799
*TEMP VL910_122 FW910.20 MH01799
*PERM VL910_073 FW910.00 MH01712
Fix pack, PTF ID and Update Status all show as *NONE/None.
I assume that using the green screen to *PERM apply all PTFs won't be enough to get the firmware copied to *PERM at the next IPL. What I can't tell is if the *PERM apply is as disruptive as the *TEMP apply.
_____________________________________________________________________
Spirax-Sarco Engineering Plc. This e-mail has been scanned for viruses by Cisco Cloud Email Security.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
