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
10Troubleshooting
You can use a variety of procedures for diagnosing and xing problems that you may encounter when using
vCenter Server Heartbeat. You can use troubleshooting procedures to investigate the causes of such problems
and attempt to correct them yourself, or you can obtain assistance from VMware Technical Support. The
following unexpected behaviors illustrate Problems, Causes, and Solutions for a given scenario.
This chapter includes the following topics:
■
“Two Active or Two Passive Servers,” on page 83
■
“Synchronization Failures,” on page 86
■
“Registry Status is Out-of-Sync,” on page 88
■
“Channel Drops,” on page 89
■
“Subnet or Routing Issues,” on page 93
■
“MaxDiskUsage Errors,” on page 94
■
“Application Slowdown,” on page 97
Two Active or Two Passive Servers
When two identical servers become active on the same network or both become passive, this is not by design
and should be addressed immediately.
Two Active Servers
When two active servers are live on the same network, vCenter Server Heartbeat refers to the condition as
Split-brain syndrome. Two active servers live on the same network is critical and must be resolved immediately.
Problem
Split-brain syndrome is identied by the following symptoms:
■
Both servers in the pair are running and in an active state. The task bar icons display P / A (Primary and
active) and S / A (Secondary and active)
■
An IP address conict occurs on a server pair running vCenter Server Heartbeat on the Principal (Public)
IP address
VMware, Inc. 83