You can add static routes between two vApp networks that are routed to the same organization virtual data center network. Static routes allow traffic between the networks.
You cannot add static routes to a fenced vApp or between overlapping networks. After you add a static route to a vApp network, configure the network firewall rules to allow traffic on the static route. For vApps with static routes, select to use assigned IP addresses until the vApp or associated networks are deleted.
Static routes function only when the vApps containing 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
- Two vApp networks are routed to the same organization virtual data center network.
- The vApp networks are in vApps that were started at least once.
- Static routing is enabled on both vApp networks.
Procedure
Example: Static Routing Example
vApp Network 1 and vApp Network 2 are both routed to Org Network Shared. You can create a static route on each vApp network to allow traffic between the networks. You can use information about the vApp networks to create the static routes.
Network Name | Network Specification | Router External IP Address |
---|---|---|
vApp Network 1 | 192.168.1.0/24 | 192.168.0.100 |
vApp Network 2 | 192.168.2.0/24 | 192.168.0.101 |
Org Network Shared | 192.168.0.0/24 | NA |
On vApp Network 1, create a static route to vApp Network 2. On vApp Network 2, create a static route to vApp Network 1.
vApp Network | Route Name | Network | Next Hop IP Address |
---|---|---|---|
vApp Network 1 | tovapp2 | 192.168.2.0/24 | 192.168.0.101 |
vApp Network 2 | tovapp1 | 192.168.1.0/24 | 192.168.0.100 |