Accelerated Networking Support for Azure Cloud
Acclerated Networking (AN) feature in Microsoft Azure facilitates high network performance with minimum latency. Using this feature performance for load balancing, DNS/GSLB, and WAF features is improved considerably.
Starting with Avi Vantage release 17.2.14, Accelerated Networking is supported for a Service Engine group for Microsoft Azure cloud. By default, all SE groups created on Avi Vantage release 17.2.14 have this option enabled.
The following are the few considerations while deploying Accelerated Networking:
- This option cannot be enabled 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.
By default, all the SE groups created in Avi Vantage release 17.2.14 and later releases will have Accelerated Networking enabled. 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
This section covers the following points:
- Disabling cloud reconcile
- Running the script for cloning of virtual services
- Enabling cloud reconcile
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 Controller.
Follow the steps mentioned below to clone a virtual service from one SE group to another.
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 cloud connector.
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 Controller package.
It is available under
/opt/avi/scripts/ directory on the Avi 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.
Once cloning of virtual services is complete, follow the
enable cloud-reconcile command to re-enable reconcile.
[admin:cntrl1]: > configure cloudproperties [admin:cntrl1]: cloudproperties> enable cloud_reconcile [admin:cntrl1]: cloudproperties> save