SPARC M7-16
 
SPARC M8-8
 
SPARC M7-8
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
 

In this Document

Goal

Solution

References

Applies to:

Goal

CAP PROBLEM OVERVIEW: How to update System firmware

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

*********************************************************************

Before starting the firmware update procedure, obtain the latest SysFW image by downloading the appropriate patch to a location that is network-connected with the Active SP unit.  See Doc ID 1967048.1

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED: M8-8 / M7-8 / M7-16 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 upgrade procedure exclusively runs on the Active SP unit:

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 business need, stop all HOSTs prior to starting System Firmware update, by running stop /Servers/PDomains/PDomain_x/HOST for each HOST
    See 'Is it possible to upgrade/downgrade firmware while the Hosts are running Solaris ?'  within the Firmware FAQ Doc ID 1542610.1

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 System Firmware updating 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 ILOM 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 ILOM 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. When using 'stop|start /SYS' or 'stop|start /System' or when restarting the hosts too quickly, one or more hosts FW may not be updated. To avoid this scenario

• do not use 'start /SYS' or 'start /System',
• before starting a host, user must make sure that the Host FW has been updated to the target version

9. To determine if a HOST will have any bits updated when it is stopped and started, you can check the information in Doc ID 1967048.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

References

This solution has no attachment