A new feature in vCloud Director 1.5 is support for static routing. This provides the ability to route between network segments without the use of NAT and enables increased flexibility in implementing network connectivity within a vCloud environment. Though most networks will have a directly connected default gateway, it is possible for networks to have more than one router (such as multiple vShield Edge devices). Static routing provides a way to manually configure routing tables so that traffic can be forwarded to these remote networks while still using the default gateway for all remaining traffic. In vCloud Director, static routing can be configured at both the routed organization network level and vApp network level.
- For organization networks, routes can be defined within the organization network or to an external network.
- For vApp networks, the static routing configuration is simplified as routes are only applied on the external interface.
To demonstrate the different options for static routing with vCloud Director, I've recorded a video which will show you how to add Static Routes Between vApp Networks Routed to Different Organization Networks. An organization administrator can add static routes between two vApp networks that are routed to different organization networks. Static routes allow traffic between the networks. You cannot add static routes between overlapping networks or fenced vApps. After you add a static route to an organization network, configure the network firewall rules to allow traffic on the static route. For vApps with static routes, select the Always use assigned IP addresses until this vApp or associated networks are deleted check box.
Static routes only function when the vApps included in the routes are running. If you change the parent network of a vApp, delete a vApp, or delete a vApp network, and the vApp includes static routes, those routes cannot function and you must remove them manually.
Prerequisites:
- vShield 5.0
- Two organization networks routed to the same external network
- Static routing is enabled on both organization networks
- A vApp network routed to each organization network
- The vApp networks are in vApps that were started at least once
