Before Upgrading#

Dependencies#

The supported upgrade paths to release 24.2 using this ISO upgrade:

  • 21.4.x > 24.2

Versions#

Before starting with this upgrade, please read the following notes related to upgrades from earlier versions of the software.

Release 24.2 - Sync and Dashboard Management

  • After upgrade to release 24.2, dashboard management is available after 30 minutes, since the scheduled delta-sync process initially carries out a full sync and thereafter an incremental resource sync. No manual sync is therefore required after upgrade. For details, see the Insights Analytics section of the Platform Guide.

  • Ensure that:

Release 24.1 onwards - Microsoft Teams, Deprecation of Basic Authentication

Starting with Automate 24.1, Microsoft PowerShell must be set up for app (application) registration for authentication.

See the following references:

Release 24.1 onwards - Virtual Machine and ESXi Version Compatibility, and AVX Support

Before starting your upgrade, ensure that the hardware version of each of your virtual machines (VMs) is at least version 11, compatible with ESXi 6.0 and up, and that your host CPU supports AVX (Advanced Vector Extensions).

A check cluster command in the Automate pre-upgrade steps checks for AVX support. To ensure that AVX support is added to the VMs, you’ll need to upgrade the compatibility of the VM in vCenter.

Before upgrading to release 24.1:

  • Install EKB-21455-21.4.0_patch.script first. Refer to MOP-EKB-21455-21.4.0_patch.pdf.

    • Server Name: https://voss.portalshape.com

    • Path: Downloads > VOSS Automate > 24.1 > Upgrade > ISO

    • MOP: MOP-EKB-21455-21.4.0_patch.pdf

    • Patch File: EKB-21455-21.4.0_patch.script

Release 21.4 onwards - Product License Changes

From release 21.4 onwards, VOSS Automate allows for the registration and update of product licenses within the application. A licensing service is installed during installation or upgrade and a license token is associated with the platform on which it is installed.

Maintenance Windows and Upgrade Duration#

Note

The standard screen command should be used where indicated. See: Using the screen command.

Normal operations will be interrupted during an upgrade. Perform the upgrade in a maintenance window. Refer to the type of upgrade for details on the upgrade duration.

Tasks that are marked Prior to Maintenance Window can be completed a few days prior to the scheduled maintenance window so that VOSS support can be contacted if needed and in order to allow for reduced downtime.

Ensure that sufficient time is allocated to the maintenance window. This may vary in accordance with your topology, number of devices and subscribers.

The information below serves as a guideline:

Note

Contact VOSS support if further guidance is required.

  • Cluster upgrade: 4h

  • Template install: 2.5h

  • For a 500K Data User system (13Mil RESOURCE documents), the expected upgrade_db step is about 12h.

  • For a 160K Data User system (2.5Mil RESOURCE documents), the expected upgrade_db step is about 2.5h.

You can follow the progress on the Admin Portal transaction list.