Sipmon Documentation

Appearance

import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';

When updating from version < 18.10 to a version >= 18.10, you need to

  • Retrieve a new license from Sipmon support
  • Make sure your Sipmon MBI server is based on CentOS/RH 7. You may use the following procedure to migrate your server: Migrate your reporting server

The upgrade of Sipmon MBI consists of 4 steps :

  • Updating the repository
  • Updating the extension interface
  • Updating the reporting server
  • Updating the MariaDB database

Prerequisites ​

Upgrade your central server ​

See Introduction to upgrade.

Update the RPM signing key ​

On EL7/8, for security reasons, the keys used to sign Sipmon RPMs are rotated regularly. The last change occurred on October 14, 2021. When upgrading from an older version, you need to go through the key rotation procedure, to remove the old key and install the new one.

Step 1: Update the repository ​

When you upgrade from a previous major version to 22.10.x, you first need to update the repository on your Central & Reporting servers.

You will find the new "Business" repository on the "Repositories" page in your Sipmon Support account.

Step 2: Upgrade the extension interface ​

  1. Update the package, run the following commands:
  1. Update through the interface: Log on to the Sipmon web interface, go to Administration > Extension > Manager and click on the Update button to update the extension and the widgets.

Step 3: Upgrade the reporting server ​

Java version requirement ​

Ensure a version of Java 17 (or 18) is installed before you start the procedure.

  • If you need to check the Java version, enter the following command:
shell
java -version

  • If you need to upgrade the Java installation to Java 17 (or 18), go to the Oracle official download page.

  • If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 17 (or 18) version:

shell
sudo update-alternatives --config java

Then restart the service:

shell
systemctl restart cbis

Upgrade procedure ​

Now you can start the upgrade process:

  1. Connect to your reporting server and stop the scheduler service (CBIS):

    shell
    systemctl stop cbis

  2. Then run the following commands:

  1. Start the scheduler service:

    shell
    systemctl start cbis

  2. Start and enable gorgoned:

    shell
    systemctl start gorgoned && systemctl enable gorgoned

Step 4: Upgrade the MariaDB database ​

  1. Stop the cbis service:

    shell
    systemctl stop cbis

  2. See Upgrading MariaDB.

  3. Start the cbis service:

    shell
    systemctl start cbis