Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrade Procedure

Warning:

If you are upgrading from 2.34, please make sure you use the special upgrade procedure described in the document Upgrading Control Center from Version 2.34.

If you have previously upgraded from 2.34 and are now going to upgrade to 3.x, you must begin by undoing a step performed in the 2.34 upgrade. Run this command:

You can then follow the instructions below.

Below are general instructions for upgrading Control Center. Note that for specific releases, additional actions may be required; separate instructions are then given in each case in what follows.

Be sure to refer to the current Paragon Active Assurance Installation Guide.

  • Disable the apache2 and netrounds-callexecuter services completely:

  • Stop all Paragon Active Assurance services:

  • Make backups according to the Operations Guide, chapter Backing Up Product Data, starting with the section "Backing Up the PostgreSQL Database".

  • Verify the integrity of the tarball containing the new Control Center version:

  • Unpack the Control Center tarball:

  • Install new Control Center packages.

    In the file /etc/netrounds/netrounds.conf you can optionally configure the SPEEDTEST_ADDRESS setting (if you are going to use Speedtest). This can either point to the same IP address that SITE_URL resolves to, or it can have a hostname of its own.

    Warning:

    You will now be prompted about overwriting existing configuration files. Before proceeding, please read all the information about settings below.

    Note:
    • We highly recommend that you first inspect the difference between your old configuration and the new one using the "D" choice. In most cases you will then want to keep your old settings by pressing "N" (do not overwrite).
    • New optional and updated settings may be available in the example configuration files provided in the packages. We recommend that you review these and add new options as appropriate for your installation.
    Warning:

    For the Apache configuration files found in

    you need to press "Y", which is the "package maintainer's version".

    If you have installed proper SSL certificates (as recommended) instead of the default snakeoil ones, you will have to modify the file again to point to the correct path in the SSLCertificateFile and SSLCertificateKeyFile settings after the Debian package installation has completed. See the Installation Guide, chapter Service Configuration, section "SSL Certificate Configuration".

  • Run the database migration:

    Warning:

    If you have changed the database password from the default, make sure you also change this in the db-password setting in the /etc/netrounds/plugin.yaml file before running ncc migrate. Otherwise, the command will fail.

    Note:
    • This is a sensitive command, and care should be taken when executing it on a remote machine. In such a scenario it is strongly recommended that you use a program like screen (generally installed by default on popular Linux distributions) or tmux (run sudo apt-get install tmux to install) so that the migrate command will continue running even if the ssh session breaks.
    • This command takes considerable time to execute.
  • Restart all Paragon Active Assurance services:

  • Install the new Test Agent repository and plugins.

    The plugins are used by Test Agent Applications.

  • Enable services as follows:

  • Restart all Paragon Active Assurance services:

    Note:

    You must do this to get the services up and running again after the upgrade.

  • To activate the new configuration, you also need to run:

  • Check that the system is up and running with the commands

  • Do the following to enable the latest version of all plugins in all accounts:

    For more information on how to manage plugins using the Control Center CLI, see the in-app help under "Plugins".

  • Log in to the Control Center GUI and go to the Test Agents view. Next to each Test Agent for which an upgrade is available, an up-arrow icon appears. Click that icon to go ahead with the upgrade.

Troubleshooting

Password Authentication Failed For User

If the ncc migrate command fails with an error message

you must update the variable db-password in the /etc/netrounds/plugin.yaml file as explained in the warning above. Edit this file and then rerun ncc migrate.

Target WSGI Script Not Found

If you accidentally selected "N" for the Apache configuration files (see this step above) and got an error message like the one below

run the following commands to get back on track:

This overwrites the old configuration with the new one in the updated package.

Again, if you have installed proper SSL certificates (as recommended) instead of the default snakeoil ones, you will have to modify the file again to point to the correct path in the SSLCertificateFile and SSLCertificateKeyFile settings after the Debian package installation has completed. See the Installation Guide, chapter Service Configuration, section "SSL Certificate Configuration".

Same Origin Policy Disallows Reading the Remote Resource

This or some similar error may occur if you have set SITE_URL and SPEEDTEST_ADDRESS to different values in /etc/netrounds/netrounds.conf. You then need to change ALLOWED_ORIGINS in /etc/netrounds/restol.conf to allow both of these values in the restol.conf file. The simplest way to achieve this is to delete any value previously assigned to ALLOWED_ORIGINS. That setting will then get a default value which allows SITE_URL and SPEEDTEST_ADDRESS as found in /etc/netrounds/netrounds.conf.

Test Agent Appliance Does Not Come Online After Control Center Upgrade

If you upgrade Control Center 3.1 or 3.2 to version 3.3 or later and you are using Test Agent Appliance 3.3, it may happen that a Test Agent Appliance on which a Test Agent Application is run (this is supported from version 3.3.1 onward) will not come online but remain gray in Control Center. This is because traffic on port 6800 is filtered by a DROP rule.

Resolve this issue by running the following command on the Control Center machine: