Question

How to enable IP forwarding on a controller that is connected to Versa Director?

Solution

Enabling IP forwarding for the Virtual Machine (VM) is necessary to allow a VM to receive traffic addressed to other destinations.

NOTE: This is an Azure setting, and not a setting in the guest operating system. This configuration is in addition to the the security group configuration that is available on NIC level (on Microsoft Azure). This configuration is not a replacement for placing approriate security group for the SD-WAN deployment solution.


Enabling IP Forwarding on Controller Interface Connected to Versa Director


Follow these steps to enable IP forwarding:

  1. Login to Azure portal.
  2. Select Network Interfaces.
  3. Select a Name and click IP configurations.
  4. Select Enabled option for IP forwarding.


This enables the IP forwarding on the Controller interface connected to Versa Director.


Adding User Defined Routes

Enable User Defined Routes (UDR) in Azure along with IP forwarding. With UDRs, the controller address is used as a gateway for IPSec overlay network address for the netconf traffic originating from the Versa Director.


Follow these steps to add UDR:

  1. Login to Azure portal.
  2. Select Route tables > Create route tables.
  3. In the Create route table section, enter appropriate values for Name, Subscription, Resource group, and Location. A Route table, Test, is created.

  4. Select Route tables > Test > Routes > Add.
  5. In the Add route pane, enter values for Route name, Address prefix, Next hop type, and Next hop address.
  6. Click OK. 

Associating the Route Table with Subnets

 NOTE: You cannot motre than one routing table with a subnet.


Follow these steps to associate the route table with the subnets:

  1. Open the newly created route table, and click Subnets.
  2. In the Subnets column, click Associate to add a subnet.
  3. In the Associate subnet column, click Virtual network.
  4. Select the virtual network in the Resource column.
  5. In the Associate subnet column, click Subnet.
  6. In the Choose subnet column, select the subnet.
  7. Click OK.
  8. Optionally, associate additional subnets with the route table.

    NOTE: You cannot associate more than one routing table with a subnet.


  9. The subnets associated with this route table are now visible in the subnets section of your route table’s column.