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

Cloud OnRamp with Azure

Use the Cloud OnRamp screen to create transit virtual networks (VNets) for hosting vEdge Cloud router instances in different Azure locations in the public internet. A Cloud OnRamp setup comprises three components:

  • A transit VNet, which connects a Viptela overlay network to one or more cloud-based applications.
  • A host VNet, which is where cloud-based applications reside.
  • The connections, or mappings, between the transit VNet and one or more host VNets.

Screen Elements

  • Top bar—On the left are the menu icon, for expanding and collapsing the vManage menu, and the vManage product name. On the right are a number of icons and the user profile drop-down.
  • Title bar—Includes the title of the screen, Cloud OnRamp.
  • Add New Cloud Instance—Click to create a Cloud OnRamp VNet instance using the cloud instance configuration wizard.
  • Cloud OnRamp Dashboard—Displays after you add at least one cloud instance.
    • VNet panes—Located on the Cloud OnRamp Dashboard, directly under the Add New Cloud Instance button, is a pane for each VNet that has been created. For each VNet, the pane shows:
      • Credential value for the VNet
      • Name of the VNet
      • Type of VNet
      • Number of up and down connections for mapped host VNets
      • Number of up and down connections for transit VNets

G00522.png

Create a Cloud Instance

  1. Click Add New Cloud Instance:

    G00525.png
     
  2. In the Add Cloud Instance–Log In to a Cloud Server popup:
    1. In the Cloud drop-down, select the cloud type to be Azure.
    2. To give vManage programmatic access to your Azure Subscription, log in to the cloud server:
      1. In the Subscription ID field, enter the ID of the Azure subscription you want to use as part of the Cloud onRamp workflow.
      2. In the Client ID field, enter the ID of an existing application or create a new application in Azure. To create a new application, go to your Azure Active Directory ► App Registrations ► New Application Registration.
      3. In the Tenant ID field, enter the ID of your Azure account. To find the tenant ID, go to your Azure Active Directory and click Properties.
      4. In the Secret Key field, enter the password associated with the client ID.
  3. Click Log In.
    The cloud instance configuration wizard opens. This wizard consists of three screens that you use to select a location and discover host VNets, add transit VNet, and map host VNets to transit VNets.
    A graphic on the right side of each wizard screen illustrates the steps in the cloud instance configuration process. Steps not yet completed are shown in light gray. The current step is highlighted within a blue box. Completed steps are indicated with a green checkmark and are shown in light orange.

    G00479.png
  4. Select a location and discover host VNets:
    1. In the Choose Location drop-down, select a geographical location.
    2. Click Discover Host VNets. A list of host VNets discovered in that location is displayed.
    3. Select the desired VNet.
    4. Click Next.
  5. Add a transit VNet:
    1. In the Transit VNet Name field, type a name for the transit VNet. The name can be up to 32 characters and can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens (–), and underscores (_). It cannot contain spaces or any other characters.
    2. Under Device Information, enter information about the transit VNet:
      1. In the WAN Edge Version drop-down, select the Viptela software version to run on the VNet transit. The drop-down lists the published versions of the Viptela software in the Azure marketplace.
      2. In the Size of Transit VNet drop-down, select how much memory and how many CPUs to create on the VNet transit.
      3. In the Device 1 drop-down, select the serial number to use.
      4. In the Device 2 drop-down, select the serial number to use.
      5. Click Advanced if you wish to enter more specific configuration options.
      6. In the Transit VPC Subnet field, enter a custom CIDR that has a network mask in the range of 16 to 25. If you choose to leave this field empty, the Transit VPC is created with a default CIDR of 10.0.0.0/16.
    3. Click Next.
  6. Map the host VNets to transit VNets:
    1. In the table of host VNets, select the desired host VNet.
    2. Click Map VNets. The Map Host VNets popup opens.
    3. In the Transit VNet drop-down, select the transit VNet to map to the host VNets.
    4. In the VPN drop-down, select the VPN in the overlay network in which to place the mapping.
    5. In the IPSec Tunnel CIDR section, enter two pairs of interface IP addresses for each vEdge Cloud router to configure IPSec tunnels to reach the Azure virtual network transit. The IP addresses must be network addresses in the /30 subnet, be unique across the overlay network, and not be a part of the host VNet CIDR. If they are part of the host VNet CIDR, Azure will return an error while attempting to create VPN connections to the transit VNet.
    6. In the Azure Information section:
      1. In the BGP ASN field, enter the ASN that will be configured on the Azure Virtual Network Transit that is spun up within the host VNet. Use an ASN that is not part of an existing configuration on Azure. For acceptable ASN values, refer to Azure documentation.
      2. In the Host VNet Gateway Subnet field, enter a host VNet subnet in which the Virtual Network Gateway can reside. It is recommended you use a /28 subnet or higher. You must not provide a subnet that is already created in the VNet.
    7. Click Map VNets.
    8. Click Save and Complete.

When you configure the two vEdge Cloud routers that form the transit VNet, ensure that the color you assign to the tunnel interface in the VPN feature configuration template for VPN 0, is a public color, not a private color. Public colors are 3g, biz-internet, blue, bronze, custom1, custom2, custom3, default, gold, green, lte, metro-ethernet, mpls, public-internet, red, and silver.

Display Host VNets

  1. In the Cloud OnRamp Dashboard, click the pane for the desired VNet. The Host VNets/Transit VNets screen opens, and Host VNets is selected by default. In the bar below this, Mapped Host VNets is selected by default, and the table on the screen lists the mapping between host and transit VNets, the state of the transit VNet, and the VPN ID.
  2. To list unmapped host VNets, click Unmapped Host VNets.
  3. To display the transit  VNets, click Transit  VNets.

Map Host VNets to an Existing Transit VNet

  1. In the Cloud OnRamp Dashboard, click the pane for the desired location of the required account. The Host VNets/Transit VNets screen opens.
  2. Click Unmapped Host VNets.
  3. Click Discover Host VNets.
  4. From the list of discovered host VNets, select the desired host VNet.
  5. Click Map VNets. The Map Host VNets popup opens.
  6. In the Transit VNet drop-down, select the desired transit VNet.
  7. In the VPN drop-down, select the VPN in the overlay network in which to place the mapping.
  8. Click Map VNets.

Unmap Host VNets

  1. In the Cloud OnRamp Dashboard, click the pane for the desired VNet. The Host VNets/Transit VNets screen opens.
  2. Click Mapped Host VNets.
  3. From the list of VNets, select the desired host VNets. It is recommended that you unmap one vNet at a time. If you want to unmap multiple vNets, do not select more than three in a single unmapping operation.
  4. Click Unmap VNets.
  5. Click OK to confirm the unmapping.

Display Transit VNets

  1. In the Cloud OnRamp Dashboard, click the pane for the desired VNets. The Host VNets/Transit VNets screen opens, and Host VNets is selected by default.
  2. Click Transit VNets.

The table at the bottom of the screen lists the transit VNets.

Add a Transit VNet

  1. In the Cloud OnRamp Dashboard, click the pane for the desired VNet. The Host VNets/Transit VNets screen opens, and Host VNets is selected by default.
  2. Click Transit VNets.
  3. Click Add Transit VNet.

Delete a Transit VNet

  1. In the Cloud OnRamp Dashboard, click the pane for the desired VNet. The Host VNets/Transit VNets screen opens, and Host VNets is selected by default.
  2. Click Mapped Host VNets.
  3. Select the desired host VNet, and click Unmap VNets.
  4. Click OK to confirm the unmapping.
  5. Click Transit VNets.
  6. Click the Trash icon to the left of the row for the transit VNet.
  7. Click OK to confirm.
  • Was this article helpful?