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
[L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
This message indicates that you have exceeded the amount of allocated disk space reserved for the active
node’s send queue.
Problem
Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from
the active node.
Cause
A temporary interruption in the VMware Channel, or insufficient VMware Channel bandwidth to support the
volume of replication traffic starts filling the active node's send queue.The size of the queue eventually exceeds
the configured disk quota.
Solution
◆
Assuming no other channel connection issues exist (see knowledge base article 1008551 – Troubleshooting
VMware vCenter Server Channel Drops), you can increase the amount of disk space allotted to the queues.
The default setting is 1GB, which can be insufficient on nodes with a large volume of replication traffic and
limited VMware Channel bandwidth. If you have sufficient disk space, set the queue size to zero (unlimited)
so vCenter Server Heartbeat can use any free disk space to store the queues.
[L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
This message indicates that you have exceeded the amount of allocated disk space reserved for the passive
node’s receive queue.
Problem
Replication stops and the vCenter Server Heartbeat Event Log displays the error message originating from
the passive node.
Cause
Two of the most common causes are shown below:
■
The bottleneck lies between the VMware Channel NIC and the disk subsystem on the passive node.
Replication traffic passes across the VMware Channel faster than it can be written to disk on the passive
node.The excess is buffered temporarily in the passive node’s receive queue.The size of the queue can
eventually exceed the allotted disk quota.
■
If the passive node is much less powerful than the active node in terms of processor speed, RAM, or disk
performance, it can lag behind the active node during periods of high replication activity. Monitor one or
more Windows performance counters to determine the component experiencing sustained high activity.
Intensive page file use or persistently large disk queue length can indicate a problem. Upgrade one or
more physical or resource components of the node.
Either node can be active or passive. If the Secondary is more powerful than the Primary, hardware or
resource-related issues can only occur while the Secondary is in the active role.
92 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide