6.6
Table Of Contents
- vCenter Server Heartbeat Administrator's Guide
- Contents
- About This Book
- Introduction
- vCenter Server Heartbeat Monitoring
- Supported vCenter Server Heartbeat Clients
- vCenter Server Heartbeat Console
- vSphere Web Client Plug-in
- vSphere Client Plug-in
- Server Monitoring
- Network Monitoring
- Application Monitoring
- Performance Monitoring
- Monitoring Data Replication
- Managing vCenter Server Heartbeat
- Server Configuration Wizard
- Managing Heartbeat Settings
- Managing Application Protection
- Managing Services
- Managing Tasks
- Managing Rules
- Managing Plug-ins
- Managing Data Protection
- Maintaining vCenter Server Heartbeat
- vCenter Server Heartbeat Diagnostics
- Collecting Diagnostic Logs
- Two Active or Two Passive Nodes
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Node 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
Server Monitoring
Protection against operating system or hardware failure affecting the active node is accomplished using two
instances of the vCenter Server Heartbeat that monitor one another by sending “I’m alive” messages over the
VMware Channel. If the passive node detects that this process (the heartbeat) has failed, a failover is initiated.
Checking the vCenter Server Heartbeat Pair Status
The Server: Summary page is the default page that opens when administering the vCenter Server Heartbeat
pair. The Server: Summary page allows you to view the roles that nodes are performing (active or passive),
actions that each node is currently performing, and summary information on communications status and data
replication between nodes.The lower pane displays status information for each node in the pair.
Note To change the currently displayed node (active or passive), click the node graphical representation in
the upper pane, or select the Identity tab (Primary or Secondary) in the bottom pane.
The following (table 2-2) lists the possible system statuses and their meanings.
Table 2- 2. System Status
DescriptionIconStatus
Heartbeat service is shut down.Heartbeat service
shutdown
Heartbeat service is starting up.Initializing
(Normal status) File and registry changes on the active node are intercepted and
replicated to the passive node. Protected applications are monitored.
Replicating
File and registry replication is stopping and all protected applications may be closing
down.
Not replicating
The system is performing a failover.Switching active server
VMware Channel connections have been established between the two nodes.Connecting to peer
server
VMware Channel connections have been lost between the two nodes.Disconnecting from peer
server
File replication is stopping and, optionally, all protected applications may be closing
down.
Stopping replication
Replication is starting and protected applications are optionally starting.Starting replication
Heartbeat is initializing on the active node and starting protected applications.Starting as active server
Heartbeat is stopping. The Heartbeat service is shutting down, and will no longer
participate in replication. Optionally, protected applications may be stopped.
Heartbeat service
shutting down
The passive node has lost connection to the active node. If this condition persists
for the failover timeout, and failover is permitted between the pair of nodes, then a
failover will occur.
Lost active server
A failover has occurred,Active following failover
The Heartbeat service cannot be contacted on the node.Server not responding
VMware, Inc. 29
Chapter 2 vCenter Server Heartbeat Monitoring