System update
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. Similar to the node updates, these updates are performed in a non-disruptive manner.
Updating the system by using the GUI
Before updating the system, ensure that the multi-pathing driver on connected hosts is correctly configured and working.
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
- 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.
User-driven system configuration actions are restricted while the update is in progress.
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.
| 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 |