Upgrading the Central Node component

You can upgrade the component to version 5.1 only from version 5.0. If you are using an older version, you must upgrade it to 5.1 in the following order: 3.7 → 3.7.1, 3.7.1 → 3.7.2, 3.7.2 → 4.0, 4.0 → 4.1, 4.1 → 5.0.

If you are using the distributed solution and multitenancy mode, you must prepare the PCN and SCN servers for the upgrade. For more details on the preparation procedure, see the Updating Kaspersky Anti Targeted Attack Platform section.

Operation mode in which Kaspersky Anti Targeted Attack Platform is used to protect the infrastructure of multiple organizations or branch offices of the same organization simultaneously.

Two-level hierarchy of servers with Central Node components installed. This hierarchy allocates a primary control server (Primary Central Node (PCN)) and secondary servers (Secondary Central Nodes (SCN)).

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

To upgrade the Central Node component:

1. Place the application upgrade package on the server with the Central Node component in the /data/upgrade directory.

   If you want to upgrade a component deployed as a cluster, you can place the upgrade package on any server in the cluster.

2. Sign in to the management console of the Central Node server where you want to upgrade the component via SSH or through the terminal.
3. Unpack the upgrade package by running the following command: tar xvf ./upgrade.tar.gz.
4. Install the upgrade package by running the following commands:
   1. chmod +x /data/upgrade/install_kata_upgrade.sh
   2. /data/upgrade/install_kata_upgrade.sh
5. Install the upgrade by running the following command: kata-upgrade --data-dir /data/upgrade --user admin --password <password set when installing the component>.

   If the password contains special characters, the password variable must be specified in the following format: --password '<password>'.

The Central Node component is upgraded.

After updating the component, you must log in again to the Central Node server management console over SSH or through the terminal.