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
5vCenter Server Heartbeat Diagnostics
You can use a variety of procedures for diagnosing and fixing problems that you may encounter when using
vCenter Server Heartbeat.You can use troubleshooting procedures to investigate the causes of such problems
and attempt to correct them yourself, or you can obtain assistance from VMware Technical Support. The
following unexpected behaviors illustrate Problems, Causes, and Solutions for a given scenario.
This chapter includes the following topics:
■
“Collecting Diagnostic Logs,” on page 79
■
“Two Active or Two Passive Nodes,” on page 80
■
“Synchronization Failures,” on page 82
■
“Registry Status is Out-of-Sync,” on page 85
■
“Channel Drops,” on page 85
■
“Subnet or Routing Issues,” on page 89
■
“MaxDiskUsage Errors,” on page 90
■
“Application Slowdown,” on page 94
Collecting Diagnostic Logs
In the event that it is necessary to collect diagnostic logs for vCenter Server Heartbeat, launch the LogCollector
tool to automatically collect all required diagnostic logs for forwarding to VMware support.
Procedure
1 Right-click the vCenter Server Heartbeat System tray icon.
2 Select Collect Diagnostic Logs.
The vCenter Server Heartbeat LogCollector is displayed.
3 Click either Collect logs from all machines or Collect logs from this machine only.
The LogCollector displays the progress of collecting logs and once complete, provides a .zip file containing
the logs located in at <install_location>\VMware\vCenter Server Heartbeat\Log_<date>\<server>.zip
VMware, Inc. 79