Skip to main content
Version: ✨ 24.10

Upgrade from i-Vertix 4.2

info

This guide requires your system to be on version 4.2. If you need to upgrade from an older version, please contact us via support@i-vertix.com.

Prerequisites​

warning

Before attempting any upgrade, please make sure to create a snapshot or a backup of your i-Vertix Central Virtual Machine and any other Machine involved.

To upgrade the systems, a stable internet connection is required on the Central and on each Poller.

Upgrade Central Server​

Prepare the Upgrade​

Start by logging in the system using ssh. The user needs to be able to run commands with sudo.

Install the automated upgrade scripts with following command:

sudo dnf install ivertix-ansible-playbooks

dnf install

Perform Upgrade Step 1​

Launch the first step of the Central system upgrade with following command:

sudo ansible-playbook /opt/i-vertix/scripts/ansible/upgrade-central-42-to-43-step1.yaml

ansible first step

Since the scripts upgrade the entire system and download many packages, the process may take up to 45 minutes or longer, depending on the hardware resources and the internet connection of the Central Monitoring server.

Perform Application Upgrade​

After the first upgrade step is complete you need to perform the application upgrade.

Upgrade Wizard​

Open the Monitoring Interface in your Browser and step through the displayed upgrade wizard.

note

You must be logged out to access the wizard.

Application Upgrade Wizard

webui_1 webui_2 webui_3 webui_4 webui_5

Update Modules​

Then, login with an administrator account and navigate to AdministrationExtensionsManager.

Click the Update all button to update all installed Modules. The modules are updated simultaneously, it may take some time until every module is updated.

extensions update

After the updates are complete, every module should turn green (up-to-date).

extensions update final

Perform Upgrade Step 2​

Return to the Central's CLI and run the next upgrade script:

sudo ansible-playbook /opt/i-vertix/scripts/ansible/upgrade-central-42-to-43-step2.yaml

ansible 2

Perform Upgrade Step 3​

After Step 2 is finished, we need to upgrade the MariaDB database.

The procedure varies depending on whether the database is embedded (i.e. located on Central server) or deployed on a remote server. See Remote Database Management architecture for more details.

In cases where the database is deployed on the same host as the monitoring application, run:

sudo ansible-playbook /opt/i-vertix/scripts/ansible/upgrade-central-42-to-43-step3.yaml

ansible 3

Finalize Upgrade​

Reboot the Central server using following command:

sudo reboot
tip

It is strongly suggested to clean the Browser cache before logging in again to avoid errors on the web application.

Upgrade Pollers​

Perform Automatic Upgrade​

To upgrade all Pollers, we need to run the following command in the Central server CLI:

sudo ansible-playbook /opt/i-vertix/scripts/ansible/upgrade-poller-42-to-43.yaml

By default, the automated script will upgrade 5 pollers simultaneously until every single configured poller is upgraded.

You can also upgrade a single Poller by adding the option -l <poller name>:

sudo ansible-playbook /opt/i-vertix/scripts/ansible/upgrade-poller-42-to-43.yaml -l Poller1

Verify Poller Upgrade​

To verify that the pollers are working after the upgrade, log in to the monitoring system with an administrator account and navigate to ConfigurationPollers.

Pollers

Check the following properties:

  • 1 is the poller running?
  • 2 is the poller sending data to the central monitoring server?
  • 3 is the poller updated to the new major version (24.10)?

If the poller is not running, check the upgrade log for any errors. You can also try to export the monitoring configuration to the poller. When doing so, make sure to select Restart instead of Reload for the Restart Monitoring Engine option.

note

Each Poller may take some time to send the collected monitoring data after the system upgrade.

If not every 2 Last Update is up-to-date during your initial check, wait a few minutes and verify again. By then, all data should be synced.