This section describes the steps to migrate an existing deployment to accelerated networking.

The Accelerated Networking (AN) feature in Microsoft Azure facilitates high network performance with minimum latency. The Avi Load Balancer supports accelerated networking for a SE group for Microsoft Azure cloud. All SE groups created on Avi Load Balancer have this option enabled by default.

You cannot enable this option on an existing SE group having SEs without accelerated networking. Microsoft Azure does not support a combination of virtual machines with accelerated networking enabled and disabled in the same availability set.

Migrating to Accelerated Networking

To migrate an existing deployment to accelerated networking:

  • Create a new SE group

  • Migrate all the virtual services associated with the previous SE group to this new SE group.

Virtual Services are migrated to the new SE group using either or both of the following methods:

  • Modifying the SE group of the Virtual Services.

  • Cloning Virtual Services to the new SE group having accelerated networking enabled.

Modifying SE Group of Virtual Services

This method preserves the IP addresses of the virtual services, and all the analytics history associated with them. This method causes downtime for the virtual service, when the virtual service is moved from one Azure Load Balancer to another.

Cloning Virtual service to the New SE Group

Once the new virtual services are up and running in the new SE group, switch the DNS and delete the previous virtual services. This method does not require any downtime but requires a new set of IP addresses for the virtual services. It also works if DNS is managed outside of the Avi Load Balancer Controller.

Follow the steps mentioned below to clone a virtual service from one SE group to another.

Note:

Before cloning of virtual services, disable periodic cloud reconcile for the cloud. This is to avoid any interruption to the cloned virtual services due to the reconcile run by Avi Load Balancer cloud connector. Run the no cloud_reconcile command under the configure controller properties mode to disable reconcile for the cloud.

[admin:cntrl1]: > configure cloudproperties
[admin:cntrl1]: cloudproperties> no cloud_reconcile
[admin:cntrl1]: cloudproperties> save

Once reconcile is disabled for the cloud, run the following script to create clones of the virtual services. These virtual services will share the pools with their respective virtual services where they are cloned from.

Note:

The clone_vs_segroup.py script required for Acclerated Networking is available in the Avi Load Balancer Controller package. It is available under /opt/avi/scripts/ directory on the Avi Load Balancer Controller.

usage: clone_vs_segroup.py [-h] [-c CONTROLLER] [-u USER] [-p PASSWORD]
[-x API_VERSION] [-C CLOUD] [-t TENANT] [-e]
[-f FROMSEGROUP] [-d TOSEGROUP] [-s SUFFIX] [-n]

optional arguments:
-h, --help      show this help message and exit
-c CONTROLLER, --controller CONTROLLER
                FQDN or IP address of Avi Vantage Controller
-u USER, --user USER Avi Vantage username
-p PASSWORD, --password PASSWORD
                Avi Vantage password
-x API_VERSION, --api_version API_VERSION
                Avi Vantage API version (default=17.2.14)
-C CLOUD, --cloud CLOUD
                Cloud name
-t TENANT, --tenant TENANT
                Tenant name
-e, --enable    Enable the cloned Virtual Service
-f FROMSEGROUP, --fromsegroup FROMSEGROUP
                Source SE group
-d TOSEGROUP, --tosegroup TOSEGROUP
                Destination SE group
-s SUFFIX, --suffix SUFFIX
                suffix to be added to virtual service names
-n, --dryrun    Dry run mode. Only json files of all the objects will be created, no changes will be done to Avi Controller.