An organization administrator can add static routes between two vApp networks that are routed to different organization virtual datacenter networks. Static routes allow traffic between the networks.

About this task

You cannot add static routes between overlapping networks or fenced vApps. After you add a static route to an organization virtual datacenter 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 function only when the vApps included in the routes are running. If a vApp includes static routes and you perform the following operations, the static routes cannot function and you must remove them manually.

  • Change the parent network of the vApp

  • Delete a vApp

  • Delete a vApp network

Prerequisites

Verify that vCloud Director has the following configurations:

  • Two organization virtual datacenter networks routed to the same external network.

  • Static routing is enabled on both organization virtual datacenter networks.

  • A vApp network is routed to each organization virtual datacenter network.

  • The vApp networks are in vApps that were started at least once.

Procedure

  1. Click the Manage & Monitor tab and click Organization VDCs in the left pane.
  2. Double-click the organization virtual datacenter name to open the organization virtual datacenter.
  3. Click the Org VDC Networks tab, right-click the organization virtual datacenter network name, and select Configure Services.
  4. On the Static Routing tab, click Add.
  5. Type a name, network address, and next hop IP address.

    The network address is for the vApp network to which to add a static route. The next hop IP address is the external IP address of the router for the organization virtual datacenter network to which that vApp network is routed.

  6. Select To external network and click OK.
  7. Click Add.
  8. Type a name, network address, and next hop IP address.

    The network address is for the vApp network that is routed to this organization virtual datacenter network. The next hop IP address is the external IP address of the router for that vApp network.

  9. Select Within this network and click OK.
  10. Repeat steps 4 through 9 to add static routes to the second organization virtual datacenter network.

Static Routing Example

vApp Network 1 is routed to Org VDC Network 1. vApp Network 2 is routed to Org VDC Network 2. You can create static routes on the organization virtual datacenter networks to allow traffic between the vApp networks. You can use information about the vApp networks and organization virtual datacenter networks to create the static routes.

Table 1. Network Information

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.11.0/24

192.168.10.100

Org VDC Network 1

192.168.0.0/24

10.112.205.101

Org VDC Network 2

192.168.10.0/24

10.112.205.100

On Org VDC Network 1, create a static route to vApp Network 2 and another static route to vApp Network 1. On Org VDC Network 2, create a static route to vApp Network 1 and another static route to vApp Network 2.

Table 2. Static Routing Settings for Org VDC Network 1

Static Route to Network

Route Name

Network

Next Hop IP Address

Route

vApp Network 2

tovapp2

192.168.11.0/24

10.112.205.100

To external network

vApp Network 1

tovapp1

192.168.1.0/24

192.168.0.100

Within this network

Table 3. Static Routing Settings for Org VDC Network 2

Static Route to Network

Route Name

Network

Next Hop IP Address

Route

vApp Network 1

tovapp1

192.168.1.0/24

10.112.205.101

To external network

vApp Network 2

tovapp2

192.168.11.0/24

192.168.10.100

Within this network

What to do next

Create firewall rules to allow traffic on the static routes. See Add a Firewall Rule for an Organization Virtual Datacenter Network.