Installation guide

vCloud Director 1.0 and 1.5 support a variety of vApp network configurations. VCM supports these
scenarios.
n
VCM is located in the vApp with the virtual machines that it is managing.
n
The vApp has a direct connection to the org network.
n
The vApp has a direct connection to the external network.
n
The vApp has a one-to-one IP address NAT connection to the organization network with direct
connection to the external network.
n
The vApp has a one-to-one IP address NAT connection to the organization network with a one one-to-
one IP address NAT connection to the external network.
n
The vApp has a direct connection to the organization network with one IP address to one IP address
NAT connection to the external network.
VCM does not support one to many IP addresses NAT mapping for vCloud Director vApp virtual
machines.
To determine the connection string to use when discovering the vCloud Director virtual machines, you
must know where VCM is located in the network and how NAT is implemented.
Location of
VCM or the
Proxy Server
on the
Network
External Network Organization Network Discovery
Rule
Connection
String
In the
managed
vApp
NA NA Internal IP
On Org
Network
NA Direct connection. None (use
DNS) or
Internal IP
On Org
Network
NA NATat vApp level. vApp
External IP
On External
Network
Direct Connection Not connected or direct connection. Internal IP
On External
Network
Direct from
Organization
NAT at vApp level. vApp
External IP
On External
Network
NAT at Org level The vApp level IPis collected from
vCloud Director, but it is not used for
the VCM connection.
Org External
IP
Table 3–1. Determining the Connection String Based on Network Configuration
After you collect the vCloud Director data, you can view the internal and external IP addresses in network
information for the virtual machines.
Best Practice
VCM cannot use DCOM to communicate with vCloud Director vApp virtual machines across NAT
mapped networks.
vCenter Configuration Manager Administration Guide
42
VMware, Inc.