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
Hardware or Driver Issues on VMware Channel NICs
NIC malfunctions and old or incorrect drivers can cause channel drops resulting in poor performance.
Problem
The VMware Channel intermittently drops or disconnects and reconnects.
Cause
The following are common causes of NIC problems.
■
Old or incorrect VMware Channel NIC drivers
■
Hardware failure of the hub or Ethernet switch used for the VMware Channel connection
■
Defective Ethernet patch or crossover cables
■
Improper conguration of the 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 identied
with HP/Compaq ProLiant NC67xx/NC77xx Gigabit Ethernet NICs. Check other NIC types. See knowledge
base article 1008383 (vCSHB-Ref-116) – 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 congure 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 rewalls.
Because rewalls block unauthorized network trac, congure rewalls on the route of the VMware Channel
to allow channel trac.
Problem
The VMware Channel cannot connect, or continuously connects and disconnects.
Cause
In a WAN deployment, port 57348 or any other port congured for the VMware Channel is closed on one or
more rewalls on the route between the VMware Channel NIC on the Primary server and its counterpart on
the Secondary server.
Solution
◆
Open port 57348 and any other port congured for the VMware Channel on all rewalls on the route
between the VMware Channel NIC on the Primary server and its counterpart on the Secondary server.
90 VMware, Inc.
Administrator Guide