Upgrading Kaspersky SD-WAN

To upgrade Kaspersky SD-WAN:

  1. Download the knaas-installer_<version information> installation archive from the root directory of the distribution kit and extract the installation archive on the administrator device.
  2. Set up the configuration file in accordance with the changes that have been made to the new version of Kaspersky SD-WAN. You can view the changes in the in the CHANGELOG.md file in the root directory of the installation archive.

    When upgrading Kaspersky SD-WAN, make sure that you keep the files with passwords and SSL certificates.

  3. Upgrade Kaspersky SD-WAN in one of the following ways:
    • If you want to upgrade the solution in attended mode:

      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 password of the root account on the administrator device and the generated master password.

    • If you want to upgrade the solution in partially attended mode:

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

      Enter the root password o the administrator device when running the command.

    • If you want to upgrade the solution in unattended mode:

      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

The Kaspersky SD-WAN components are upgraded on the virtual machines that you specified in the configuration file. A successful upgrade message is displayed in the console of the administrator device.

If a network connectivity issue occurs with one of the virtual machines during the upgrade of solution components, an error message is displayed in the administrator device console, and the solution is not upgraded. In that case, you need to restore network connectivity and then run the upgrade command again.

After upgrading the solution, you need to clear your Bash command history.

See also

About the attended, unattended, and partially attended action modes

Page top