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
Figure 1- 4. Single NIC Configuration
Figure 1- 5. Multi-NIC Configuration
The IP address a client uses to connect to the active server (the Principal (Public) IP address) must be congured
as a static IP address and not DHCP (Dynamic Host Conguration Protocol) enabled. In Figure 1-4 and Figure
1-5, the Principal (Public) IP address is congured as 192.168.1.127.
LAN Deployment
When deployed in a LAN, the Principal (Public) NIC on the active server is congured with both a unique
permanently assigned Management IP address for administrative access and the Principal (Public) IP address
which allows trac from clients. The Principal (Public) NIC on the passive server is congured to use its
unique permanently assigned Management IP address. When a switchover or failover occurs, the Principal
(Public) IP address assigned to the currently active server is removed and reassigned to the new active server.
The new passive server remains accessible to administrators via the Management IP address but is not visible
to clients. The newly active server then starts accepting trac from clients.
The NICs on the active and passive servers used for the VMware Channel are congured so that their IP
addresses are outside of the subnet range of the Principal (Public) network. These addresses are referred to as
VMware Channel addresses.
During installation, setup will switch o NetBIOS for the VMware Channel(s) on the active and passive servers
as this connection remains live and both the passive and active machines have the same NetBIOS name.
Following vCenter Server Heartbeat installation (runtime), NetBIOS is disabled across the channel(s).
14 VMware, Inc.
Administrator Guide