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.

Two VLAN Network Configuration
The Data Director components are shown, connected by the five Data Director networks, with the Internal Network on VLAN 1 and the other networks on VLAN 2.

The two VLANs carry the following traffic.

One VLAN is for the shared network for vCenter, Web Console, DB Name Service, and DB Access Networks.

One VLAN is for the Internal Network. This VLAN carries internal management traffic between databases, the Data Director Management Server, and the DB Name Server. The Internal Network must be a VLAN.

This configuration requires DHCP or IP pool on the shared (vCenter Server, Web Console, and Internal) network, and for the DB Access network. To handle internal management traffic, the DHCP range or the IP pool should have at least as many IP addresses as the number of databases. See Data Director Networks, IP Allocation, and Firewalls.

Because all vCenter Network traffic, Web Console Network traffic, and SQL traffic is carried by one network, you cannot isolate databases into different networks.