System update

The main software update package includes new functionality, enhancements, and fixes. For more information on the contents of the release, see release notes. For details of supported upgrade paths, see the concurrent compatibility and code cross-reference page. The upgrade test utility also checks whether the proposed upgrade path is supported.

During the system update, the nodes are updated sequentially. Each node update involves a restart, during which time the partner node in the I/O group processes I/O. After all the nodes in the system are successfully restarted, the new code level is automatically committed.

After the commit, the system can automatically update firmware levels on enclosure hardware components and drives. For more details on drives, see Automatic drive updates. Similar to the node updates, these updates are performed in a non-disruptive manner.

Note: Sometimes, firmware updates can take several hours to complete. For example, requirement of completing battery conditioning cycles before you apply the firmware. But this requirement is not a reason for any concern as these updates only take place once the main software upgrade process is complete and the cluster is running in a fully operational and redundant state.

When the system is updating, certain administrative actions are restricted until the upgrade process completes. Certain commands are permitted during the upgrade process, except during the final commit phase of the upgrade. Refer to the documentation for a command to see whether it is available during upgrade.

Note: The version of the code on the config node that determines whether the command is available during upgrade.

Preparing for a system update

Before you upgrade a system, complete the following actions:

Ensure that all errors in the event log are addressed through their associated fix procedures and marked as fixed.
Ensure that all host multipathing drivers are at supported levels and are correctly configured.
For older systems, where nodes are online for more than six months, consider performing a full reboot by using the service assistant to identify any potential latent hardware issues or issues in the system environment before performing the upgrade. Check that multipathing drivers have recovered paths after each reboot.

Updating the system by using the GUI

The update is started on the Update System panel in the GUI. The GUI guides the user through the procedure, including the preinstall checks that are performed by the upgrade test utility.

Updating the system by using the CLI

To update the system by using the CLI:

Download the system code file to the /update directory.
Download and install the upgrade test utility by using the applysoftware command.
To perform preinstall checks, use the following command:
```
svcupgradetest -v <v.r.m.f>
```
Note: For example, if you are planning to update the system to SVC 8.6.0.4, use the command svcupgradetest -v 8.6.0.4
Install the system code by using the applysoftware command.

Note: For more information on the use of svcupgrade test, see https://www.ibm.com/support/pages/software-upgrade-test-utility.

Once the system update is complete, a notification is sent on the GUI. The update status, including the estimated completion time, is available in the Update System GUI panel or the lsupdate CLI command.

Troubleshooting issues during the upgrade

If issues occur during an upgrade, follow the fix procedures in the management GUI for guidance. Any user-driven node activities must only be done under the guidance of the fix procedure or IBM support to avoid any unnecessary impact to host applications.

System update duration

The following table shows the estimated time for an update on a four-node system:

Table 1. Upgrade time for a four-node cluster
Steps	Time for step (in minutes)	Minimum time (in minutes)	Maximum time (in minutes)
Get ready	1	1	1
Upgrade node A2	9-24	10	25
Upgrade node B4	9-24	19	49
Wait for 10 minutes (for multi-pathing recovery)	10	29	59
Upgrade node A1	9-24	38	83
Upgrade node B3	9-24	47	107
Commit	10	57	117
Total	-	57	117