6.4
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Application Protection Overview
- Applications: Applications Tab
- Reset the Application Health Status
- View Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Start and Stop 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
- Status and Control
- vCenter Server Heartbeat Console
- About vCenter Server Heartbeat Console
- Work with Groups and Pairs
- Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
- Review the Status of vCenter Server Heartbeat Groups and Pairs
- Exit vCenter Server Heartbeat Console
- Shut Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Client Plug-in
- Uninstall vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Glossary
VMware, Inc. 71
10
This chapter includes the following topics:
“Troubleshooting Unexpected Behaviors” on page 71
“Two Active Servers” on page 71
“Two Passive Servers” on page 73
“Synchronization Failures” on page 74
“Registry Status is Out of Sync” on page 76
“Channel Drops” on page 76
“Subnet or Routing Issues ” on page 80
“MaxDiskUsage Errors” on page 80
“MaxDiskUsage Error Messages” on page 81
Troubleshooting Unexpected Behaviors
The following unexpected behaviors illustrate symptoms, causes and resolution for a given scenario.
Two Active Servers
When two identical active servers are live on the same network, vCenter Server Heartbeat refers to the
condition as Split-brain syndrome. Two active servers do not occur by design and when detected, must be
resolved immediately.
Symptoms
Split-brain syndrome is identified 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 conflict occurs on a server pair running vCenter Server Heartbeat on the Principal (Public)
IP address.
A name conflict occurs on a server pair running vCenter Server Heartbeat. In a WAN environment the
Primary and Secondary servers connect to the network using different IP addresses. However, if the
servers are running with the same name and are visible to each other across the WAN, a name conflict
occurs.
Clients (for example, VI Client, ESX, etc.) cannot connect to the server running vCenter Server Heartbeat.
Troubleshooting
10