1. Upgrade Guide
  2. Upgrading Session Monitor
  3. Upgrading Session Monitor

Upgrading Session Monitor

Note:

It is not possible to directly upgrade from Session Monitor version 3.3 to Session Monitor version 3.4 or later as versions 3.4 and 4.x are built on Oracle Linux, and version 3.3 is Debian-based. To upgrade from 3.3 to 3.4 or 4.x, a re-install is required.

To upgrade Session Monitor:

  1. Upgrade from Session Monitor release 3.3 to 3.4 or release 4.0 by referring to the Migration Guide provided in the 3.4, and 4.0 product documentation page on Oracle Help Center.

    With this migration procedure, you can perform an upgrade without losing historic calls/data.

  2. After upgrading to Session Monitor release 3.4/4.0, upgrade to Session Monitor release 4.3 either by PSA or ACLI.

    • Upgrading from Release 4.2 to Release 4.3 through PSA

    • Upgrading from Release 4.2 to Release 4.3 through ACLI

Upgrading from Release 3.4 to Release 4.3 through PSA

Note:

If an upgrade is performed from version 3.4, 4.0, or 4.2 to 4.3, upgrade time varies from 45 minutes to 3 or more hours based on the number of database rows in the "Calls" table. For such cases, upgrading from PSA is not recommended as PSA GUI has a timeout. You must follow the steps in "Upgrading from Release 3.4 to Release 4.1 through ACLI"

The following is an example of the time needed for upgrade based on the number of rows in the Calls table

On your ME, Execute : mysql vsp -e 'select count(*) from calls'; to find the number of rows in calls table.

If Number of rows in Calls Table ~= 100 Million, then time for upgrade is 45 minutes.

Upgrading from 4.2 Release to 4.3 won't be affected.

To upgrade from release 3.4 to release 4.3:

  1. Open the PSA page of the ME by entering the URL address in the web browser: https://<IPofME>/setup/

    Where, <IPofME> is IP address of the ME.

    Contact your Oracle Representative for credentials.

  2. Click browse and upload the software downloaded from Oracle,

    For Release 4.3, the software is an .rpm file.

  3. After the upload is complete, click Install.

  4. Accept the license agreement. The installation begins.

  5. (Optional) You will receive the following error message if there is no enough disk space.

    Cannot update. Not enough disk space. Please contact Support.

    To free up the space, refer to the Document 1937398.1 in the Customer Support website.

    The upgrade/installation may take 1 or more hours depending on the data on your machine. Once the installation gets completed, logout of the PSA page and re-login. Click Software Version from the right panel.

    Result: The upgraded version is shown as Release 4.3.0.0.0 on the machine.

  6. Run the following command after establishing an SSH session with the product. 

    source /opt/oracle/ocsm_env.sh
  7. Log out of the application GUI and log in again to access new features.

Upgrading from Release 3.4 to Release 4.3 through ACLI

Note:

This section provides an example procedure for upgrading Mediation Engine (ME). The Procedure for other machine types like Probe , and Mediation Engine Connector is same.

To upgrade Session Monitor from release 3.4 to release 4.3 through ACLI:

  1. Copy the RPM file ocsm-4.3.0.0.0-156.x86_64.rpm to the system.

  2. Set the correct environment by running the following command: 
    source /opt/oracle/ocsm/ocsm_env.sh
  3. Run the following command to stop all the services on Operations Monitor: 
    pld-systemctl stop
  4. Run the following command: 
    yum install ocsm-4.3.0.0.0-156.x86_64.rpm
  5. Run the following command to start all services. 
    pld-systemctl start
  6. The upgrade is complete. Run the following command to verify the Session Monitor software version: 
    cat /opt/oracle/ocsm/etc/iptego/display_version

    Result: The output should be latest Session Monitor version. For example, 4.3.0.0.0.

  7. Run the following command after establishing an SSH session with the product. 
    source /opt/oracle/ocsm/ocsm_env.sh
  8. Log out of the application GUI and log in again to access new features.

Upgrading DPDK

DPDK upgrade is required. Release 4.3 and above supports DPDK version 19.08 only.

To update DPDK:

  1. Follow the instructions in "Uninstalling DPDK"
  2. Follow the instructions in "Installing and Configuring DPDK with Internet" or "Installing and Configuring DPDK without Internet" based on setup below.
  3. Reboot the machine that hosts the probe, or mediation engine and probe.

Uninstalling DPDK

This section describes the instructions for uninstalling DPDK.

To uninstall DPDK:

  1. Run the following commands: 
    source /opt/oracle/ocsm/ocsm_env.sh
/opt/oracle/ocsm/usr/share/pld/rat/configure_dpdk.py --remove

Installing and Configuring DPDK with Internet

This section describes the procedure for installing and configuring DPDK for Session Monitor.

Note:

You must be connected to the internet before starting the installation. Running the following command installs, downloads the required files, and configures the DPDK automatically.
For DPDK installation, for Oracle X7-2 server has the following pre-requisite:
  1. Create a file, /opt/oracle/ocsm/etc/iptego/white_list_dpdk.local with the value i140e before triggering DPDK installation.
  1. Log into the Platform Setup Application page.
  2. Select Capture Settings.
  3. Check the box in Monitoring column against each sniffing interface that you want to use for capturing the traffic.
  4. Log into the machine that hosts the probe or mediation engine and probe as a root user.
  5. (Optional) For better understanding of the network, CPU, and NUMA nodes of the server, you can run the following command to review the output of the system_layout.py script. It will display system information: 
    source /opt/oracle/ocsm/ocsm_env.sh
/opt/oracle/ocsm/usr/share/pld/rat/system_layout.py
  6. Run the following commands which guides you through the installation: 
    source /opt/oracle/ocsm/ocsm_env.sh
/opt/oracle/ocsm/usr/share/pld/rat/configure_dpdk.py
    The configure_dpdk.py script downloads and installs the required DPDK driver, the corresponding Kernel headers required for compiling DPDK driver, compiles, installs the driver, and creates server and Session Monitor DPDK related configuration.
  7. (Optional) To view all the available advanced options, run the following command: 
    /opt/oracle/ocsm/usr/share/pld/rat/configure_dpdk.py -h

Installing and Configuring DPDK Without Internet

DPDK can be installed and configured without an internet connection.
  1. Log into the Platform Setup Application page.
  2. Select Capture Settings.
  3. Check the box in Monitoring column against each sniffing interface that you want to use for capturing the traffic.
  4. Log into the machine that hosts the probe or mediation engine and probe as a root user.
  5. (Optional) For better understanding of the network, CPU, and NUMA nodes of the server, run the system_layout.py script to display system information. 
    source /opt/oracle/ocsm/ocsm_env.sh
/opt/oracle/ocsm/usr/share/pld/rat/system_layout.py
  6. Run the following command: 
    yum install kernel-uek-devel-$(uname -r)
  7. Download the DPDK tar file from http://git.dpdk.org/dpdk/refs/ into the folder /var/cache/ocsm/dpdk/.
  8. Run the following commands as a root user: 
    source /opt/oracle/ocsm/ocsm_env.sh
/opt/oracle/ocsm/usr/share/pld/rat/configure_dpdk.py
  9. (Optional) To view all the available advanced options, run the following command: 
    /opt/oracle/ocsm/usr/share/pld/rat/configure_dpdk.py -h