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
Subnet or Routing Issues
In a LAN or WAN deployment, the following connection problems can occur.
LAN Deployment
Incorrectly congured 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 Principal (Public) NIC and/or one or more channels
sharing the same subnet.
Solution
◆
If vCenter Server Heartbeat is deployed in a LAN environment, the Principal (Public) IP address and the
VMware Channel IP address on a server should be in separate subnets. When multiple redundant channels
are present, each should have its own subnet. Check the network conguration for each NIC on both
servers in the pair and correct any issues.
WAN Deployment
Incorrect routing can prevent the active and passive servers from connecting in a WAN environment.
Problem
The VMware Channel disconnects or fails to connect in a WAN deployment.
Cause
When the VMware Channel disconnects or fails to connect in a WAN deployment, the static route might not
be congured or might be congured incorrectly.
When vCenter Server Heartbeat is deployed in a WAN, the Principal (Public) IP address and the VMware
Channel IP addresses cannot be in dierent subnets, because there usually is a single network path between
the two servers. Congure a static route between the endpoints to route trac in the VMware Channel.
Solution
◆
Refer to knowledge base article 1008451 (vCSHB-Ref-466) - Creating a static route for the VMware Channel
Connection in a WAN Environment for a detailed discussion about WAN channel routing issues, and for
instructions on conguring a static route for the VMware Channel.
VMware, Inc. 93
Chapter 10 Troubleshooting