Directly upgrading from SCS 1.2 to SCS 1.3 is not supported, but this limitation is removed starting with SCS 1.4. Swarm supports upgrading from SCS 1.1, 1.2, or 1.3 to SCS 1.4 and booting from Storage bundle v15.0 with multicast disabled.
Upgrade Notes
Any version before SCS 1.4 cannot boot versions of Swarm storage that include the optional multicast feature (version 15.0 and later). This is due to changes required in SCS to properly support this feature.
Complete the SCS upgrade first if upgrading both SCS and Swarm Storage simultaneously. Then add the new Swarm Storage component to the SCS repo (using
scsctl repo component add ...). During this process,scsctlwill prompt as to whether or not to enable multicast for the storage cluster by asking to set a value forcip.multicastEnabled. SelectTrueto enable the use of multicast (this matches the behavior of prior versions of Swarm), orFalseto disable it. If you are unsure which to choose, contact DataCore Support.Installing a new Swarm Storage component version does not automatically activate the version for PXE booting; the new version must be explicitly activated. Run the below command and choose the new version to activate:
Code Block scsctl storage software activate
Refer to the following steps to upgrade SCS:
Install the new RPM.
...
rpm -Uvh swarm-scs-[version].x86_64.rpmIf static IP addresses were previously assigned before this migrationupgrade, skip this step and proceed to the “boot/reboot” step.
Use case #1:step#2
Allow DHCP to assign IP addresses
When the cluster nodes are rebooted, DHCP will assign an IP address to each node. If the nodes have already been booted with manually assigned IPs, the assigned IP addresses will remain the same. If IP addresses were not manually assigned, but existing DHCP leases are still in effect, then currently assigned IP addresses will remain the same. If existing DHCP leases have expired (or this is the first boot of the storage cluster), DHCP will assign IP addresses from the allocated pool in no particular order . When this use case is selected, and so proceed to the “Boot/reboot” stepSwarm nodes.Use case #2: Pre-assign an IP address to each storage node
In this case, an IP address must be manually assigned to each storage node before it is rebooted. The procedure for manual assignment is fully explained in Configuring Swarm for Static IPs with Swarm Cluster Services (SCS)).
The summary of the manual assignment procedure is:Get an instance list that provides a node ID to use in the next step.
Code Block scsctl storage instance list
Assign an IP address to each node.
Code Block scsctl storage config set -d -i {chassis ID} "network.ipV4Address={your.static.address.here}"
Install the new RPM.
Code Block rpm -Uvh swarm-scs-[version].x86_64.rpmRun the following command.
Code Block scsctl diagnostics upgrade_check
Refer to the following step if an error occurs during the upgrade_check command:
| Code Block |
|---|
systemctl restart swarm-platform && sleep 90 |
Run the diagnostics check.
Code Block scsctl diagnostics config scan_missingIt shows the below output:
Code Block Running step [11/11]: Show the next steps after this wizard ******************************************************************************** Congratulations, your Swarm Cluster Services server has been upgraded! Please reboot, then run the following to ensure your system is fully configured:Reboot the system.
Re-initialize DHCP:
Code Block scsctl init dhcp --dhcp-reserve-lower [integer]
...
Troubleshooting Notes
Refer to the following steps if an error occurs during the upgrade_check command:
...
Choose the SCS version to activate to the latest version
Code Block scsctl platform software activate
...
Choose the version that matches the recently installed RPM.
...
| Info | ||
|---|---|---|
InfoA customer might see the below error in the output while upgrading to SCS 1.7 or above, but this is safe to ignore it.
|
...