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
3Server Protection
Protection against operating system or hardware failure aecting the active server is facilitated by two instances
of the vCenter Server Heartbeat that monitor one another by sending “I’m alive” messages and reciprocating
with acknowledgments over the VMware Channel. If the passive server detects that this process (the heartbeat)
has failed, an automatic switchover is initiated.
Additionally, vCenter Server Heartbeat proactively monitors the capability of the active and passive servers
to communicate with the rest of the network by polling dened nodes around the network, including by
default, the primary DNS server, default gateway, and the Global Catalog server at regular intervals. If all
three nodes fail to respond, for example, due to a network card or local switch failure, vCenter Server Heartbeat
can initiate an automatic switchover, allowing the passive server to assume the role of the active server.
This chapter includes the following topics:
■
“Checking the Server Pair Status,” on page 29
■
“Monitoring the Status of Servers,” on page 31
■
“Conguring Heartbeat Settings,” on page 31
Checking the Server Pair Status
The Server: Summary page is the default page that opens when administering a pair of servers. The Server:
Summary page allows you to view the roles that the servers are performing (active or passive), the actions that
the servers are currently performing, and summary information on the status of communications and data
replication between servers. The lower pane displays status information for each server in the pair.
Note To change the currently displayed server, click the server graphical representation in the upper pane,
or select the server Identity tab (Primary or Secondary Server) in the bottom pane.
The following table lists the possible system statuses and their meanings.
Table 3- 1. System Status
DescriptionIconStatus
The Heartbeat service is shut down.Heartbeat service
shutdown
The Heartbeat service is starting up.Initializing
(Normal status) File and registry changes on the active server are intercepted and
replicated to the passive server. The protected applications are monitored.
Replicating
VMware, Inc. 29