Kaspersky Anti Targeted Attack Platform

Installing the application upgrade package to version 6.0.4

Before installing the application upgrade package, it is recommended to first create a backup of the current state of each Central Node server to be updated and download it to the hard drive from the application administrator menu. If an error occurs during installation of an application upgrade package or if you need to reinstall Kaspersky Anti Targeted Attack Platform, you can use your backup copy of the application.

The upgrade is delivered as an upgrade package. The package is included in the application distribution kit.

The 6.0.4 application upgrade package is installed on the Central Node, Sensor (if the component is not installed on the same server as Central Node) and Sandbox 6.0.2 servers. Installation of the upgrade package on the Central Node and Sensor servers depends on the way the application is deployed and used:

  • If you are using the distributed solution and multitenancy mode, you must install the upgrade package on each Central Node and Sensor server installed on standalone servers. You do not need to disconnect the SCN servers from the PCN to install the upgrade package.
  • To install the update on Central Node servers that are part of a high availability cluster, you must follow special steps that are described below.
  • In other cases, to install the update package, you must connect to each Central Node and Sensor server

    over SSH or through the terminal

    and log in to the management console. You do not need to disconnect Sandbox and Sensor from the Central Node to install the upgrade package.

To install the update package on Central Node deployed as a cluster:

  1. Enter the management console of any cluster server over SSH or using a terminal.
  2. Find out which servers in the cluster have the 'manager' role by running the following commands:

    sudo -i

    docker node ls

    A list of cluster servers is displayed. Look at the MANAGER STATUS column in the list: if a server has Leader or Reachable in that column, it means it has the 'manager' role.

  3. Log in to the management console of any of the 'manager' servers over SSH or using a terminal.
  4. Place the component upgrade package, upgrade-6.0.4.tar.gz, in the /tmp directory. If the function of network traffic saving is enabled, make sure that the amount of free disk space is more than 100 GB.
  5. Raise the privileges of the user by running the following command:

    sudo -i

  6. Unpack the upgrade archive:

    tar xvf /tmp/upgrade-6.0.4.tar.gz -C /tmp/

  7. Install the upgrade package by running the following commands:

    cd /tmp

    chmod +x ./install.sh

    ./install.sh server

  8. Copy the upgrade-6.0.4.tar.gz package to the /tmp directory on each worker server in the cluster.
  9. Enter the management console of any worker server over SSH or using a terminal.
  10. Raise the privileges of the user by running the following command:

    sudo -i

  11. Unpack the upgrade archive:

    tar xvf /tmp/upgrade-6.0.4.tar.gz -C /tmp/

  12. Install the upgrade package by running the following commands:

    cd /tmp

    chmod +x ./ks_patch.ks.sh

    ./ks_patch.ks.sh

  13. Repeat steps 9 to 12 for each worker server in the cluster.
  14. Make sure the application setup log contains a check_klava record in the 'after' section. To view the log, run the following command:

    cat /tmp/ks_check_klava_patch.log

    The log is updated every minute. If the entry is missing from the log or the log file does not exist, please contact Technical Support.

The upgrade package will be installed.

To install the upgrade package on Central Node installed on a server:

  1. Place the component upgrade package, upgrade-6.0.4.tar.gz, in the /tmp directory on the server. If the function of network traffic saving is enabled, make sure that the amount of free disk space is more than 100 GB.
  2. Log in to the management console of the server on which you want to install the upgrade package

    over SSH or through the terminal.

  3. Unpack the upgrade archive:

    tar xvf /tmp/upgrade-6.0.4.tar.gz -C /tmp/

  4. Raise the privileges of the user by running the following command:

    sudo -i

  5. Install the upgrade package by running the following commands:

    cd /tmp

    chmod +x ./install.sh

    ./install.sh server

    chmod +x ./ks_patch.ks.sh

    ./ks_patch.ks.sh

  6. Make sure the application setup log contains a check_klava record in the 'after' section. To view the log, run the following command:

    cat /tmp/ks_check_klava_patch.log

    The log is updated every minute. If the entry is missing from the log or the log file does not exist, please contact Technical Support.

    The upgrade package will be installed.

To install the upgrade package on the Sensor server:

  1. Place the component update package, upgrade.tar.gz, in the /tmp directory on the server. If the function of network traffic saving is enabled, make sure that the amount of free disk space is more than 100 GB.
  2. Sign in to the management console of the server where you want to install the upgrade package via the SSH protocol or through the terminal.
  3. Make sure that the /dev/sda2 file system has more than 100 GB of free space.
  4. Unpack the upgrade package by running the tar xvf /tmp/upgrade.tar.gz -C /tmp/ command.
  5. Raise the privileges of the user by running sudo -i.
  6. Install the upgrade package by running the following commands:

    cd /tmp/upgrade/

    chmod +x ./install.sh

    ./install.sh sensor

The upgrade package is installed on the Sensor server.

To install the upgrade package on the Sandbox server:

  1. Place the Sandbox component update package, upgrade.tar.gz, in the /tmp directory on the server.
  2. Sign in to the management console of the server where you want to install the upgrade package via the SSH protocol or through the terminal.
  3. Install the upgrade package by running the following commands:

    cd /tmp

    chmod +x ./install.sh

    ./install.sh sandbox

  4. Wait for the upgrade package to install successfully.

The upgrade package is installed on the Sandbox server.