Upgrading the cluster to KSMG 2.1

We strongly recommend to back up KSMG virtual machines (make a snapshot of the virtual machine in the hypervisor) of all cluster nodes before upgrading KSMG. This will let you go back to the previous version of KSMG if the installation of the new version fails.

Before upgrading using the KSMG web interface, you must download the ZIP archive with the upgrade package from the Kaspersky website or a partner company website and extract the KTGZ update file from the archive.

This sequence of steps lets you keep processing the traffic of the organization during the update process.

To update the application to version 2.1 in a cluster containing multiple nodes:

In the web interface of the Control node, go to the Nodes section and make sure that all cluster nodes are available and do not have errors.
If there is no access to the cluster node, or if errors are encountered on the node, resolve the problems before you start the update process.
Install upgrade packages on one of the Secondary nodes.
To upgrade KSMG to version 2.1 on the first of the cluster nodes that you are upgrading:
1. In the web interface of the Control node, go to the Message queue section, click Manage settings for sending/receiving, select the node for which you want to install the update, and disable the reception of messages on that node. For details, see Enabling and disabling the transmission and reception of messages.
2. In the table of messages in the queue, filter the messages by node then wait until messages from all queues are sent.
3. Remove the load from the node in the load balancer settings.
4. If you have edited KSMG settings in Technical Support Mode, run the script for detecting incompatible objects in the system. If necessary, delete or edit the detected objects.
  If unknown objects are detected on your computer during the upgrade, upgrade installation is stopped.
5. In the web interface of the node being upgraded, click Install patch and install the upgrade package: ksmg_upgrade_2.0.1.6960_2.1.0.7854.ktgz.
6. Wait for the web interface page to reload.
7. In the web interface of the updated node, in the lower part of the left menu pane, click the name of the current user, then select About and in the displayed window, make sure that the Version line displays 2.1.
8. In the web interface of the updated node, click Change role to Control node.
9. If necessary, transfer the saved configuration files of the operating system or built-in MTA that you copied before installing the update.
10. In the web interface of the new Control node:
  1. Update the databases.
  2. If a connection with the LDAP server was configured, update the LDAP cache.
    If a LDAP server connection was not configured, synchronize with an Active Directory domain controller.
    In the application web interface window, select the Settings → External services → LDAP server connections section.
    Select the Synchronization settings tab.
    In the Schedule drop-down list, select Manually.
    Click Save.
    Click Synchronize now.
  3. Turn on the reception and transmission of messages on all cluster nodes and click Apply.
  4. Turn off the reception of messages on all cluster nodes and click Apply.
  5. Turn on the reception of messages only on the updated node.
  6. Check if the messages can pass through the node. To do so, send a test message through the node and confirm if it was delivered to the recipient.
  7. Restore the load on the node in the load balancer settings.
The KSMG application on the cluster node is upgraded to version 2.1.
After installing the upgrade package, the node becomes inaccessible to other cluster nodes. In the web interface of this node, you need to assign it the role of the new Control node.
Install upgrade packages on each of the remaining Secondary nodes.
After the update, each Secondary Node will be accessible to the new Control Node and inaccessible to the old Control Node.
Install upgrade packages on the old Control node.
To upgrade KSMG to version 2.1 on the old Control node:
1. In the web interface of the previous Control node, go to the Message queue section, click Manage settings for sending/receiving, select the node for which you want to install the update, and disable the reception of messages on that node. For details, see Enabling and disabling the transmission and reception of messages.
2. Wait until messages from all queues are sent.
3. Remove the load from the node in the load balancer settings.
4. Go to the Nodes section and assign the Secondary node role to the node.
5. If you have edited KSMG settings in Technical Support Mode, run the script for detecting incompatible objects in the system. If necessary, delete or edit the detected objects.
  If unknown objects are detected on your computer during the upgrade, upgrade installation is stopped.
6. In the web interface of the node, install the upgrade package: ksmg_upgrade_2.0.1.6960_2.1.0.7854.ktgz.
7. Wait for the web interface page to reload.
8. In the web interface of the updated node, in the lower part of the left menu pane, click the name of the current user, then select About and in the displayed window, make sure that the Version line displays 2.1.
9. If necessary, transfer the saved configuration files of the operating system or built-in MTA that you copied before installing the update.
10. In the web interface of the new Control node:
  1. Update the databases.
  2. If a connection with the LDAP server was configured, update the LDAP cache.
    If a LDAP server connection was not configured, synchronize with an Active Directory domain controller.
    In the application web interface window, select the Settings → External services → LDAP server connections section.
    Select the Synchronization settings tab.
    In the Schedule drop-down list, select Manually.
    Click Save.
    Click Synchronize now.
  3. Turn on the reception of messages on the node with the updated program.
  4. Check if messages can pass through. To do so, send a test message through the node and confirm if it was delivered to the recipient.
  5. Restore the load on the node in the load balancer settings.
As a result, the KSMG application on the cluster node is upgraded to version 2.1.
Before installing the update, you must assign the Secondary node role to it in the web interface of this node.
Return the Control node role to the previous Control node.

As a result, all cluster nodes are upgraded to KSMG version 2.1 and are accessible from the new Control node.

Page top