Adding, modifying, and deleting IP addresses of KATA servers

The procedure of adding, modifying, and deleting IP addresses depends on the number of KATA servers.

Integration with a single KATA server

To modify the IP address of the server:

1. In the KSMG web interface, select Settings → External services → KATA Protection.
2. Select the Settings tab and under KATA server, click Change.

To delete the IP address of the server:

1. In the KSMG web interface, select Settings → External services → KATA Protection.
2. Select the Settings tab and under KATA server, click Delete.

Integration with multiple KATA servers

Only applicable when integrating with KATA 5.0 or a later version.

The procedure for adding, modifying, and deleting KATA server addresses depends on the method of specifying addresses chosen at the stage of preparing the configuration file of the local balancer:

• The domain name is used to obtain KATA server addresses.

  To modify or delete KATA server addresses,

  publish the relevant changes on the DNS server.

  The local balancer will detect and apply the published changes within 5 minutes. Restarting the service manually is not necessary.

  After making modifications, it is recommended to check KATA server connection status in the command shell of the operating system on each cluster node using the KATA integration monitoring script.

• IP addresses of KATA servers are specified in the configuration file.

  To modify or delete KATA server addresses:

  1. Connect to the cluster node over SSH to gain access to the Technical Support Mode.
  2. Make a backup copy of the built-in balancer configuration file.

     cp -p /etc/haproxy/haproxy.cfg /etc/haproxy/haproxy.cfg.backup

     In case of problems, you will be able to restore the configuration file from backup using the following command:

     cp -p /etc/haproxy/haproxy.cfg.backup /etc/haproxy/haproxy.cfg

  3. Open the configuration file of the built-in balancer (/etc/haproxy/haproxy.cfg) in a text editor and edit the backend section or replace the file with a prepared modified version.
  4. Restart the built-in balancer service:

     systemctl restart haproxy

  5. Check the status of the built-in balancer service:

     systemctl status haproxy

     The status must be running.

  6. Check the KATA server connection status using the KATA integration monitoring script.
  7. Repeat steps 1 to 6 on each cluster node.