6.3

VMware, Inc. 21
Chapter 2 vCenter Server Heartbeat Installation
18 Enter the Service Name for the vCenter Server or SQL Server.
19 In the NIC drop-down, select the Principal (Public) NIC.
20 In the Public IP drop-down, select the Principal (Public) IP address assigned to the Principal (Public) NIC.
21 In the first Mask field, enter the Subnet Mask of the Principal (Public) IP address.
22 In the Passive IP field, enter a reserved Management IP address for the Secondary server.
23 In the second Mask field, enter the Subnet Mask of the Management IP address.
24 Click Finish. Do not start vCenter Server Heartbeat.
25 Verify that the pre-populated management names and IP addresses to be used are configured and
available in the non-updatable DNS servers before starting vCenter Server Heartbeat for the first time.
Renaming the Servers
Configuration for non-identical nodes in the Pair requires unique server names for each server and the vCenter
Server application to operate properly. To create the unique names you must rename both the Primary and
Secondary servers to ensure proper configuration and prevent name resolution problems when clients attempt
to access the vCenter Server application
For example, before installing vCenter Server Heartbeat your vCenter Server is named “vCenterServer”.
During the vCenter Server Heartbeat installation process on “vCenter Server” you clone “vCenterServer” (the
Primary server) to create a Secondary server.
N
OTE The Service Name is the DNS name by which application clients connect to the application.
Normally this is the original name of the vCenter Server or SQL Server. There is only one Service Name
and it is the same on all servers in the cluster.
N
OTE The Management IP address is unique for each server in the cluster.