Skip to content

Virtual Routers

Virtual Routers allow for routing across Virtual Networks. Admins are able to connect virtual networks both via the GUI or CLI. The routing is implemented by means of a Virtual Machine appliance which is available to be downloaded from the Storage → Apps Menu.

Storage Menu

Search for the Service Virtual Router Appliance from the list of Apps available in the linked marketplaces, it should be available from the Public marketplace.

Apps List Virtual Router

Select the App and Import to the default Datastore by clicking the Import to Datastore button. This will allow the Template to be instantiated and used for bridging Virtual Networks. This special Virtual Machine Template contains and implements various Virtual Network Functions (VNFs) that process the context information from the HyperCloud infrastructure.

Service Virtual Router Template Context

Navigate to Templates → Virtual Routers and select the downloaded Service Virtual Router App for instantiation.

VR VM Template

Click the green dropdown button to enter the Wizard that will help Instantiate the VR. From here there are several Custom Attributes that can be enabled or disabled; as well as, options once Virtual Network(s) is(are) selected.

  1. Give the Virtual Router a unique, logical Name

    Instantiate VR Template

  2. Select Virtual Network(s)

    • Floating IP
      • More than one Virtual Machine can be associated with a Virtual Router to implement High Availability (HA) where a floating IP will be assigned to the group of VMs, that will coordinate to manage the traffic
    • Force IPv4 or IPv6
      • The IP assigned to the NIC can be forced; if the VR is not configured for HA, this will be the IP requested for the VM appliance
    • Management Interface

      • With this option selected, the NIC will be a Virtual Router management interface; traffic will not be forwarded to it.

        VR NIC Options

  3. Enable/Disable Custom Attributes

  4. Click green Instantiate button to finish the setup and HyperCloud will create the Virtual Router and the Virtual Machines automatically.

Danger

When the VR is terminated, the associated VM will remain active. When an attempt is made to remove the VM, the error message:
[one.vm.action] Error performing action "terminate-hard": Could not terminate VM, wrong state SHUTDOWN.
This is a side-effect of how the front end communicates with libvert.

Warning

If the Virtual Router is locked, a small, dark line will appear next to the Instance listing, indicating this new state; however, the corresponding VM created in conjunction with this VR will not be locked and can be modified.

VR Lock State