2.7

n
One VLAN mapped to the DB Name Service Network enables database client applications to connect to
DBVMs. The clients request the database virtual machine IP address from the DB Name Server using
the DB Name Service network. The DB Name Server provides connection information to a database
client application, which then connects to the database using its Database Access Network. Any
database client that will issue SQL traffic to a database managed by Data Director must have access to
this network using port 389.
In addition, DB Access Networks carry SQL traffic between database client applications and databases.
These networks are not defined at installation. DB Access Networks are made available when Data Director
system administrators define resource bundles in the Data Director UI and assign the resource bundles to
organizations. A DHCP Server or IP pool is required on the DB Access Networks. Set aside at least one
network for the DB Access Network.
Two VLAN Network Configuration
A two VLAN network configuration includes one network to carry Internal Network traffic, and one
network for all other traffic. This setup requires two networks with 1-Gigabit or greater Ethernet interfaces.
The following diagram illustrates a two VLAN network configuration.
Figure 2‑2. Two VLAN Network Configuration
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 DB Access Network (DHCP or IP pool required)
Database
Client
DB Name Service Network
Internal Network
(DHCP or IP pool required)
vCenter Network
Web Console Network
DB Name Service Network
1 DB Access Network
(DHCP or IP pool required)
Network adapter
(configured during setup)
VLAN 1
VLAN 2
vCenter
Server
ESXi host
Web Console
Network
vSphere Update
Manager Server
Database
Client
Database
Client
SMTP Server
VMware vFabric Data Director Installation Guide
20 VMware, Inc.