Follow

Virtual Networking as a Routing Service

When creating a virtual network (vnet) in 3.3 and later, additional configuration is required if "Virtual Networking" is chosen for the external Routing Service: a static route must be added to the SDN Router and the Network Function Virtualization (NFV) instance of the vnet acting as a routing service.

In this example, the user is creating Vnet2 that will use Vnet1 as the Routing Service (external) interface.

Vnet1:

  • Vnet IP Range: 10.104.14.0/24
  • External Routing Service IP (bridged): 10.102.14.200
  • Internal IP: 10.104.14.1

Vnet2:

  • Vnet IP Range: 10.6.200.0/24
  • External Routing Service IP (Vnet1): 10.104.14.100
  • Internal IP: 10.6.200.1

Ignite SDN Router:

  • SSH into the Ignite SDN Router with username manager and the password is what was configured when the hardware was registered
  • Run sudo su and retype your manager password to become root
  • Run /usr/share/cloudistics/export_bgp_route.sh "add <network address of Vnet2> <subnet mask of Vnet2> <external IP of Vnet1>"
    • In this example, the command would be /usr/share/cloudistics/export_bgp_route.sh "add 10.6.200.0 24 10.102.14.200"

Vnet1's NFV instance:

  • Open the console to the NFV instance for Vnet1
  • Log in as root with password cloudistics
  • Enter vi /etc/sysconfig/network-scripts/route-internal and type i to edit the file
  • Enter <vnet IP range of Vnet2> via <external IP of Vnet2> dev internal and enter ESC and :wq to write changes and close the file
    • In this example, the entry would be 10.6.200.0/24 via 10.104.14.100 dev internal
  • Run ifup internal

 

Alternatively, you can use an Instance as a NFV - Learn how here

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments