To upgrade the NetApp Element software, you must use the sfinstall file included in the HealthTools suite of tools.
Before you begin
- The management node in your environment is running version 11.0, 11.1 or later.
- You have the latest version of HealthTools.
- You verified that the cluster is ready to be upgraded with the command sfupgradecheck.
Steps
- For NetApp HCI systems, go to the NetApp HCI software download page. For standalone SolidFire storage systems, go to the Element software download page.
- Select the correct software release and download the latest storage node image to a computer that is not the management node.
- Copy the ISO file to the management node in an accessible location like /tmp.
You can do this using, for example, SCP.
Note: When you upload the ISO file, make sure that the name of the file does not change, otherwise later steps will fail.
- Optional: Download the ISO from the management node to the cluster nodes before the upgrade.
This step reduces the upgrade time by pre-staging the ISO on the storage nodes and running additional internal checks to ensure that the cluster is in a good state to be upgraded. Performing this operation will not put the cluster into "upgrade" mode or restrict any of the cluster operations. sfinstall -u <cluster_username> -p <cluster_password> <MVIP> <path-to-install-file-ISO> --stage
Example
See the following sample input:
sfinstall 10.117.0.244 -u admin -p admin
/tmp/solidfire-rtfisodium-11.0.0.345.iso --stage
The output for the sample shows that sfinstall attempts to verify if a newer version of sfinstall is available:
sfinstall 10.117.0.244 -u admin -p admin
/tmp/solidfire-rtfisodium-11.0.0.345.iso 2018-10-01 16:52:15:
Newer version of sfinstall available.
This version: 2018.09.01.130, latest version: 2018.06.05.901.
The latest version of the HealthTools can be downloaded from:
https:// mysupport.netapp.com/NOW/cgi-bin/software/
or rerun with --skip-version-check
See the following sample excerpt from a successful pre-stage operation:
Note: When staging completes, the upgrade event message will display Storage Node Upgrade Staging Successful.
flabv0004 ~ # sfinstall -u admin -p admin
10.117.0.87 solidfire-rtfi-sodium-patch3-11.3.0.14171.iso --stage
2019-04-03 13:19:58: sfinstall Release Version: 2019.01.01.49 Management Node Platform:
Ember Revision: 26b042c3e15a Build date: 2019-03-12 18:45
2019-04-03 13:19:58: Checking connectivity to MVIP 10.117.0.87
2019-04-03 13:19:58: Checking connectivity to node 10.117.0.86
2019-04-03 13:19:58: Checking connectivity to node 10.117.0.87
...
2019-04-03 13:19:58: Successfully connected to cluster and all nodes
...
2019-04-03 13:20:00: Do you want to continue? ['Yes', 'No']: Yes
...
2019-04-03 13:20:55: Staging install pack on cluster nodes
2019-04-03 13:20:55: newVersion: 11.3.0.14171
2019-04-03 13:21:01: nodeToStage: nlabp2814, nlabp2815, nlabp2816, nlabp2813
2019-04-03 13:21:02: Staging Node nlabp2815 mip=[10.117.0.87] nodeID=[2] (1 of 4 nodes)
2019-04-03 13:21:02: Node Upgrade serving image at
http://10.117.0.204/rtfi/solidfire-rtfi-
sodium-patch3-11.3.0.14171/filesystem.squashfs
...
2019-04-03 13:25:40: Staging finished. Repeat the upgrade command
without the --stage option to start the upgrade.
The staged ISOs will be automatically deleted after the upgrade completes. However, if the upgrade has not started and needs to be rescheduled, ISOs can be manually de-staged using the command:
sfinstall -u <cluster_username> -p <cluster_password> <MVIP> --destage Note: After the upgrade has started, the de-stage option is no longer available.
- Start the upgrade with the sfinstall command and the path to the ISO file: sfinstall -u <cluster_username> -p <cluster_password> <MVIP> <path-to-install-file-ISO>
Example
See the following sample input command:
sfinstall 10.117.0.244 -u admin -p admin /tmp/solidfire-rtfi-sodium-11.0.0.345.iso
The output for the sample shows that
sfinstall attempts to verify if a newer version of
sfinstall is available:
sfinstall 10.117.0.244 -u admin -p admin /tmp/solidfire-rtfi-sodium-11.0.0.345.iso
2018-10-01 16:52:15: Newer version of sfinstall available.
This version: 2018.09.01.130, latest version: 2018.06.05.901.
The latest version of the HealthTools can be downloaded from: https://mysupport.netapp.com/NOW/cgi-bin/software/ or rerun with --skip-version-check
Example
See the following sample excerpt from a successful upgrade. Upgrade events can be used to monitor the progress of the upgrade.
# sfinstall 10.117.0.161 -u admin -p admin solidfire-rtfi-sodium-11.0.0.761.iso
2018-10-11 18:28
Checking connectivity to MVIP 10.117.0.161
Checking connectivity to node 10.117.0.23
Checking connectivity to node 10.117.0.24
...
Successfully connected to cluster and all nodes
###################################################################
You are about to start a new upgrade
10.117.0.161
10.3.0.161
solidfire-rtfi-sodium-11.0.0.761.iso
Nodes:
10.117.0.23 nlabp1023 SF3010 10.3.0.161
10.117.0.24 nlabp1025 SF3010 10.3.0.161
10.117.0.26 nlabp1027 SF3010 10.3.0.161
10.117.0.28 nlabp1028 SF3010 10.3.0.161
###################################################################
Do you want to continue? ['Yes', 'No']: yes
...
Watching for new network faults. Existing fault IDs are set([]).
Checking for legacy network interface names that need renaming
Upgrading from 10.3.0.161 to 11.0.0.761 upgrade method=rtfi
Waiting 300 seconds for cluster faults to clear
Waiting for caches to fall below threshold
...
Installing mip=[10.117.0.23] nodeID=[1] (1 of 4 nodes)
Starting to move primaries.
Loading volume list
Moving primary slice=[7] away from mip[10.117.0.23] nodeID[1] ssid[11] to new ssid[15]
Moving primary slice=[12] away from mip[10.117.0.23] nodeID[1] ssid[11] to new ssid[15]
...
Installing mip=[10.117.114.24] nodeID=[2] (2 of 4 nodes)
Starting to move primaries.
Loading volume list
Moving primary slice=[5] away from mip[10.117.114.24] nodeID[2] ssid[7] to new ssid[11]
...
Install of solidfire-rtfi-sodium-11.0.0.761 complete.
Removing old software
No staged builds present on nodeID=[1]
No staged builds present on nodeID=[2]
...
Starting light cluster block service check