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
VMware vCenter Server Heartbeat Packet Filter Is Enabled on the Channel NIC(s)
Proper configuration requires that the packet filter be disabled on the VMware Channel NIC. When the packet
filter is enabled on the channel NICs, the following symptoms are encountered.
Problem
Interference with network traffic across the VMware Channel results in an intermittent channel connection or
no channel connection at all.
Cause
During installation, the VMware vCenter Server Heartbeat Packet Filter is installed and enabled on all NICs
on both the Primary and Secondary nodes.The Packet Filter on the VMware Channel NICs on each node is
disabled later in the installation of vCenter Server Heartbeat. If the vCenter Server Heartbeat Packet Filter is
left enabled on one or more channel NICs after installation completes, it can interfere with network traffic across
the VMware Channel.
Solution
◆
Click the Properties tab for each Channel NIC on both nodes and verify that the check box for vCenter
Server Heartbeat Packet Filter is cleared, so that the Packet Filter is disabled on that NIC.
Subnet or Routing Issues
In a LAN or WAN deployment, the following connection problems can occur.
LAN Deployment
Incorrectly configured subnets or routing can cause channel problems resulting in poor performance or failure
to connect.
Problem
The channel disconnects or fails to connect in a LAN deployment.
Cause
The channel disconnects or fails to connect due to the Public NIC and/or one or more channels sharing the
same subnet.
Solution
◆
If vCenter Server Heartbeat is deployed in a LAN environment, the Public IP address and the VMware
Channel IP address on a node should be in separate subnets.When multiple redundant channels are
present, each should have its own subnet. Check the network configuration for each NIC on both nodes
in the pair and correct any issues.
VMware, Inc. 89
Chapter 5 vCenter Server Heartbeat Diagnostics