Configure VNET for external routing service

When creating a virtual network (VNET) in ThinkAgile CP version 3.3 and later, additional configuration is required if you select Virtual Networking for the external Routing Service. A static route must be added to the Interconnect and the Network Function Virtualization (NFV) instance of the VNET acting as the routing service.


If you choose a VLAN network for the external network, a static route needs to be created on your core router.

To illustrate creating a VNET for the external routing service, refer to the following example. In this example, a user is creating VNET2, which will use VNET1 as the Routing Service (external) interface.



Configuring the Interconnect

Follow these steps to add a static route to the Interconnect.

  1. SSH into the Interconnect with the username admin and the password that was set when the hardware was registered.
  2. Run the following command and retype your administrator password to become root:

    sudo su

  3. Run the following command:

    > /usr/share/tacp/ "add <network address of VNET2> <subnet mask of VNET2> <external IP of VNET1>"

    In this example, the command would be:

    /usr/share/tacp/ "add 24"

Configuring the VNET1 NFV instance

Follow these steps to add a static route to the NFV instance of the VNET acting as a routing service.

  1. Open the console to the NFV instance for VNET1.
  2. Log in with the following credentials:
    • Username: root

    • Password: ThinkAgileCP

  3. Enter the command:

    vi /etc/sysconfig/network-scripts/route-internal

    and type i to edit the file.

  4. Enter the command:

    <vnet IP range of VNET2> via <external IP of VNET2> dev internal

    In this example, the entry would be: via dev internal

  5. Press ESC and enter :wq to write changes and close the file.
  6. Run: ifup internal.

Alternatively, you can use an application instance as a NFV. For more information, see Use NetScaler as an NFV.