6.3
Table Of Contents
- Installation Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- Installing vCenter Server Heartbeat on Identical Nodes
- Installing vCenter Server Heartbeat on Non-Identical Nodes
- Appendix - Setup Error Messages
- Glossary
Installation Guide
46 VMware, Inc.
When Deployed in a WAN Environment
When deployed in a WAN environment with VMware Orchestrator and the Primary and Secondary servers
in different subnets, you must configure an Exclusion File Filter following the steps below:
1 Launch vCenter Server Heartbeat Console.
2Click Data and click the File Filters tab.
3Click Add Exclusion Filter and type the following path:
$INSTALL_PATH_TO_ORCHESTRATOR/app-server/bin/boot.properties
4Click OK.
5 Perform a switchover so that the Secondary server becomes active.
6 Launch the vCenter Orchestrator Web Configuration wizard and select Network. In the IP address field
select the Principal (Public) IP address of the Secondary server. Click Apply changes.
7In the vCenter Orchestrator Web Configuration wizard, select Startup Options, and click Restart
service.
8From vCenter Server Heartbeat Console, select Applications and then Services. Verify that VMware
vCenter Orchestrator Server service is included in the protected services. If not, manually run the
Protected Service Discovery task from VMware vCenter Heartbeat Console > Applications > Tasks >
VMware VirtualCenter - Protected Service Discovery)
vCenter Server 2.5
The post installation configuration tasks are determined by the type of network environment.
LAN
For LAN deployments, perform the following:
1 If a Management IP address is configured, no additional tasks are required.
2 If a Management IP address is not configured, configure a VMware Managed IP address using the Virtual
Infrastructure Client.
a Launch the Virtual Infrastructure Client.
b In the Virtual Infrastructure Client, navigate to Administration > VirtualCenter Management
Server Configuration > Runtime Settings.
cIn the Managed IP field, type the Principal (Public) IP address.
dClick OK.
WAN
For WAN deployments, regardless of whether a Management IP address exists, vCenter Server Heartbeat
provides a task that can be configured to update the ESX hosts with the new Managed IP address during a
switchover or failover. The task requires setting the Managed IP in either the vpxd.cfg file or in the registry.
To configure the Managed IP in the Vpxd file
1The vpxd.cfg file is located at C:\Documents and Settings\All Users\Application
Data\VMware\VMware VirtualCenter.
2 On the active server, locate the <vpxd> element in the vpxd.cfg file and add a new element <managedIP>
that contains the Principal (Public) IP address of the vCenter server.
To configure the Managed IP in the registry
At HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter, create a new string value
called <managedIP> and set it with the Public (Principal) IP address of the currently active server.