6.5
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Introduction
- Configuring vCenter Server Heartbeat
- Server Protection
- Checking the Server Pair Status
- Monitoring the Status of Servers
- Configuring Heartbeat Settings
- Network Protection
- Application Protection
- Applications: Summary Tab
- Resetting the Application Health Status
- Viewing Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Stop and Start 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
- Applications: Summary Tab
- Status and Control
- About vCenter Server Heartbeat Console
- Working with Groups
- Working with Pairs in vCenter Server Heartbeat Groups
- Reviewing the Status of vCenter Server Heartbeat Groups and Pairs
- Exiting vCenter Server Heartbeat Console
- Shutting Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Web Client Plug-in
- Uninstalling vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Two Active or Two Passive Servers
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Server Does Not Meet Minimum Hardware Requirements
- Hardware or Driver Issues on VMware Channel NICs
- Firewall Connection
- Channel Fails to Connect After Configuring Firewall Ports
- Incorrect VMware Channel Configuration
- VMware vCenter Server Heartbeat Packet Filter Is Enabled on the Channel NIC(s)
- Subnet or Routing Issues
- MaxDiskUsage Errors
- Application Slowdown
- Glossary
Procedure
◆
To change Low Bandwidth Optimization after installation, select the Channel tab of the Congure Server
wizard and use the HA/DR Topology drop-down to select the appropriate topology. Click Next or Finish
to accept changes.
Figure 2- 4. Configure Server wizard - Channel tab
Configuring Public IP Addressing
vCenter Server Heartbeat servers are typically congured with one shared Principal (Public) IP address in a
LAN or two Principal (Public) IP address in a WAN. These are the addresses used by clients to connect to the
protected application.
During installation, vCenter Server Heartbeat congures the Principal (Public) IP address(s) and further
conguration is not normally necessary.
In the event that you must add a Management IP address or Principal (Public) IP address for your environment,
vCenter Server Heartbeat allows you to add these addresses using the Congure Server wizard.
Configuring Principal (Public) IP Addressing
vCenter Server Heartbeat's Congure Server wizard is used to add or modify Management IP and Principal
(Public) IP addresses when required by your environment such as during a migration from a LAN deployment
to WAN deployment.
Procedure
1 Select the Public tab of the Congure Server wizard and verify that Non-Identical is selected in the Public
Identity Mode pane.
2 Verify the vCenter Server or SQL Server Public name in the Name used to connect to vCenter or SQL Server
eld.
24 VMware, Inc.
Administrator Guide