5. vCloud Resource Design : 5.5 vCloud Networking : 5.5.8 Static Routing vApp Network Use Cases
   
5.5.8 Static Routing vApp Network Use Cases
5.5.8.1. Enabling vApp Networks Connected to an Organization Virtual Datacenter Network to Communicate Directly
This scenario provides connectivity similar to the use case shown in the following figure.
Figure 30. vApp Network Static Routing Use Case
 
If vApp level static routing is configured, enable Always use assigned IP addresses until this vApp or associated networks are deleted so that the next hop addresses for static routes does not change while vApps are powered off.

There is an overlap between organization virtual datacenter network Use Case 2 (Figure 29) and the vApp network use case, so it is important to understand the advantages and disadvantages of both configurations:
*Applying static routes at the organization virtual datacenter network consolidates management to a common view, but requires all traffic to pass through the organization’s vCloud Networking and Security Edge device.
*vApp network static routes allow traffic to flow directly between the vApps that provide the highest performance.
*Static routing at the vApp network layer supports scenarios where the organization virtual datacenter network is directly connected.
Although it is required to provide connectivity between vApps without address translation, VMware recommends that you apply static routes in the vApp network vCloud Networking and Security Edge device. Unlike NAT, static routing does not support overlapping network ranges. If there are plans to leverage static routing within the vCloud environment, allocated IP addresses for organization and vApp networks must be unique.
The static routing and NAT features are not mutually exclusive and can be used together. For example, NAT can provide external connectivity, while static routing permits direct access to other vApps within an organization.
Consider the following limitations when using static routing with vCloud Director:
*Static routing is supported only with vCloud Networking and Security Edge 5.0 (or later).
*Static routing is limited to a maximum of 64 static routes per vCloud Networking and Security Edge device.
*Dynamic routing protocols are not currently supported.
*Static routing does not apply to fenced vApps.