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
Monitoring the Status of Servers
The Server: Monitoring page provides additional information about the status of communications between the
servers within the pair. The graphical representation provides an overview of the status of communications
between the servers. A green channel icon indicates that the channel is connected and healthy while a yellow
dashed channel icon indicates that communications are not operational between the indicated servers. In
addition to the heartbeat sent between the servers, vCenter Server Heartbeat also sends a ping to ensure that
the servers remain visible to one another.
Configuring Heartbeat Settings
The Server: Monitoring page provides three conguration features: Congure Pings, Congure Failover, and
Congure Response Times.
Configuring Pings
IP addresses of all NICs used for the VMware Channel and congured Management IP addresses are, by
default, automatically added during startup of vCenter Server Heartbeat. The Server: Monitoring Ping
Conguration dialog allows you to add additional ping targets. This conguration allows vCenter Server
Heartbeat to send pings across the VMware Channel in addition to the heartbeat (“I’m alive” messages) and
to the other server in the pair over the Public network via the Management IP address to conrm that the
server is still operational and providing service.
To add additional ping targets:
Procedure
1 Click Congure Pings to open the Server Monitoring: Ping Conguration dialog.
2 Select the Ping Settings tab to congure the Ping Interval.
3 Select the Ping Routing tab to add additional ping targets.
Configuring Failover and Active Server Isolation
vCenter Server Heartbeat continuously monitors the servers in the pair and the network to ensure availability
and uses native logic and a combination of elapsed time, administrator congured rules, current server network
status, and congured ping routing to determine if failover or isolation of the active server is warranted should
the servers experience missed heartbeats.
To congure failover:
Note For information on conguring ping routing, see “Conguring Pings,” on page 31 and Conguring
Public Network Connection Checks.
VMware, Inc. 31
Chapter 3 Server Protection