CSN Upgrades
To update any CSN implementation, download and use the CSN 8.3 bundle from the Downloads section on the DataCore Support Portal.
Note
Any components running separately from the CSN host, such as Content Gateway and Elasticsearch, are not updated by the CSN install script and must be upgraded separately, using the RPMs in the CSN bundle.
How you upgrade depends on the versions you are starting from and whether you run the Swarm UI locally on the CSN (because you have no Content Gateway available to host it):
Upgrading Swarm Storage Only
To update the version of Swarm Storage software being used in the storage cluster, do the following:
Download the latest CSN bundle from the Downloads section on the DataCore Support Portal.
Expand the bundle on your CSN server.
Install the new Storage (castor) RPM using the following command from a standard RHEL/CentOS terminal window:
yum install [new Swarm version RPM]
After the install, open the CSN Console. A new Swarm software version will appear on the Cluster Services > Netboot Management page.
See Console - Cluster Services.To switch to an alternate Swarm software version, select the desired version and click Update. This will change the software image used to network boot all Swarm nodes.
Reboot the Swarm cluster so that it can pick up the new version. You may reboot the Swarm cluster all at once or rebooting one node at a time from the Admin Console to pick up the new version.
Upgrading Storage and local Swarm UI (with script)
Important: The CSN bundle install script installs all of the RPMs involved in running the Swarm UI on the CSN itself. Do not install it on the CSN if you have a Content Gateway elsewhere to host it. To verify whether you already have Swarm UI on your CSN, log into it using this URL:
http://{CSN-IP}:91/_admin/storage
For this configuration, you can update Swarm Storage and the components needed to run Swarm UI on the CSN by doing the following:
To identify configuration issues for the upgrade, download and run the latest Storage Settings Checker, which is bundled with the Swarm Support tools. With help from Support, address any setting issues (such as deprecations and new requirements) that the report surfaces.
If you have ever customized the
/etc/caringo/netboot/netboot.cfg
file (such as for "gateway" or "kernelOptions"), make a record of your non-default parameters.Download the latest CSN bundle from the Downloads section on the DataCore Support Portal.
Expand the bundle on your CSN server.
Remove the yum lock before running the script:
yum remove yum-plugin-versionlock
Run the CSN's install script from a terminal console, or run using SSH by adding the --viassh flag:
The install script ensures that the Swarm
cluster.cfg
is current with Swarm 9, but the script may reverse some changes required for Swarm 11. Be sure to verify the following before rebooting the nodes:
In thecluster.cfg
, modify the security and SNMP users to make them Swarm 10+ compatible. See Defining Swarm Admins, Swarm Users, and Swarm Passwords.Remove the “
snmp
” user from the administrators lineRemove
security.operators
Add
snmp.rwCommunity
andsnmp.roCommunity
Verify that any customizations you needed for
/etc/caringo/netboot/netboot.cfg
(such as for "gateway" or "kernelOptions") are present.The install script restores the defaults in
/etc/rsyslog.conf
for where log files are stored. If you had changed the log location, reapply your changes after running the script.From the Netboot page of the CSN Console, select the new Swarm version.
From the Swarm UI or legacy Admin Console, reboot the whole cluster at once or do a rolling reboot. As directed by Support, you can use the Support Tools bundle script
swarmrestart
to perform a rolling reboot.
Upgrading CSN 8 (with script)
If you are already running a CSN 8.3.x version, do not upgrade unless you are running Swarm UI on the CSN. The only changes to CSN 8.3 relate to the version of Swarm UI that the /usr/bin/configure_storage_webui_with_serviceproxy.py
script sets up locally.
The CSN supports upgrade from one software version to the next via a script process similar to initial installation. The CSN will not be functional during the upgrade and will require a reboot after the software is updated. Schedule the upgrade during off peak hours to ensure Swarm activities are not disrupted.
CSN Migrations
If you are running CSN 2 or 3, contact Support for help with your migration to the current version of CSN 8.