Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

Create vEdge Cloud VM Instance on Azure

To start a software vEdge Cloud router, you must create a virtual machine (VM) instance for it. This article describes how to create a VM instance on Microsoft Azure. You can also create the VM on Amazon AWS or on a server running the vSphere ESXi Hypervisor software or the Kernel-based Virtual Machine (KVM) Hypervisor software.

Note: Viptela offers only a Bring Your Own License (BYOL) for the vEdge Cloud router, so you are not actually purchasing the Viptela product. You are charged hourly for the VNET instance.

For server requirements, see Server Hardware Recommendations.

Launch Azure Marketplace and Create a vEdge Cloud Router VM Instance

  1. Launch the Azure Marketplace application:
    1. In the left pane, click New to create a new vEdge Cloud router VM instance.
    2. In the Search box, search for Viptela.

  1. In the right pane, select Viptela vEdge Cloud Router (3 NICs) (Staged).

  1. In the Viptela vEdge Cloud Router (3 NICs) (Staged) screen, click Basics in the left pane to configure basic settings for the vEdge Cloud router VM:
    1. In the Viptela VM Name field, enter a name for the vEdge Cloud router VM instance.
    2. In the Username field, enter the name of a user who can access the VM instance.
    3. In the Authentication type field, select either Password or SSH public key.
    4. If you selected password, enter, and then confirm, your password. You use the username and password to open SSH session to the VM instance.
    5. If you selected SSH public key, see https://docs.microsoft.com/en-us/azu...reate-ssh-keys for instructions about how to generate an SSH key pair for Linux VMs.
    6. In the Subscription field, select Pay-As-You-Go from the drop-down menu.
    7. In the Resource Group field, click Create new to create a new resource group, or click Use existing to select an existing resource group from the drop-down menu.
    8. In the Location field, select the location in which you wish to bring up the vEdge Cloud router VM instance.
    9. Click OK.

  1. In the left pane, click Viptela vEdge Settings to configure the vEdge Cloud router infrastructure settings.

  1. In the Infrastructure Settings pane:
    1. Click Size. In the Choose a size pane, select D3_V2 Standard for the instance type and click Select. This is the recommended instance type.

  1. Click Storage Account. In the Choose storage account pane, click Create New to create a new storage account or select one of the listed storage accounts. Then click OK.

  1. Click Public IP Address. In the Choose public IP address pane, click Create New to create a new public IP address, or select one of the listed public IP address to use for the public IP subnet. Then click OK.

  1. In the Domain Name field, select vedge from the drop-down menu.
  2. Click Virtual Network. In the Choose virtual network pane, click Create New to create a new virtual network (VNET), or select an existing VNET to launch the vEdge Cloud instance in. Then click OK.

  1. If you selected an existing VNET, use the drop-down menu to choose available subnets within the VNET. Then click OK.

    You must have three subnets available within the VNET; otherwise, the vEdge Cloud router VM instance will fail to launch. Also, ensure that route tables associated with your VM subnets have a user-defined route (UDR) towards the service subnet of the vEdge Cloud router. The UDR ensures that the VM subnets use the vEdge Cloud router as the gateway. See the example topology below.

  2. If you created a new VNET, define the address space within that VNET. Then click OK in the Subnets pane.

    Viptela prepopulates subnet names and assigns IP addresses per subnet from the VNET address space you defined. If you plan to connect your VNET instances through the service subnet associated to the vEdge Cloud router, you do not need to make updates to the route table.

  1. In the Summary pane, click OK.The Summary pane validates and displays the configuration you defined for the vEdge Cloud router VM instance.

  1. Click Buy to purchase. Then click Purchase in the Purchase pane.

Note: Viptela offers only a Bring Your Own License (BYOL) for the vEdge Cloud router, so you are not actually purchasing the Viptela product. You are charged hourly for the VNET instance.

The system creates the vEdge Cloud router VM instance and notifies you that the deployment has succeeded.

  1. Click the vEdge VM instance you just created.

The system displays the public IP address and DNS name of the vEdge Cloud router VM instance.

  1. SSH into the public IP address of the vEdge Cloud router VM instance.

  1. At the login prompt, log in with the username and password you created in Step 3. To view the vEdge Cloud router default configuration, enter the following command:

vEdge# show running-config

When you create a vEdge Cloud router VM, the security group configuration shown below is applied to the NIC associated with the public subnet. This security group does not restrict traffic from specific sources, but it does restrict specific services. Custom services for TCP and UDP that need to be enabled for Viptela control protocols are also automatically configured. You can change the security group configuration to suit your requirements.

vEdge Cloud Router Interface and Subnet Mapping

To create a vEdge Cloud router VM instance on Azure Marketplace, a minimum of three NICs are required—one each for management, service, and transport. The table below shows the mapping of the vEdge Cloud router interface with the subnet associated to these NICs.

vEdge Cloud Router Interface Subnet Description
eth0 Management subnet In-band management
ge0/1 Service subnet Connects the vEdge Cloud router as a gateway device
ge0/0 Transport subnet Transport/WAN link
  • Was this article helpful?