Updating the system manually

During a manual system upgrade, each node is removed, individually updated, and added back to the cluster in turn.

Manual upgrade allows users to directly control the removal and upgrade of individual nodes. It is also used when automatic CCU has encountered problems midway through upgrade and requires additional intervention from the user. Some of the checks from automatic CCU are removed, so manual upgrade should be used with caution.

As each node is removed and then updated, which also includes a restart, the partner node in the I/O group processes I/O. Only one node should be updated at a time. After the final node is removed for upgrade, the system automatically commits the upgrade.

Start the update on the Settings > System > Update System in the management GUI by using the Alternative Update Options tab. Select the appropriate test utility, upgrade package, and code level. When asked, select Service Assistant Manual Update.

Remove a node from the cluster, use the Update Manually panel to upload the necessary file, and start the update. After the node update is complete, it is added back to the system automatically. The update status indicates that a manual upgrade is in progress. Completion estimate is not provided because it depends on the pause between each node being removed and upgraded.

Update each node, one at a time, other than the configuration node by using this method. After all nodes, other than the configuration node, are updated and successfully returned to the cluster, remove the configuration node. Removal of the configuration node causes the remaining nodes, which are all on the uplevel version of the code, to commit the upgrade. One of the remaining nodes is elected as the new configuration node. After the commit is complete, a notification is sent to the GUI.

After the commit is complete, the removed node can be added back to the system. This node identifies that it is still on the downlevel build and it automatically updates the code level to conform with the rest of the cluster.

You can also start the manual update by using the applysoftware CLI command by using the -prepare option. Ensure that the installsoftware command is run with the -pacedccu option. Continue to run the upgrade test utility before proceeding with the update.

The user-driven system configuration actions are restricted while the update is in progress.

After the commit, the system might automatically update firmware levels on enclosure hardware components. Similar to the node updates, these updates are performed in a nondisruptive manner.