Mx-32 - How to update System Firmware (ILOM / HC / POST / HV / OBP / GM )

Asset ID:	1-71-1981675.1
Update Date:	2018-02-01
Keywords:

Solution Type Technical Instruction Sure

Solution 1981675.1 : Mx-32 - How to update System Firmware (ILOM / HC / POST / HV / OBP / GM )

Applies to:

SPARC M5-32 - Version All Versions and later
SPARC M6-32 - Version All Versions and later
Information in this document applies to any platform.

Goal

CAP PROBLEM OVERVIEW: Procedure to update Mx-32 System Firmware

To report errors or request improvements on this procedure, please go to My Oracle Support, and put a comment on Doc ID: 1981675.1

Please be aware of:
- Bug 21120905 - Hostflash image NOT updated on powered off HOST
- Bug 21024666 - Hostflash image updated on running HOST

At this point in time the option with the lowest risk on domain outages is to upgrade SYSFW with all HOSTS stopped. If in doubt on how to proceed, contact your TSC SR owner.

Notes:

when upgrading from 9.0.2.c or earlier, all HOSTs MUST be stopped before starting upgrade
when upgrading from 9.3.0.c , ensure SP0 is the active SP before upgrading, check the patch readme for details
all the SPs and SPPs are updated at the same time from the Active SP, no specific user interaction is required to update the Standby SP and SPPs
the image for M5-32 and M6-32 is named Sun_System_Firmware-x_x_x_x-SPARC_M5-32+M6-32.pkg where x_x_x_x is the SysFW version
although upgrading System Firmware from CLI is the prefered method, it's possible to upgrade from the BUI : SP / ILOM Administration / Maintenance / Firmware Update.
to ensure the SP is fully functional, you may choose to reset the SP before starting the firmware update procedure (add approximately 25 minutes)

Before starting the firmware update procedure, obtain the latest System Firmware by downloading the appropriate patch to a location that is network-connected with the active SP unit. At the time of last modification of this document, the latest version of System Firmware is 9.6.8.b. To obtain information on what the latest version of System Firmware is, and on their patch locations, please visit "SPARC M5-32 and M6-32 Servers: Firmware Image Software Version Matrix Information (Doc ID 1540816.1)".

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED: Mx-32 Product Training/Experience

TASK COMPLEXITY: 2

TIME ESTIMATE: 120 minutes (excluding possible all domain stop/start )

FIELD ENGINEER INSTRUCTIONS

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? : n/a

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

The System Firmware procedure exclusively runs on the active SP unit:

0. optionally perform reset /SP to start with a freshly booted SP

1. for updating the firmware, you must have an administrator (a) or field engineering (s) role

2. login to the active SP, and make sure your role is correct, by running show /SP/users/<user> role

3. depending on customer preferences, stop all HOSTs prior to starting ILOM update, by running stop /Servers/PDomains/PDomain_x/HOST for each HOST

4. check and record settings of keyswitch for all HOSTS, by running show /Servers/PDomains/PDomain_x/HOST keyswitch_state for each HOST

5. to allow the system firmware to update HOST bits , set keyswitch to normal for all HOSTS, by running set /Servers/PDomains/PDomain_x/HOST keyswitch_state=normal

6. now start the System Firmware update, by running the command load -source <protocol>://<xxx.xxx.xx.xxx>/<pathname> (answer Y to preserve the configuration information):

<protocol> is the transport mechanism used, for example http
<xxx.xxx.xx.xxx> is the IP address of the host then provides the System Firmware update image file
<pathname> is the full pathname of the System Firmware update image file on host <xxx.xxx.xx.xxx>
the Active SP check the compatibility and versions for all SPs/SPPs present,
the System Firmware image is stored in SP flash,
the Standby SP gets the image from the Active, it is upgraded, resets on the new image, comes back as Standby and stops, waiting for the Active to complete flashupdate
on the console session, you would see it seating in "Waiting for Active-SP to complete flashupdate ..." until the upgrade on the Active SP has completed
each SPP now downloads the images from the Active SP and are upgraded simultaneously
if the corresponding host is running, the next version of the binaries is updated with the newly flashed copies and the system continues to use the running version. it will be updated when the host restarts
if the corresponding host is off, both the next and running version of the binaries are updated with the newly flashed copies
when completed, the Active SP requests the SPPs to reset, each SPP reboots and blocks, waiting for Active to complete flashupdate
the Active SP now updates itself and reboots on the new image
No SP role switch occurs during the upgrade process, the original active SP remains active

7. restore the keyswitch settings for all HOSTS, as found in step 4, by running set /Servers/PDomains/PDomain_x/HOST keyswitch_state=<state>

8. To determine if a HOST will have any bits updated when it is stopped and started, you can check the information in SPARC M5-32 and M6-32 Servers: Firmware Image Software Version Matrix Information (Doc ID 1540816.1):

compare the values listed for GM / Hostconfig, Hypervisor, OBP and POST, for the ILOM version currently used, and the ILOM version that will be installed
if the values are identical for both the currently used and the new ILOM firmware, a HOST stop/start will proceed as usual
in any other case, at the time a HOST is stopped and started, these bits will be updated

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

If HOSTS are stopped, make sure all HOSTS successfully get started

======================== Other info =====================

REFERENCE INFORMATION:

Oracle ILOM Administrator's Guide for Configuration and Maintenance Firmware Release 3.2.x, http://docs.oracle.com/cd/E37444_01/pdf/E37446.pdf
SPARC M5-32 and SPARC M6-32 Servers Administration Guide, http://docs.oracle.com/cd/E24355_01/pdf/E41216.pdf

References

<NOTE:1542610.1> - SPARC Mx-32, M7 and M8 Servers: Firmware FAQ
<NOTE:1540816.1> - SPARC M5-32 and M6-32 Servers: Firmware Image Software Version Matrix Information

Attachments

This solution has no attachment