6.5
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Introduction
- Configuring vCenter Server Heartbeat
- Server Protection
- Checking the Server Pair Status
- Monitoring the Status of Servers
- Configuring Heartbeat Settings
- Network Protection
- Application Protection
- Applications: Summary Tab
- Resetting the Application Health Status
- Viewing Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Stop and Start Applications
- Configuring Applications
- Application Maintenance Mode
- Reviewing the State of an Application
- Reviewing the Applications Log
- Filtering Application Log Entries
- Applications: Services Tab
- Applications: Tasks Tab
- Applications: Plug-ins Tab
- Applications: Summary Tab
- Status and Control
- About vCenter Server Heartbeat Console
- Working with Groups
- Working with Pairs in vCenter Server Heartbeat Groups
- Reviewing the Status of vCenter Server Heartbeat Groups and Pairs
- Exiting vCenter Server Heartbeat Console
- Shutting Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Web Client Plug-in
- Uninstalling vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Two Active or Two Passive Servers
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Server 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
Channel Fails to Connect After Configuring Firewall Ports
Problem
The VMware Channel fails to connect and does not allow trac to pass between the Primary and Secondary
servers.
Cause
If Microsoft Windows changed the connection type from Private network to Unidentied network after the
user has congured the rewall port to allow channel communications, this may cause the rewall changes
to be reset for the new network type.
Solution
The rewall rules must be recreated to allow trac to pass through for the Client Connection port and the
Default Channel port. VMware recommends that the rewall be congured to allow the Client to connect to
the Client Connection port by process, nfgui.exe, rather than by a specic port. To enable Channel
communications between servers, change the Network List Manager Policy so that the VMware Channel
network is identied as a Private Network, and not the default Unidentied Network, and congure the
rewall to allow trac to pass through on Port 57348, the Default Channel port.
Incorrect VMware Channel Configuration
An incorrectly congured channel connection can prevent proper communication and replication.
Problem
The following problems are experienced:
■
IP conicts occur on one of the VMware Channel IP addresses
■
The VMware Channel does not connect, or connects and disconnects
Cause
The list below provides the most common miscongurations.
■
Identical IP addresses at each end of the VMware Channel
■
IP addresses in dierent subnets without static routing at each end of the VMware Channel
■
VMware Channel NIC congured for DHCP when a DHCP server is not available
During installation, vCenter Server Heartbeat congures the VMware Channel NICs with user-provided
information. Incorrect information or incorrectly modifying the VMware Channel NIC conguration after
installation causes the VMware Channel to fail communicating.
On rare occasions, if the Primary and Secondary servers have NICs of the same type in a dierent order, both
the name and IP address of a VMware Channel NIC on the Primary server can transfer to the Principal (Public)
NIC on the Secondary or the name and IP address of the Principal (Public) NIC can transfer to a VMware
Channel NIC. Similarly, the names of the VMware Channel NICs can reverse on the Secondary server. You
must reconcile the names of the NICs with their physical identities and assign the correct IP address to each
NIC on the Secondary server.
VMware, Inc. 91
Chapter 10 Troubleshooting