Creating and preparing a new Secondary cluster node

To create and prepare a new Secondary node:

  1. Create a virtual machine for the new cluster node.

    The number of virtual CPUs, amount of RAM, and hard disk size must match the same settings of the virtual machines of existing cluster nodes. For other settings of the virtual machine, use the values from the table for the specific hypervisor.

  2. Perform the initial configuration of the application.

    When configuring network settings for the first replacement node, use the IP address and domain name that you reserved and prepared in the previous step. For the second and subsequent replacement nodes, use the freed up IP addresses and domain names from decommissioned nodes.

  3. Add the new node to the cluster.
  4. Make sure the status of the new node includes license information and does not contain any licensing errors.
  5. Run a database update manually.

    When the database update is complete, make sure that the status of the node does not contain any errors related to the database update.

  6. If you have LDAP connections, manually start the synchronization with domain controllers.

    Once the synchronization with the domain controllers is complete, make sure that the status of the node does not contain any errors related to LDAP connections.

  7. If you have connections to external services (KPSN, KATA), make sure that the status of the node does not contain any errors related to the connection to these services.
  8. If necessary, install the national root certificates package on the new cluster node.
  9. Install the required update packages with bug fixes for Kaspersky Web Traffic Security on Rocky Linux by following the instructions of Technical Support.
  10. If you need to work with the application using the SNMP protocol, configure the snmpd service on the new cluster node.
  11. If you are using the SIEM event publication functionality, configure event publishing on the new cluster node.
  12. If necessary, make changes to the configuration file templates of the built-in proxy server and to the configuration of other operating system services, as agreed with Technical Support.
  13. Restart the new node.
  14. After restarting, make sure that there the status of the node does not contain any errors.
Page top