VMware VCENTER SERVER 4.0 - GETTING STARTED UPDATE 1 Installation Guide Page 47

  • Download
  • Add to my manuals
  • Print
  • Page
    / 72
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 46
VMware, Inc. 47
Chapter 3 Installing vCenter Server Heartbeat
To Add a new connection
1 In the navigation panel, select the vCenter Server Heartbeat Group to receive the new connection. Click
Add Connection in the tool bar, select Add Connection from the File menu, or right-click an existing
group in the navigation panel and select Add Connection to invoke the Add Connection dialog.
2 Type the Host Name or IP address for the new connection into the text box, select the Port Number (if
different from the default value of 52267), and select a group from the Add to Group drop-down list (to
add the connection to a Group other than the one currently selected).
3Click OK. The newly created connection appears in the navigation panel on the left of the VMware
vCenter Server Heartbeat Console window, and the Server: Summary page updates to represent any
existing network relationships of the added server.
4 Enter the remaining connections necessary to define the new vCenter Server Heartbeat Group.
Post Installation Configuration
Upon completion of installation, a series of tasks must be performed to ensure that VMware vCenter Server
Heartbeat is properly configured.
1 Before starting VMware vCenter Server Heartbeat, verify the time synchronization between the Primary
and Secondary servers. When a difference exists, synchronize the Secondary (passive) server to the
Primary (active) server across the VMware Channel. Type the following command at the command
prompt:
net time \\<Primary_Channel_IP_address> /set
2 When protecting SQL Server, verify that the SetSPN.exe tool present on both the Primary and the
Secondary servers at the following locations:
On Windows Server 2003 environments, in Program Files\Support Tools. If Support Tools are
not installed on your system, download them from http://support.microsoft.com/?kbid=926027 and
copy SetSPN.exe to <install_path>\R2\bin.
On Windows Server 2008 environments, in Windows\System32. This is normally present as a
component of the Windows 2008 operating system.
SetSPN.exe is a Microsoft command-line tool that reads, modifies, or deletes the Service Principal Names
(SPN) directory property for an Active Directory service account and is required to be present on both
servers prior to starting vCenter Server Heartbeat for the first time.
3 On the Primary server, navigate to Start > Administrative Tools > Services and set the VMware vCenter
Server Heartbeat service to Automatic and close the dialog.
4 Start vCenter Server Heartbeat on the Primary server. Right-click the vCenter Server Heartbeat System
Tray icon and select Start VMware vCenter Server Heartbeat. The icons change from a double dash to a
P, indicating the server is the Primary server, and an A indicating the server is acting in an active role.
N
OTE When a you attempt to connect to vCenter Server Heartbeat for the first time, you are presented
the option to accept the SSL certificate from the server. To continue connecting to vCenter Server
Heartbeat, you must accept the SSL certificate.
N
OTE You may be prompted to login. If so, login using a valid administrator-level Username and
Password for the server for which you are adding a connection, and click OK.
NOTE vCenter Server Heartbeat will not attempt to update DNS and therefore, the Administrator must
pre-populate the DNS server with entries for the new management names and IP addresses that are to be
used. Use adjacent IP addresses for the Principal (Public) IP address and the Management IP address for
the Primary and Secondary Servers when installing vCenter Server Heartbeat on servers running
Windows 2008.
Page view 46
1 2 ... 42 43 44 45 46 47 48 49 50 51 52 ... 71 72

Comments to this Manuals

No comments