2.5

Figure 2-1. A Four-VLAN Network Diagram
Data Director
Web Console
vFabric Data Director vApp
vCenter Network
Management
Server
DB Name
Server
Internal Network (DHCP or IP pool required)
Database VMs
1 to N DB Access Networks
(DHCP or IP pool required)
Database
Client
DB Name Service Network
Database
Client
Database
Client
Web Console Network
vCenter Network
Internal Network
(DHCP or IP pool required)
DB Name Service Network
DB Access Networks
(DHCP or IP pool required)
network adapter
(configured during setup)
vCenter
Server
ESXi host
Web Console
Network
vSphere Update
Manager Server
SMTP Server
This example configuration uses four VLANs with DHCP servers or IP pool mapped in the Data Director
setup wizard after the Deploy OVF Template wizard completes.
n
One VLAN mapped to the vCenter Network, which carries Management Server traffic between vCenter
Server, the Data Director Management Server, and the DB Name Server. The Data Director Management
Server acquires virtual resource information over this network. vSphere Update Manager communicates
with the DB Name Server to get the database server IP address through the vCenter Network.
n
One VLAN mapped to the Internal Network, which carries management traffic between the Data Director
Management Server and the agents running in the database virtual machines (DBVMs), and DB Name
Server traffic between the database virtual machines and the LDAP Server when an IP address changes.
A DHCP Server or IP pool is required on the Internal Network.
n
One VLAN mapped to the Web Console Network, which carries Data Director UI traffic to a web browser.
The Web Console network adapter is defined in the Data Director vApp. Any Web client that will use the
Data Director Management Server must have access to this network using HTTPS.
Chapter 2 Planning the Network Configuration
VMware, Inc. 19