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
1 Navigate to Server: Monitoring > Congure Failover to open the Server Monitoring: Failover
Conguration dialog.
2 The Failover timeout can be customized by changing the default value (60 seconds) to a custom value. Type
a new numeric value (seconds) in the Failover timeout text box or use the arrow buttons to congure how
long vCenter Server Heartbeat waits for a missed heartbeat before it takes a pre-congured action to
failover or isolate the active server from the network.
3 Select or clear check boxes for the items listed below to select the actions to take if the specied Failover
timeout is exceeded.
When the congured Failover timeout value has elapsed, vCenter Server Heartbeat will evaluate, in order,
the following pre-congured rules before taking action:
■
Failover from Primary server to Secondary server if channel heartbeat is lost for failover timeout
■
Failover from Secondary server to Primary server if channel heartbeat is lost for failover timeout
■
Prevent failover or auto switchover while not synchronized
■
Prevent Failover if channel heartbeat is lost but Active server is still visible to other servers
■
Make the server passive if the Channel and Public networks are lost for the congured failover timeout
Note If a rule is not selected, vCenter Server Heartbeat will skip the rule and move to the next rule in
the list. After all selected rules have been evaluated vCenter Server Heartbeat will take action.
4 Click OK.
Important If either Server: Monitoring Ping Routing or Network Monitoring Ping Routing is miscongured,
unpredictable behavior can occur.
Typical Failover and Active Server Isolation Scenarios
The following scenarios assume that vCenter Server Heartbeat is deployed in a LAN with all rules selected in
the Server: Monitoring > Congure Failover > Failover Conguration dialog.
Failover
The following scenario assumes the active server has failed and is no longer available.
Upon detection of missed heartbeats, vCenter Server Heartbeat on the passive server performs the following
steps:
1 As soon as the passive server detects that the VMware Channel is experiencing missed heartbeats. It will
attempt to ping the active server's Management IP address via the Public network using the passive server's
NIC congured with the Management IP address. If the ping is successful, the passive server will veto
the failover. If the ping is unsuccessful, it will continue to the next step.
Note Since the passive server assumes that active server has failed, the passive server will not attempt
to verify synchronization with the active server.
2 At this point, the passive server checks the congured value of the Failover timeout and starts a "Heartbeat
lost" countdown The passive server continues with the next step.
32 VMware, Inc.
Administrator Guide