A possible network configuration is to have four separate VLANs for the different types of Data Director network traffic and one or more separate DB Access Networks for database (SQL) network traffic. This configuration requires 1-Gigabit or greater Ethernet interfaces.

The following diagram illustrates a four-VLAN network configuration.

A Four-VLAN Network Diagram
The Data Director components are shown, connected by the five Data Director networks.

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.

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.

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.

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.

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.