Replacement of a failed controller node

You can deploy a new controller node to replace a controller node that has failed beyond repair. If a controller node fails while in a cluster with other nodes, the new controller node is automatically added to that cluster and synchronized with the existing nodes.

Before running this script, make sure that the IP address of the virtual machine or physical server on which you are deploying the new controller node is the same as the IP address of the virtual machine or physical server where the failed controller node was deployed. You specified the IP addresses of the virtual machines or physical servers for deployment of controller nodes when you deployed the solution, in the ctl section of the configuration file.

The scenario for replacing a failed controller node involves the following steps:

1. Preparing the administrator device

   Prepare the administrator device for deployment of the new controller node. You can use a local or remote virtual machine, or a personal computer as the administrator device. When deploying a Kaspersky SD-WAN testbed in accordance with the all-in-one deployment scenario, you must use a virtual machine as the administrator device.

2. Ensuring network connectivity between the administrator device, solution components, and the new controller node

   Ensure network connectivity between the administrator device, solution components, and the virtual machine or physical server on which you want to deploy the new controller node. You must make sure that the links between virtual machines or physical servers satisfy the hardware and software requirements.

   The virtual machine physical server must be deployed in a trusted network segment to avoid compromising the transmitted traffic.

3. Deploying a controller node

   Do the following on the administrator device:

   1. Accept the End User License Agreement by running the following command:

      export KNAAS_EULA_AGREED="true"

   2. Go to the directory with the extracted installation archive.
   3. If you want to deploy the new controller node in attended mode, do one of the following:
      • If you have generated passwords manually while deploying the solution, run the following command:

        ansible-playbook -i inventory/generic -e "@<path to configuration file>" -e "@inventory/external/images.yml" -K --ask-vault-pass knaas/knaas-install.yml

        When running the command, enter the root account password and the generated master password.

      • If you have not generated passwords manually while deploying the solution, run the following command:

        ansible-playbook -i inventory/generic -e "@<path to configuration file>" -e "@inventory/external/images.yml" -K knaas/knaas-install.yml

   4. If you want to deploy the new controller node in unattended mode, do one of the following:

      We recommend using this mode only in a trusted environment, because otherwise hackers may intercept your passwords.

      • If you have generated passwords manually while deploying the solution, run the following command:

        ansible-playbook -i inventory/generic -e "@<path to configuration file>" -e "@inventory/external/images.yml" -e "ansible_become_password=yourSudoPassword" --vault-password-file ./passwords/vault_password.txt knaas/knaas-install.yml

      • If you have not generated passwords manually while deploying the solution, run the following command:

        ansible-playbook -i inventory/generic -e "@<path to configuration file>" -e "@inventory/external/images.yml" -e "ansible_become_password=yourSudoPassword" knaas/knaas-install.yml

The new controller node is deployed to replace the failed controller node. A successful deployment message is displayed in the console of the administrator device.

If a network connectivity problem occurs with a virtual machine or physical server while deploying the controller node, an error is displayed in the console of the administrator device, and the new controller node is not deployed. In that case, you need to restore network connectivity, clean up the virtual machine or physical server, and then run the deployment command again.

See also About the attended, unattended, and partially attended action modes

Page top