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
Channel Drops
When the VMware Channel loses connection between the servers, the following scenarios can occur.
Performance Issues
Poor performance can be experienced as a result of a channel loss.
Problem
The message java.io.IOException: An existing connection was forcibly closed by the remote host
appears in the active server's NFLog.txt file, and the VMware Channel connection between the servers
is lost.
Cause
This unusual condition points to an application or Windows experiencing a fault on the passive server. A
sudden restart of the passive server can occur due to the following causes:
■
The server is congured for automatic software update management and some updates force the server
to restart
■
A software or Operating System issue that occasionally fails and requires a system restart
■
The VMware vCenter Server Heartbeat service experiences problems, does not respond, or terminates
unexpectedly
Solution
To resolve the issue, perform the following checks.
1 Determine the likely source by examining the Windows event logs.
2 If the server does not display evidence of a system restart or unresponsive application, one or both of the
VMware Channel NICs could be forcing a channel disconnection. See “Hardware or Driver Issues on
VMware Channel NICs,” on page 90 for more information on this topic.
Passive Server Does Not Meet Minimum Hardware Requirements
Inadequate hardware can cause channel drops and result in poor performance.
Problem
The data rate between the servers is very fast during a Full System Check and the VMware Channel drops.
Cause
The passive server does not meet the recommended hardware requirements for vCenter Server Heartbeat or
it meets the requirements, but is much less powerful than the active server. The underpowered server cannot
apply the received replication data from the active server at the rate that the data is sent to the passive server.
Solution
◆
To avoid reinstalling vCenter Server Heartbeat, upgrade the hardware, such as memory or CPU, on the
passive server. Establish the identity (Primary or Secondary) of the aected server before you perform
the upgrade.
VMware, Inc. 89
Chapter 10 Troubleshooting