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
3 Select or clear check boxes for each of the following items to select actions to take if the configured Failover
timeout is exceeded.
Note If the first two check boxes are not selected, failover will not occur in a LAN.
When the configured Failover timeout value has elapsed, vCenter Server Heartbeat will evaluate, in order,
the following pre-configured rules before taking action:
Important Options selected when configuring failover via the Configure Failover dialog work in concert
with Failure actions for Rules and Services. For example, if you disable failover by clearing the first two
check boxes but set Failure actions to Switchover, failover will be prevented.
If either Server: Monitoring Ping Routing or Network Monitoring Ping Routing is misconfigured, unpredictable
behavior can occur.
■
Failover from Primary server to Secondary server if channel heartbeat is lost for failover timeout
If the heartbeat is lost for the configured Failover timeout, failover from the Primary node to the
Secondary node.
■
Failover from Secondary server to Primary server if channel heartbeat is lost for failover timeout
If the heartbeat is lost for the configured Failover timeout, failover from the Secondary node to the
Primary node.
■
Prevent failover or auto-switchover while not synchronized
If the Primary and Secondary node's registry or protected files are not synchronized, do not allow to
failover.
■
Prevent Failover if channel heartbeat is lost but Active server is still visible to other servers
If communications over the VMware Channel are lost for the configured Failover timeout but the node
can successfully ping configured ping targets, failover is prevented.
■
Make the server passive if the Channel and Public networks are lost for the configured failover timeout
If communications over the VMware Channel are lost for the configured Failover timeout and the
node's attempt to ping configured targets are unsuccessful for the Failover timeout, the node will
become passive to prevent the possibility of split-brain.
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 rules have been evaluated vCenter Server Heartbeat will take action based upon the configured
Failover timeout.
4 Click OK.
Managing Response Times
vCenter Server Heartbeat also allows you to configure the time to wait following a channel connection before
starting replication and the time to wait following channel disconnection before stopping replication.
Procedure
1 Click Configure Response Times to open the Server Monitoring: Response Times dialog.
2 Type new values (seconds) into the fields or use the arrow buttons to select new values.
3 Click OK.
50 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide