6.3

VMware, Inc. 57
Chapter 4 Installing vCenter Server Heartbeat on Non-Identical Nodes
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 If you have configured vCenter Server Heartbeat to use non-updating Microsoft DNS servers (Locked
Down mode) or non-Microsoft DNS servers, verify that the prepopulated management names and IP
addresses to be used are configured and available in the DNS servers before starting vCenter Server
Heartbeat for the first time.
Renaming the Servers
Configuration for non-identical nodes in the cluster require unique server names.
To rename the Secondary server
1 Navigate to Start > Administrative Tools > Services and set the Neverfail Server R2 service to Manual,
Stopped, and close the dialog.
2 Right-click the Secondary server image and select Edit Settings.
3 Disable the virtual network adapters for both the VMware Channel and Principal (Public) NICs.
4 Open Network Connections, right-click the Principal (Public) network connection and select Properties.
Select Internet Protocol (TCP/IP) and click Properties.
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.