Network settings modification scenario for a subset of the nodes

The administrator must ensure network connectivity between nodes with new and old addresses.

Scenario for modifying the network settings of a subset of cluster nodes involves the following steps:

1. Changing the role of a node from Control to Secondary

   You must carry out this step if the Control node is in the subset of nodes for which you want to change addresses. Temporarily assign the Control node role to a node for which you are not planning to change the address.

2. Disabling mail traffic processing on selected nodes

   If you are using a load balancer, in balancer settings, turn off the load for nodes whose addresses you are planning to change. If you are not using a load balancer, in the web interface of Kaspersky Secure Mail Gateway, disable the reception of messages for the selected nodes.

   After turning off the load, wait until messages from all queues are completely sent on the selected nodes.

3. Changing the addresses of Secondary nodes

   Change the addresses of selected Secondary nodes, one by one. To do so, on each node:

   1. Modify the network settings of the Secondary node in Technical Support Mode.

      You can modify the network settings of the operating system, IP addresses of network adapters, the default gateway address, DNS server addresses.

   2. Test the network settings of the operating system on the node.

      This step lets you make sure that the new network settings are in fact applied.

   3. Modify the A and PTR records on the DNS server for the Secondary node to match the new IP address and domain name of the node.

      This is necessary for correct functioning of Kerberos authentication with the Single Sign-On technology and for interaction with other mail systems.

   4. Change the address of the node in the program in Technical Support Mode

      This step is necessary if the IP address or port of the node was modified.

4. Replacing Secondary nodes with the old addresses with Secondary nodes with the new addresses in the cluster using the program web interface

   Nodes that had their address changed must be removed from the cluster; these nodes must then be added to the cluster with the new addresses.

5. Changing the role of a node from Secondary to Control

   This step is necessary is the Control node role was temporarily assigned to a different node.

6. Checking the availability and health of all cluster nodes

   You can view the statuses of cluster nodes in the web interface of the Control node.

7. Enabling mail traffic processing on nodes

   Enable mail traffic processing on cluster nodes with new addresses, one after another. Make sure that traffic is being processed without errors.