.. _upgrade-standalone-ISO:
.. rst-class:: chapter-with-expand
Upgrade a Single Node Cluster Environment with the ISO and Template
---------------------------------------------------------------------
.. index:: voss;voss post-upgrade-migrations
.. index:: screen
.. index:: database;database convert_drive
.. index:: app; app cleanup
.. _19.1.2|EKB-2262:
.. _19.2.1|VOSS-497:
.. _19.2.1|VOSS-497|EKB-3126:
.. _20.1.1|VOSS-661:
.. _20.1.1|EKB-5552:
.. _20.1.1|EKB-6669:
.. _21.4|VOSS-872:
.. _24.1|VOSS-1187:
.. important::
* Before upgrading to release 24.1, ensure that an additional disk is available
for the Insights database.
.. raw:: html
See: Adding Hard Disk Space
and VOSS Automate Hardware Specifications.
.. raw:: latex
See the Adding Hard Disk Space topic in the Platform Guide and VOSS Automate Hardware Specifications in the Architecture and Hardware Specification Guide.
This disk is needed to assign to the ``insights-voss-sync:database`` mount point.
See: :ref:`standalone-Post-maintenance-mount-insights-disk`.
* Before upgrading to release 24.1, 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 VOSS support can be contacted 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.
* 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 reduce down time.
The standard **screen** command should be used where indicated.
See: :ref:`screen-command`.
.. _standalone-Download-Files-and-Check:
Download Files and Check (Prior to Maintenance Window)
......................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+==============================================================================+====================+
| VOSS files: | |
| | |
| **https://voss.portalshape.com > Downloads > VOSS Automate > XXX > Upgrade** | |
| | |
| Download ``.iso`` and ``.template`` files, where XXX matches the release. | |
| Transfer the file to the ``media/`` folder. Two options: | |
| | .. raw:: html |
| Either using SFTP: | |
| | |
| |
|
| | |
| | |
| | |
| Or using SCP: | |
| | |
| | |
| * **scp platform@:~/media** | |
| | |
| * **scp platform@:~/media** | |
| | |
| | |
| Verify that the ``.iso`` image and ``.template`` file copied: | |
| | |
| | |
| * **ls -l media/** | |
| | |
| | |
| Verify that the original ``.sha256`` checksums on the | |
| Download site match. | |
| | |
| | |
| * **system checksum media/** | |
| | |
| ``Checksum: `` | |
| | |
| * **system checksum media/** | |
| | |
| ``Checksum: `` | |
| | |
| | |
+------------------------------------------------------------------------------+--------------------+
.. _standalone-Upgrade-Security-Health-Steps:
Security and Health Steps single node cluster (Prior to Maintenance Window)
..................................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+----------------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+====================================================================================================+====================+
| Validate the system health. | |
| | |
| | |
| | |
| Verify there are no pending Security Updates: | .. raw:: html |
| | |
| |
|
| | |
| |
|
+----------------------------------------------------------------------------------------------------+--------------------+
| Check system health. | |
| | |
| * **diag disk** | |
| | |
| If there is any sign of the paths below are over 80% full, a clean-up is needed, | |
| for example to avoid risk of 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) | |
| | |
| | |
| | |
| | .. raw:: html |
| | |
| |
|
| | |
| |
|
| | |
| * **Adaptation check** - if the *GS SME Adaptation* is installed, check for duplicate instances of | |
| of ``GS_SMETemplateData_DAT`` and deleted any duplicates before upgrading to 21.2. | |
+----------------------------------------------------------------------------------------------------+--------------------+
.. _standalone-Schedules-Transactions-Version-Check:
Version Check (Maintenance Window)
.........................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+-------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+===========================================================================================+====================+
| | |
| **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: :ref:`standalone-post-template-upgrade-tasks-iso`. | |
| | |
| **Version** | |
| | |
| Record the current version information. This is required for upgrade troubleshooting. | |
| | |
| * Log in on the Admin Portal and record the information contained in the | .. raw:: html |
| **About > Extended Version** | |
| |
|
| | |
| |
|
| | |
| | |
+-------------------------------------------------------------------------------------------+--------------------+
.. _maintenance-window-Pre-Upgrade-Standalone-Steps:
Pre-Upgrade Steps single node cluster (Maintenance Window)
..................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+-----------------------------------------------------------------------------------------+--------------------+
| Create a restore point and then restart server. | |
| | |
| As part of the rollback procedure, ensure that | |
| a suitable restore point is obtained prior to the start of the | .. raw:: html |
| activity, as per the guidelines for the infrastructure on which | |
| the VOSS Automate platform is deployed. If you cannot |
|
| | |
| |
|
| After the restore point has been created, restart. | |
| | |
| Optional: If a backup is required in addition to the restore point, use the | |
| **backup add ** and | |
| **backup create ** commands. For details, refer to the *Platform Guide*. | |
| | |
+-----------------------------------------------------------------------------------------+--------------------+
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+---------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+=======================================================================================+====================+
| Before upgrading, check all services: | |
| | |
| Make sure no services are stopped/broken. The message 'suspended waiting for mongo' | |
| is normal on a fresh node. | |
| | |
| * **app status** | |
| | .. raw:: html |
| | |
| |
|
| | |
| Verify the node is not in the 'recovering' state (``stateStr`` is not ``RECOVERING``) | |
| | |
| | |
| * **database config** | |
| | |
+---------------------------------------------------------------------------------------+--------------------+
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+----------------------------------------------------------------------------------------+--------------------+
| The following step is needed if own private certificate and generated SAN certificates | |
| are required and the ``web cert gen_csr`` command was run. | |
| For details, refer to the Web Certificate Setup Options topic in the Platform Guide. | |
| | |
| The steps below are needed to check if a CSR private key exists but no associated | |
| signed certificate is available. | .. raw:: html |
| | |
| Request VOSS support to run on the CLI as ``root`` user, the following command: |
|
| | |
| | |
| If the ``echo $SIGNED`` command output is blank, back up the ``csr/`` directory with | |
| for example the following command: | |
| | |
| :: | |
| | |
| mv /opt/platform/apps/nginx/config/csr/ /opt/platform/apps/nginx/config/csrbackup | |
| | |
+----------------------------------------------------------------------------------------+--------------------+
.. _maintenance-window-upgrade-ISO-standalone:
Upgrade single node cluster (Maintenance Window)
.......................................................
.. note::
* By default, the cluster upgrade is carried out in parallel on all nodes and without any
backup in order to provide a fast upgrade.
* For systems *upgrading to 24.1 from 21.4.0 - 21.4-PB5*:
* The VOSS platform maintenance mode will be started automatically
when the **cluster upgrade** command is run. This prevents any new occurrences of scheduled transactions, including the
24.1 database syncs associated with **insights sync**. For details on **insights sync**, see the *Insights Analytics* topic
in the Platform Guide.
* The **cluster maintenance-mode stop** command must however be run manually
after the maintenance window of the upgrade: :ref:`standalone-maintenance-window-manual-stop`.
For details on the VOSS platform maintenance mode, see the *Maintenance Mode* topic in the Platform Guide.
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+-----------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+=============================================================================+====================+
| It is recommended that the upgrade steps | |
| are run in a terminal opened with the **screen** command. | |
| | |
| On the primary unified node: | |
| | |
| | |
| * **screen** | |
| | .. raw:: html |
| * **cluster upgrade media/** | |
| |
|
| will be removed from the system at this stage. | |
| |
|
| | |
| Note: If the system reboots, do not carry out the next manual reboot step. | |
| | |
| To remove a mount directory ``media/`` on nodes that may | |
| have remained after for example an upgrade, run: | |
| | |
| **cluster run all app cleanup** | |
| | |
| Manual reboot *only if needed*: | |
| | |
| * **system reboot** | |
| | |
| If node messages: `` failed with timeout`` are displayed, | |
| these can be ignored. | |
| | |
| Since all services will be stopped, this takes some time. | |
| | |
| Close **screen**: ``Ctrl-a \`` | |
| | |
+-----------------------------------------------------------------------------+--------------------+
.. note::
In order to carry out fewer upgrade steps, the updates of instances
of some models are skipped in the cases where:
* ``data/CallManager`` instance does not exist as instance in ``data/NetworkDeviceList``
* ``data/CallManager`` instance exists, but ``data/NetworkDeviceList`` is empty
* Call Manager AXL Generic Driver and Call Manager Control Center Services
match the ``data/CallManager`` IP
.. _maintenance-window-Post-Upgrade-Security-Health-Steps-standalone:
Post-Upgrade, Security and Health Steps single node cluster (Maintenance Window)
....................................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+---------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+=======================================================================================+====================+
| Verify the status: | |
| | |
| * **diag health** | .. raw:: html |
| | |
| |
|
| | |
| |
|
| | |
+---------------------------------------------------------------------------------------+--------------------+
| 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. | .. raw:: html |
| | |
| |
|
| | |
| |
|
| | |
+---------------------------------------------------------------------------------------+--------------------+
| Complete all the security updates. | |
| | |
| | .. raw:: html |
| * **security update** | |
| |
|
| | |
| |
|
| * **system reboot** | |
| | |
+---------------------------------------------------------------------------------------+--------------------+
.. _standalone-Template-Upgrade:
Template Upgrade single node cluster (Maintenance Window)
................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+---------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+=======================================================================================+====================+
| It is recommended that the upgrade steps | |
| are run in a terminal opened with the **screen** command. | |
| | |
| | .. raw:: html |
| * **screen** | |
| |
|
| | |
| | |
+---------------------------------------------------------------------------------------+--------------------+
The following message appears:
::
Running the DB-query to find the current environment's
existing solution deployment config...
* Python functions are deployed
* System artifacts are imported.
The template upgrade automatically detects the deployment mode, either "Enterprise" or "Provider".
A message displays according to the selected deployment type.
Check for one of the messages below:
::
Importing EnterpriseOverlay.json
Importing ProviderOverlay.json ...
The template install automatically restarts necessary applications.
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+==========================================================================================+====================+
| | |
| Review the output from the **app template** command and confirm that the upgrade message | .. raw:: html |
| appears: | |
| |
|
| | |
| |
|
| | |
| | |
| | |
| :: | |
| | |
| Deployment summary of PREVIOUS template solution | |
| (i.e. BEFORE upgrade): | |
| ------------------------------------------------- | |
| | |
| | |
| Product: [PRODUCT] | |
| Version: [PREVIOUS PRODUCT RELEASE] | |
| Iteration-version: [PREVIOUS ITERATION] | |
| Platform-version: [PREVIOUS PLATFORM VERSION] | |
| | |
| | |
| This is followed by updated product and version details: | |
| | |
| | |
| :: | |
| | |
| Deployment summary of UPDATED template solution | |
| (i.e. current values after installation): | |
| ----------------------------------------------- | |
| | |
| Product: [PRODUCT] | |
| Version: [UPDATED PRODUCT RELEASE] | |
| Iteration-version: [UPDATED ITERATION] | |
| Platform-version: [UPDATED PLATFORM VERSION] | |
| | |
+------------------------------------------------------------------------------------------+--------------------+
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+------------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+================================================================================================+====================+
| | |
| | .. raw:: html |
| | |
| * If no errors are indicated, make a backup or restore point as per the |
|
| | |
| |
|
| | |
+------------------------------------------------------------------------------------------------+--------------------+
| | |
| | .. raw:: html |
| | |
| For an unsupported upgrade path, the install script stops with the message: |
|
| | |
| and see Transaction logs for more detail. |
|
| | |
| You can restore to the backup or rollback/revert to the restore point made before the upgrade. | |
| | |
| | |
+------------------------------------------------------------------------------------------------+--------------------+
| | |
| | .. raw:: html |
| If there are errors for another reason, the install script stops with a | |
| failure message listing the problem. Contact VOSS support. |
|
| allowing the migration to proceed whilst the system is in use - thereby limiting | |
| A transaction is queued on VOSS Automate and its progress is displayed as it executes. |
|
| | |
+------------------------------------------------------------------------------------------------+--------------------+
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+==========================================================================================+====================+
| | |
| Check status and health | .. raw:: html |
| | |
| |
|
| | |
| |
|
| | |
+------------------------------------------------------------------------------------------+--------------------+
.. _standalone-post-template-upgrade-tasks-iso:
Post Template Upgrade Tasks single node cluster (Maintenance Window)
...........................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+--------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+======================================================================================+====================+
| | |
| Verify the upgrade: | .. raw:: html |
| | |
| Log in on the Admin Portal and check the information contained in the | |
| **About > Version** menu. Confirm that versions have upgraded. |
|
| where ``XXX`` corresponds with the release number of the upgrade. | |
| trying to open the interface again. |
|
| | |
| | |
+--------------------------------------------------------------------------------------+--------------------+
.. _standalone-Log-Files-Error-Checks:
Log Files and Error Checks single node cluster (Maintenance Window)
......................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+----------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+==================================================================================+====================+
| Inspect the output of the command line interface for upgrade errors, | .. raw:: html |
| for example ``File import failed!`` or ``Failed to execute command``. | |
| | |
| 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: |
|
| 'log view platform/execute.log' | |
| directory to an SFTP server: |
|
| | |
| * **log send sftp://x.x.x.x install** | |
| | |
+----------------------------------------------------------------------------------+--------------------+
| | .. raw:: html |
| Log in on the Admin Portal as system level administrator, go to | |
| **Administration Tools > Transaction** and inspect the transactions |
|
| | |
| |
|
| | |
+----------------------------------------------------------------------------------+--------------------+
.. _standalone-maintenance-window-manual-stop:
Manually Stop the Maintenance Window
.................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+----------------------------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+================================================================================================================+====================+
| On the CLI: | |
| | |
| Run the **cluster maintenance-mode stop** command to end the automatic start of the VOSS maintenance mode when | .. raw:: html |
| the **cluster upgrade** command was run when upgrading to 24.1 from 21.4.0 - 21.4-PB5. | |
| |
|
| | |
| |
|
| | |
+----------------------------------------------------------------------------------------------------------------+--------------------+
.. _standalone-Post-maintenance-window-Licensing:
Licensing (outside, after Maintenance Window)
.................................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+-------------------------------------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+===================================================================================================================+====================+
| From release 21.4 onwards, the deployment needs to be licensed. | .. raw:: html |
| After installation, a 7-day grace period is available to license the product. | |
| Since license processing is only scheduled every hour, |
|
| | |
| |
|
| | |
+-------------------------------------------------------------------------------------------------------------------+--------------------+
.. _standalone-Post-maintenance-mount-insights-disk:
Mount the Insights disk (outside, after Maintenance Window)
.............................................................
.. tabularcolumns:: |p{13.5cm}|p{4cm}|
+---------------------------------------------------------------------------------------+--------------------+
| Description and Steps | Notes and Status |
+=======================================================================================+====================+
| *On the primary unified node*, assign the ``insights-voss-sync:database`` mount point | |
| to the drive added for the Insights database prior to upgrade. | |
| | .. raw:: html |
| For example, if ``drives list`` shows the added disk as: | |
| |