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
Enabling Failover in a WAN
By default, when deployed in a WAN environment, failover is disabled.To enable failover in a WAN environment,
follow the steps below.
Procedure
1 Navigate to the Network: Network Monitoring page.
2 Click Configure Auto-switchover.
3 Select the Auto-switchover if client network connectivity lost for check box.
4 Configure the number of pings to wait before performing the failover.
5 Click OK.
Managing Split-brain Avoidance
Split-brain Avoidance ensures that only one node is active if the VMware Channel connection is lost, but both
nodes remain connected to the Public network. Split-brain Avoidance works by pinging from the passive node
to the active node across the Public network. If the active node responds, the passive node does not failover,
even if the VMware Channel connection is lost.
Procedure
1 To enable Split-brain Avoidance, navigate to the Server: Monitoring page.
2 Click Configure Failover.
3 Select Prevent failover if channel heartbeat is lost but Active server is still visible to other servers
(recommended).
4 Click OK.
Managing Max Server Time Difference
vCenter Server Heartbeat generates a warning if the Primary and Secondary node's system clocks are not
synchronized.The threshold for time difference is configured on the Server: Summary page.
Procedure
1 Select the Server: Summary tab and click Configure to display the Server: Summary Configure dialog.
2 Enter a value (seconds) or use the arrow buttons to select an alert threshold value for time difference
between nodes, which is checked at handshake following startup.
3 Click OK.
Initiating a Failover
After configuring vCenter Server Heartbeat to protect all required applications and data, the Secondary node
can take over from the Primary node in a managed and seamless manner called a failover.
This is particularly useful when maintenance work performed on the Primary requires rebooting the node.
VMware, Inc. 51
Chapter 3 Managing vCenter Server Heartbeat