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
Cause
This unusual condition points to an application or Windows experiencing a fault on the passive node. A sudden
restart of the passive node can occur due to the following causes:
■
The node is configured for automatic software update management and some updates force the node 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 node 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 86 for more information on this topic.
Passive Node Does Not Meet Minimum Hardware Requirements
Inadequate hardware can cause channel drops and result in poor performance.
Problem
The data rate between nodes is very fast during a Full System Check and the VMware Channel drops.
Cause
The passive node does not meet the recommended hardware/resource requirements for vCenter Server
Heartbeat or it meets the requirements, but is much less powerful than the active node.The underpowered
node cannot apply the received replication data from the active node at the rate that the data is sent to the
passive node.
Solution
◆
To avoid reinstalling vCenter Server Heartbeat, upgrade the hardware or add additional resources such
as memory or CPU, on the passive node. Establish the identity (Primary or Secondary) of the affected
node 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.
Problem
The VMware Channel intermittently drops or disconnects and reconnects.
Cause
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
86 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide