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
■
Improper configuration of NICs used for the VMware Channel connection
■
ISP problems in a WAN environment
Solution
When a NIC problem is encountered, perform the following checks:
1 Verify that VMware Channel NIC drivers are the correct and latest versions. Known issues are identified
with HP/Compaq ProLiant NC67xx/NC77xx Gigabit Ethernet NICs. Check other NIC types. See knowledge
base article 1008383 – VMware vCenter Server Heartbeat and Gigabit Ethernet NIC drivers (NC77XX)
2 Verify hubs and Ethernet switches are operating properly. Identify and replace any defective components.
3 Test for defective Ethernet patch or crossover cables and replace if defective.
4 Correctly configure the NICs used for the VMware Channel connection.
5 Check the physical link for ISP problems.
Firewall Connection
In a LAN or WAN deployment, the VMware Channel can be connected through one or more internet firewalls.
Because firewalls block unauthorized network traffic, configure firewalls on the route of the VMware Channel
to allow channel traffic.
Problem
The VMware Channel cannot connect, or continuously connects and disconnects.
Cause
In a WAN deployment, port 57348 or any other port configured for the VMware Channel is closed on one or
more firewalls on the route between the VMware Channel NIC on the Primary node and its counterpart on the
Secondary node.
Solution
◆
Open port 57348 and any other port configured for the VMware Channel on all firewalls on the route between
the VMware Channel NIC on the Primary node and its counterpart on the Secondary node.
Channel Fails to Connect After Configuring Firewall Ports
Problem
The VMware Channel fails to connect and does not allow traffic to pass between the Primary and Secondary
nodes.
Cause
If Microsoft Windows changed the connection type from Private network to Unidentified network after the user
has configured the firewall port to allow channel communications, this may cause the firewall changes to be
reset for the new network type.
VMware, Inc. 87
Chapter 5 vCenter Server Heartbeat Diagnostics