...
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,scsctl
will prompt as to whether or not to enable multicast for the storage cluster by asking to set a value forcip.multicastEnabled
. SelectTrue
to enable the use of multicast (this matches the behavior of prior versions of Swarm), orFalse
to disable it. If you are unsure which to choose, contact DataCore Support.
...
If static IP addresses were previously assigned before this upgrade, skip this step and proceed to 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 and , so proceed to “Boot/reboot” Swarm nodes.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.rpm
Run the following command.
Code Block scsctl diagnostics upgrade_check
Note
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_missing
It 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]
Choose the SCS version to activate to the latest version.
Code Block scsctl platform software activate
...
When these conditions are true, the upgrade process requires an additional couple of steps.:
After SCS is upgraded to 1.7.1, the storage software must be upgraded to the most recent version or to any version that supports direct IP assignment and includes the “network.useStaticAddresses” setting.
After the new storage software version is activated, the storage cluster must be rebooted before any direct IP assignment is performed.
...
When restarting an entire cluster all at once, verify that nodes that were already part of the cluster are restarted first. Once they are fully online, it is safe to boot any new nodes being added into the cluster. Booting these new nodes too early can lead to IP address conflicts, and the new nodes will fail to come online.
...