In Virtual Private Cloud OnDemand, the gateway supports configuring static routing between the interfaces in the gateway. By default, static routing is disabled for a gateway. (On an isolated network, which does not connect to a gateway, static routing is not applicable).

On a routed network, network traffic goes to the gateway’s default interface, which connects to the Internet. When you configure a static route between interfaces, traffic bypasses the default interface to the Internet.

Example of Static Routing in Virtual Private Cloud OnDemand
Example of Static Routing in Virtual Private Cloud OnDemand

You might want to enable static routing on a gateway for the following use cases:

So that all the traffic from the external network traverses the antivirus appliance first before accessing your virtual machines

When you want a Web server on one routed network to connect to an application server on another routed network without having the traffic traverse the Internet

Configure static routing for a routed network by navigating from Virtual Private Cloud OnDemand to the networking services for the gateway in vCloud Director:

Virtual Private Cloud OnDemand Web UI > Gateway tab > Manage in vCloud Director > vCloud Director Administration page > Edge Gateways tab > select the gateway, right-click and choose Edge Gateway Services > Static Routing tab


You cannot register static routes with duplicate networks; for example, you cannot add static routes using the longest prefix matching protocol.

For the steps to configure static routing by using vCloud Director, see the following topics in vCloud Director Administrator’s Guide:

Enable Static Routing on an Edge Gateway

Add Static Routes Between vApp Networks Routed to the Same Organization Virtual Datacenter Network