Azure Startup Guide

The Aviatrix cloud network solution consists of two components, the controller and gateways, both of which are Azure VMs. Gateways are launched from the controller console to specific VNets. This guide helps you to launch the controller VM in Azure. Make sure you follow the instructions to also subscribe to the Aviatrix Companion Gateway described in this guide.

1. Subscribe to the Aviatrix Metered Offer

Go to Azure Marketplace to subscribe to Aviatrix Controller Meter License - PAYG.

Follow the Azure portal instruction to subscribe.

subscribe_to_meter

2. Subscribe to the Aviatrix Controller BYOL Offer

After you subscribe to Aviatrix Meter License offer, you should receive an email from admin@aviatrix.io to inform you with customer ID and a link to subscribe the actual Aviatrix Controller BYOL offer. More to continue on Step 4.

(Note with Aviatrix Meter License, you are billed monthly. No upfront cost and pay as you go.)

3. (Optional) Subscribe to an Aviatrix Companion Gateway

This step is not required for most of deployment scenarios as Aviatrix Controller automatically subscribes to the Aviatrix Companion Gateway when it is launched.

There are exceptional cases, such as if you provide Managed Service on Azure, the Aviatrix Companion Gateway requires manual subscription.

For manual subscription, follow the steps in this doc to subscribe.

4. Launch the Controller

Launch Controller VM from Azure marketplace portal

  1. Get from Azure Marketplace for the actual BYOL Controller.

    click_byol

  2. At Basics header, create new Resource Group titled “aviatrix”, virtual machine name can be “aviatrixController”. For instance size we recommend at least 8GB of RAM so B2ms should be sufficient. Next enter a username, password and Resource group, click OK. Please do NOT use ‘ubuntu’ as username if you use password as authentication type.

    Azure_Basics

  3. At the networking header, this will be preconfigured with a default subnet and security group. You should not need to change anything here. For Public IP, click Create New, at Assignment select Static and click OK.

    static_ip

  4. The management, advanced, and tag headers should not need any configuration.

  5. Finish launching the VM by hitting the create button.

  6. Find the VM’s public IP address, as shown below:

    VM

  7. Use a browser to access the controller VM. In this example, it is https://40.77.57.154

  8. At the login page, enter admin as the username. The Initial password is the internal IP address of the VM, as shown below.

    login

  9. Go through the login process.

  10. Start with the Onboarding tab at the console.

Warning

Any resources created by the Controller, such as Aviatrix gateways, Azure routing entries, subnets, etc, must be deleted from the Controller console. If you delete them directly on Azure console, The Controller’s view of the resources will be incorrect, which will lead to features not working properly.

5. Onboarding

The purpose of Onboarding is to help you setup an account on the Aviatrix Controller that corresponds to an Azure account with policies so that the Controller can launch gateways using Azure APIs.

Follow the instructions here to create an Aviatrix account that corresponds to your Azure account credential.

Note: you can create a single Aviatrix account that corresponds to AWS, Azure and GCloud account credentials. This is a multi cloud platform.

6. Gateway Troubleshoot

If the Controller fails to launch an Aviatrix gateway in Azure RM, check out this troubleshooting guide.

Enjoy!