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
2Configuring vCenter Server Heartbeat
After installation of vCenter Server Heartbeat, initial operational conguration is performed using the vCenter
Server Heartbeat Console. The VMware vCenter Server Heartbeat – Server Conguration wizard (Congure
Server wizard) sets up and maintains communications between the vCenter Server Heartbeat servers. After
the system is set up and is functioning correctly, you do not normally need to recongure the system. The
Congure Server wizard becomes redundant during daily operations of the software.
This chapter includes the following topics:
■
“Launching the Congure Server Wizard,” on page 20
■
“Conguring the Machine,” on page 21
■
“Conguring the VMware Channel,” on page 22
■
“Conguring Public IP Addressing,” on page 24
■
“Managing vCenter Server Heartbeat License Keys,” on page 26
■
“Conguring the Logs,” on page 27
VMware, Inc. 19