5.5

QuickStart Guide
16 VMware, Inc.
Secondary Server
Networking components on the Secondary server must be configured as follows:
 Same number of NICs as the Primary server
 Principal (Public) network connection configured with temporary network settings
 Channel network connection(s) configured with the following:
 Static IP address in a different subnet than the Principal (Public) network with a different IP address
than the Primary server channel NIC
 Correct network mask
 No Gateway IP address
 No DNS IP address
 NetBIOS enabled (disabled during the installation process)
 File and print sharing enabled
WAN
Deploying vCenter Server Heartbeat in a WAN environment requires additional considerations. Each server
within the vCenter Server Heartbeat pair requires its own separate Principal (Public) IP address and a VMware
Channel IP address in a separate dedicated subnet.
WAN Requirements
When deploying vCenterServer Heartbeat in a WAN environment, the following components must be
configured:
 Persistent static routing configured for the channel connection(s) where routing is required
 Two NICs (1 x Public; 1 x Channel) recommended
 At least one Domain Controller at the Disaster Recovery (DR) site
 If the Primary and DR site use the same subnet:
 During install, follow the steps for a LAN or VLAN on the same subnet
 Both servers in the vCenter Server Heartbeat pair use the same Public IP address
 If the Primary and DR site use different subnets:
 During install, follow the steps for a WAN
 Both servers in the vCenter Server Heartbeat pair require a separate Principal (Public) IP address and
a VMware Channel IP address in a separate dedicated subnet
 Provide a user account with rights to update DNS using the DNSUpdate utility provided as a
component of vCenter Server Heartbeat when prompted during the setup process
 Recommend integrating Microsoft DNS into AD so that DNSUpdate can identify all DNS Servers
that require updating
 At least one Domain Controller at the DR site
 Refer to the following articles in the knowledge base:
 KB 1008571 – Configuring DNS in a WAN Environment
 KB 1008605 – Configuring vCenter Server Heartbeat to Update BIND9 DNS Servers Deployed in a
WAN
N
OTE Prior to installing vCenter Server Heartbeat, verify that vCenter Update Manager and vCenter
Converter are configured using Fully Qualified Domain Names (FQDN) rather than IP addresses.