2.7
Table Of Contents
- VMware vFabric Data Director Installation Guide
- Contents
- About VMware vFabric Data Director
- Installation Prerequisites and vSphere Setup
- Planning the Network Configuration
- Deploy the vFabric Data Director vApp
- Perform vFabric Data Director Express Setup
- Perform vFabric Data Director Advanced Setup
- Start the Data Director Setup Wizard
- Accept the License Agreement
- Choose Advanced Setup
- Create the Initial Data Director System Administrator Account
- Set User Management Mode
- Configure the Branding Settings
- Configure SMTP Settings
- Configure the vCenter Network and Its Network Adapters
- Configure Network Mapping
- Configure Networks and Network Adapters
- Enter License Information
- Review Data Director Setup
- vFabric Data Director Upgrade
- Index
Relating Networks in vSphere and Data Director
Data Director components communicate by using vSphere networking resources. Before you start planning
your network, you must understand vSphere and Data Director networking.
Data Director requires networks to carry communications among its components, including the following.
n
Communication between the Data Director Management Server and database servers.
n
Communication between database servers and applications.
n
Communication between the Data Director DB Name Server and applications.
vSphere administrators create switches and networks for each ESXi host. As a vSphere administrator, you
can either designate existing networks for Data Director use, or create and configure networks for Data
Director use. These networks will be used for the Management Server and for one or more DB Access
Networks.
You specify the different networks at different times in the installation and setup process.
vCenter Network and
Web Console Network
You specify the vSphere port groups (networks) to use for vCenter Network
and Web Console Network during Data Director vApp deployment.
NOTE Set up vSphere Update Manager to use the vCenter Network to
communicate with Data Director. If vSphere Update Manager uses a
different network, it cannot function properly.
Internal Network and DB
Name Service Network
You set up the Internal Network and DB Name Service Network after the
Data Director vApp deploys, during the Data Director setup process. See
“Configure Network Mapping,” on page 37. DHCP or IP pool must be
enabled on these networks.
DB Access Network
A DB Access Network is the interface to the database virtual machines
(DBVMs) and carries SQL traffic. DBVMs run the actual databases and are
created when users create databases. DHCP or IP pool must be enabled on
DB Access networks. You can configure as many DB Access networks as
there are databases. You select the vSphere networks to use for the DB
Access Network when you create resource bundles. See the vFabric Data
Director Administrator and User Guide.
Best practice is to set up your Data Director networks as separate subnets, such as using different VLANs, to
provide the best security. Use VLANs with 1-Gigabit or higher speed Ethernet interfaces.
In addition to network setup, you must also open certain ports in your firewall. See “Data Director
Networks, IP Allocation, and Firewalls,” on page 15.
Data Director Networks, IP Allocation, and Firewalls
Data Director supports DHCP and IP pool for network configuration. To plan your network, you must
understand DNS Server requirements and know which firewall ports must be open for Data Director traffic.
The Data Director vApp requires the use of a DHCP or IP pool address allocation policy. Set up a DHCP
server or IP pool for the Internal Network and the DB Access Network. See the vFabric Data Director
Administrator and User Guide for information about IP pool setup. If you select a static IP address for the Web
Console Network adapter on the Management Server, a DHCP server or IP pool on the Web Console
Network is not required.
Chapter 2 Planning the Network Configuration
VMware, Inc. 15