Network settings modification scenario for all nodes

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

1. Disabling mail traffic processing on all cluster nodes

   If you are using a load balancer for email traffic, in load balancer settings, remove the load from the nodes. If you are not using a load balancer, use your mail server or firewall functionality to stop receiving email messages.

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

2. Changing the address of the Control node

   To do so, on the Control node:

   1. Change the network settings using your operating system tools: IP addresses of network adapters, network routes, addresses of DNS servers, domain name of the node.
   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 Control 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 node address for machine-to-machine communication.

      Perform this step if you have changed the IP address of the network adapter that was used for machine-to-machine communication, or if you want to change the port number for the machine-to-machine communication.

3. Removing Secondary nodes from the cluster

   Log in to the web interface of the Control node using the new address and remove all Secondary nodes from the cluster.

   If the cluster contains a single node, skip this step and go to step 6.

4. Changing the addresses of Secondary nodes

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

   1. Change the network settings using your operating system tools: IP addresses of network adapters, network routes, addresses of DNS servers, domain name of the node.
   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 node address for machine-to-machine communication.

      Perform this step if you have changed the IP address of the network adapter that was used for machine-to-machine communication, or if you want to change the port number for the machine-to-machine communication.

5. Adding Secondary nodes to the cluster

   Use the new address of the Control node to log in to the web interface and add Secondary nodes with the new addresses to the cluster.

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 the reception of messages on cluster nodes under their new addresses, one by one. Make sure that traffic is being processed without errors.

Page top