5. vCloud Resource Design : 5.5 vCloud Networking : 5.5.6 Static Routing
   
5.5.6 Static Routing
Another feature in vCloud Director 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 route (such as when using multiple interfaces on vCloud Networking and Security 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 virtual datacenter network level and vApp network level.
*For Edge Gateway instances that are connected to multiple external networks and organization virtual datacenter networks, routes can be applied on the entire Edge Gateway or on any one of the external networks connected to the Edge Gateway.
*For vApp networks, that are route connected to an external network, 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, the following are common use cases.