On this page

Unified Node Topology: Upgrade a Multinode Environment with the Delta Bundle

Note

  • While system upgrade takes approximately two hours at a single site, this may vary in accordance with your topology, number of devices and subscribers. Adjust your upgrade maintenance window to allow for your configuration.

The standard screen command should be used where indicated, and the reconnect parameter is available if needed:

  • screen - start a new session

  • screen -ls - show sessions already available

  • screen -r [screen PID] - reconnect to a disconnected session

We recommend using the screen command to avoid failures if the connection is interrupted whilst running the command. If the connection is interrupted whilst running the command in screen then the session can be retrieved by first listing the sessions PID currently running in screen: screen -ls, and then reconnecting to the session using screen -r [screen PID].

The version of screen used in VOSS Automate also supports the creation of a log file. If long-running commands will be run, the log file captures screen console output up to the session timeout. A message shows:

timed out waiting for input: auto-logout

To create a screen log file:

  1. Run screen and wait for screen to open.

  2. Press <Ctrl>-a then : (colon). This will enter screen command mode at the bottom of the console.

  3. Create your screen logfile in the media/ directory:

    1. In screen command mode, type logfile media/<screen-logfilename>.log

    2. Press <Enter>

    3. Press <Ctrl>-a and then H to start writing to the log file

    4. Run your commands.

If the screen session times out, you can obtain console output from the log file, for example:

$ sftp platform@<host>:media/<screen-logfilename>.log

Download Files and Check

Description and Steps

Notes and Status

VOSS files:

https://voss.portalshape.com > Downloads > VOSS Automate > XXX > Upgrade

Download XXX-Delta-Bundle.script file, where XXX matches the release. Transfer the XXX-Delta-Bundle.script file to the media/ folder of the primary Unified node. Two file transfer options:

Either using SFTP:

  • sftp platform@<primary_unified_node_hostname>

  • cd media

  • put <XXX-Delta-Bundle.script>

Or using SCP:

  • scp <XXX-Delta-Bundle.script> platform@<primary_unified_node_hostname>:~/media

On the primary Unified node, verify that the .script file copied:

  • ls -l media/

On the primary Unified node, verify that the original .sha256 checksums on the SFTP server match.

  • system checksum media/<XXX-Delta-Bundle.script>

    Checksum: <SHA256>

Adaptations Check

Description and Steps

Notes and Status

Identify installed adaptations and determine any effect on the upgrade plan.

If the release is accompanied by Upgrade Notes, refer to the details.

Schedules, Transactions and Version Check

Description and Steps

Notes and Status

Turn off any scheduled imports to prevent syncs triggering part way through the upgrade. Two options are available:

Individually for each job:

  1. Log in on the GUI as a high level administrator above Provider level.

  2. Select the Scheduling menu to view scheduled jobs.

  3. Click each scheduled job. On the Base tab, uncheck the Activate check box.

Mass modify:

  1. On the GUI, export scheduled syncs into a bulk load sheet.

  2. Modify the schedule settings to de-activate scheduled syncs.

  3. Import the sheet.

Schedules enabled on the CLI:

  1. Run schedule list to check if any schedules exist and overlap with the maintenance window.

  2. For overlapping schedules, disable. Run schedule disable <job-name>.

Check for running imports. Either wait for them to complete or cancel them:

  1. Log in on the GUI as a high level administrator above Provider level.

  2. Select the Transaction menu to view transactions.

  3. Filter the Action column:

    1. Choose Status as “Processing” and then choose each Action that starts with “Import”, for example, “Import Unity Connection”.

    2. Click Search and confirm there are no results.

    3. If there are transactions to cancel, select them and click Cancel.

Customized ``data/Settings``

If data/Settings instances have been modified, record these or export them as JSON.

The modifications can be re-applied or exported JSON instances can be merged following the upgrade. See: Post Template Upgrade Tasks.

Version

Record the current version information. This is required for upgrade troubleshooting.

  • Log in on the GUI and record the information contained in the About > Extended Version

Pre-Upgrade, Security and Health Steps

Description and Steps

Notes and Status

Verify that the primary node is the active primary node at the time of upgrade.

database config

Ensure that the node on which the installation will be initiated has the stateStr parameter set to PRIMARY and has the highest priority number (highest priority number could vary depending on cluster layout).

Example output

<ip address>:27020:
  priority: <number>
  stateStr: PRIMARY
  storageEngine: WiredTiger

Validate the system health.

On the Primary Unified Node, verify cluster connectivity:

  • cluster status

On each node verify network connectivity, disk status and NTP.

  • cluster check

If there is any sign of the paths below are over 80% full, a clean-up is needed to avoid risk of for example full logs occurring during upgrade. Clean-up steps are indicated next to the paths:

/              (call support if over 80%)
/var/log       (run: log purge)
/opt/platform  (remove any unnecessary files from /media directory)
/tmp           (reboot)

On the Primary Unified Node, verify there are no pending Security Updates on any of the nodes:

  • cluster run all security check

As part of the rollback procedure, ensure that a suitable restore point is obtained prior to the start of the activity, as per the guidelines for the infrastructure on which the VOSS Automate platform is deployed.

VOSS cannot guarantee that a restore point can be used to successfully restore VOSS Automate. If you cannot restore the application from a restore point, your only recourse is to reinstall the application.

Optional: If a backup is also required, use the backup add <location-name> and backup create <location-name> commands. For details, refer to the Platform Guide.

Description and Steps

Notes and Status

Before upgrading, check all services, nodes and weights for the cluster:

Make sure no services are stopped/broken. The message ‘suspended waiting for mongo’ is normal on the fresh unified nodes.

  • cluster run all app status

Make sure all application nodes show 4 or 6 nodes.

  • cluster run application cluster list

Check that the database weights are set. It is critical to ensure the weights are set before upgrading a cluster.

  • cluster run application database weight list

Example output:

172.29.21.240:
    weight: 80
172.29.21.241:
    weight: 70
172.29.21.243:
    weight: 60
172.29.21.244:
    weight: 50

Verify the primary node in the primary site and ensure no nodes are in the ‘recovering’ state (stateStr is not RECOVERING). On the primary node:

  • database config

Upgrade

Description and Steps

Notes and Status

On the primary unified node:

  • screen

Run (optionally with command parameters below):

app install media/<script_file> delete-on-success yes --force

The upgrade will also silently run an updated version of cluster check and the upgrade will fail to proceed if any error conditions exist. Fix before proceeding. Refer to the Platform Guide for details on the new version of the cluster check command.

Run:

  • database config

and verify the number of nodes are uneven, i.e. either 5 or 7. If not, run: cluster provision role database and ensure an arbitrator shows when you run database config again (stateStr: ARBITER).

From release 19.1.2 and later, the delete-on-success parameter and yes or no value have been added to remove or keep the the script file in the media/ directory after successful installation.

Note that during the upgrade, phone registration data is cleared. A message will show in the log: Remove phone registration data. This is required so that old values are not displayed, since after the upgrade this information is no longer stored in the resource cache.

Post-Upgrade, Security and Health Steps

Description and Steps

Notes and Status

On the primary unified node, verify the cluster status:

  • cluster status

  • cluster check

  • If any of the above commands show errors, check for further details to assist with troubleshooting:

    cluster run all diag health

If upgrade is successful, the screen session can be closed by typing exit in the screen terminal. If errors occurred, keep the screen terminal open for troubleshooting purposes and contact VOSS support.

Check for needed security updates. On the primary node, run:

  • cluster run all security check

If one or more updates are required for any node, run on the primary Unified node:

  • cluster run all security update

Note: if the system reboots, do not carry out the next manual reboot step.

Manual reboot only if needed:

  • cluster run notme system reboot

If node messages: <node name> failed with timeout are displayed, these can be ignored.

  • system reboot

Since all services will be stopped, this takes some time.

Post Template Upgrade Tasks

Description and Steps

Notes and Status

SSO Login URL check if needed

Verify the SSO Login URL if needed. Go to Single Sign On > SSO Identity Provider and ensure your URL matches the SSO Login URL value.

Customized ``data/Settings``

Merge the previously backed up customized data/Settings with the latest settings on the system by manually adding the differences or exporting the latest settings to JSON, merging the customized changes and importing the JSON.

Support for VG400 and VG450 Analogue Gateways

Before adding the VG400 or VG450 Gateway, the device/cucm/GatewayType model needs to be imported for each Unified CM.

  1. Create a Model Type List which includes the device/cucm/GatewayType model.

  2. Add the Model Type List to all the required Unified CM Data Syncs.

  3. Execute the Data Sync for all the required Unified CMs.

Verify the upgrade

Log in on the GUI and check the information contained in the About > Extended Version menu. Confirm that versions have upgraded:

  • Release should show 21.3

  • Platform Version should show 21.3

If your web browser cannot open the user interface, clear your browser cache before trying to open the interface again.

  • For configurations that make use of the Northbound Billing Integration (NBI), please check the service status of NBI and restart if necessary.

Restore Adaptations

Description and Steps

Notes and Status

Restore and adaptations prior to upgrade.

If the release is accompanied by Upgrade Notes, refer to the details on adaptation impact.

Restore Schedules

Description and Steps

Notes and Status

Re-enable scheduled imports if any were disabled prior to the upgrade. Two options are available:

Individually for each job:

  1. Log in on the GUI as a high level administrator above Provider level.

  2. Select the Scheduling menu to view scheduled jobs.

  3. Click each scheduled job. On the Base tab, check the Activate check box.

Mass modify:

  1. Modify the exported sheet of schedules to activate scheduled syncs.

  2. Import the bulk load sheet.

Note

Select the Skip next execution if you do not wish to execute schedules overlapping the maintenance window, but only execute thereafter.

Schedules enabled on the CLI:

  1. For disabled schedules that were overlapping the maintenance window, enable.

    Run schedule enable <job-name>.

For overlapping schedules, disable. Run schedule disable <job-name>.

Release Specific Updates

Description and Steps

Notes and Status

When upgrading to release 21.3, users of Microsoft apps should after upgrade, select each Microsoft Tenant (relation/MicrosoftTenant) in the Admin GUI and click Save on it without making any changes.

This step is required so that VOSS Automate can communicate with the Tenant post upgrade.

Log Files and Error Checks

Description and Steps

Notes and Status

Inspect the output of the command line interface for upgrade errors.

Use the log view command to view any log files indicated in the error messages, for example, run the command if the following message appears:

For more information refer to the execution log file with
'log view platform/execute.log'

For example, if it is required send all the install log files in the install directory to an SFTP server:

  • log send sftp://x.x.x.x install

Log in on the GUI as system level administrator, go to Administration Tools > Transaction and inspect the transactions list for errors.

previous

Upgrade Guide with Delta Bundle

next

Modular Cluster Topology: Upgrade a Multinode Environment with the Delta Bundle