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. 77
Chapter 10 Troubleshooting
Symptom
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.
Causes
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 configured 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
Resolution
To resolve the issue, make the following checks.
Determine the likely source by examining the Windows event logs.
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 77 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.
Symptom
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.
Resolution
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 affected server before you perform the upgrade.
Hardware or Driver Issues on VMware Channel NICs
NIC malfunctions and old or incorrect drivers can cause channel drops resulting in poor performance.
Symptom
The VMware Channel intermittently drops or disconnects and reconnects.
Causes
The following are common causes of NIC problems.
Old or incorrect VMware Channel NIC drivers
Hardware failure of the hub or Ethernet switch used for the VMware Channel connection
Defective Ethernet patch or crossover cables