Versions Compared

Version Old Version 52 New Version 53
Changes made by

Anjali Tyagi

Anjali Tyagi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed SCS upgrade section as creating a dedicated page that

...

  1. Swarm 11 bundle:

    1. Upgrade Swarm to 11.3, as guided by DataCore Support and the Settings Checker report.

    2. Upgrade to Gateway 5.4.1 if currently running Elasticsearch 2.3.3. Upgrade to Gateway 7.0 if currently running Elasticsearch 5.6.12. Refer to Upgrading from Gateway 5.x.

    3. Add an Elasticsearch 6 cluster and start a search feed, leaving the old feed as primary (See Migrating from Older Elasticsearch).

      1. Verify the [storage cluster] managementPassword is set properly in the gateway.cfg file if errors are encountered during feed creation. Correct the value and restart the gateway service if a change is needed.

    4. When the feed completes, make it primary.

    5. Upgrade to Gateway 7.0 if currently running Gateway 5.4.1.

    6. Configure gateway.cfg indexerHosts to point to the new Elasticsearch 6 cluster and restart CloudGateway:

      Code Block
      sudo systemctl restart cloudgateway

  2. Swarm 15 bundle:
    Follow the appropriate column in Upgrade Paths above. The general sequence is:

    1. Upgrade to SCS 1.5.

    2. Upgrade to Swarm Storage 15.

    3. Gateway 7.7 is required if upgrading from Elasticsearch 6. Ask support for the RPM. Upgrade to Elasticsearch 7.5.2 temporarily (configure_elasticsearch_with_swarm_search.py --esversion 7.5.2) and then upgrade to the latest Gateway 7.10 as Gateway 7.7 is not compatible with Elasticsearch 7.17.

    4. Verify Swarm operations (this is the time to downgrade).

    5. Run the latest ES configuration script for an in-place upgrade to the latest Elasticsearch 7.

    6. Upgrade to the latest Gateway 7.10. See Upgrading Gateway for upgrading the gateway.

Upgrading to the Latest SCS Version

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, scsctl will prompt as to whether or not to enable multicast for the storage cluster by asking to set a value for cip.multicastEnabled. Select True to enable the use of multicast (this matches the behavior of prior versions of Swarm), or False to 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
    languagebash
    scsctl storage software activate

Refer to the following steps to upgrade SCS:

  1. Install the new RPM.

    Code Block
    yum install -y [scs rpm]

  2. Run the below command:

    Code Block
    languagebash
    scsctl diagnostics upgrade_check

  3. Run the diagnostics check

    Code Block
    scsctl diagnostics config scan_missing

  4. 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:

  1. Code Block
    systemctl restart swarm-platform && sleep 90
  2. Code Block
    scsctl platform software activate

    Choose the version that matches the recently installed RPM.

  3. Proceed with re-initializing DHCP as listed above.

...

Info

A customer might see the below error in the output while upgrading to SCS 1.7 or above, but this is safe to ignore it.

...

    1. Upgrade to the latest SCS version. See Upgrading to the Latest SCS Version for upgrading SCS.