6.4
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Application Protection Overview
- Applications: Applications Tab
- Reset the Application Health Status
- View Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Start and Stop Applications
- Configuring Applications
- Application Maintenance Mode
- Reviewing the State of an Application
- Reviewing the Applications Log
- Filtering Application Log Entries
- Applications: Services Tab
- Applications: Tasks Tab
- Applications: Plug-ins Tab
- Status and Control
- vCenter Server Heartbeat Console
- About vCenter Server Heartbeat Console
- Work with Groups and Pairs
- Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
- Review the Status of vCenter Server Heartbeat Groups and Pairs
- Exit vCenter Server Heartbeat Console
- Shut Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Client Plug-in
- Uninstall vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Glossary
Reference Guide
22 VMware, Inc.
Configuring Public IP Addressing
vCenter Server Heartbeat servers are configured with one or more Principal (Public) IP addresses. These are
the addresses used by clients to connect to the protected application. Typically, there is one shared Principal
(Public) IP address.
You must configure all of the Principal (Public) IP addresses on the server to be active initially. On the passive
server, you must configure a unique management IP address by which you can access the passive server while
the active server continues to service clients. When the server roles switch, the passive server’s management
IP address is removed and replaced with the Principal (Public) IP address which was removed from the
previously active server. The previously active server is then provided its unique management IP address by
which the server can be accessed while passive.
Configuring Principal (Public) IP Addressing
While this is normally performed as a post-installation task when installing vCenter Server Heartbeat, in the
event of an upgrade you may be required to reconfigure your servers for non-identical nodes.
To configure for Non-Identical Nodes
1 Select the Public tab of the Configure Server wizard and verify that Non-Identical is selected in the Public
Identity Mode pane.
2 Enter the vCenter Server or SQL Server name in the Name used to connect to vCenter or SQL Server field.
3In the NIC field, select the Principal (Public) network connection in the drop-down.
4 Enter the Principal (Public) IP address in the Public IP field.
5 Enter the Principal (Public) IP address Subnet Mask in the first Mask field.
6 Enter the reserved Management IP address in the Mgmt IP field.
7 Enter the reserved Management IP address Subnet Mask in the second Mask field.
8Click Next or Finish.
N
OTE Adjacent IP addresses should be reserved and used for the Principal (Public) IP address and the
management IP addresses for the Primary and Secondary Servers when installing vCenter Server
Heartbeat on servers running Windows 2008.