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
Figure 1- 5. Single NIC Configuration
LAN and Stretched vLAN Deployment
When deployed in a LAN, the Public NIC on the active node is configured with both a unique permanently
assigned Management IP address for administrative access and the Public IP address which allows traffic
from clients.The Public NIC on the passive node is configured to use its unique permanently assigned
Management IP address. When a failover occurs, the Public IP address assigned to the currently active node
is removed and reassigned to the new active node.The new passive node remains accessible to administrators
via the Management IP address but is not visible to clients.The newly active node then starts accepting traffic
from clients.
The NICs on the active and passive nodes used for the VMware Channel are configured so that their IP
addresses are outside of the subnet range of the Public network. These addresses are referred to as VMware
Channel addresses.
DNS in a LAN or Stretched vLAN
When deployed in a LAN or stretched vLAN configuration, should a failover occur, the Public IP address is
simply removed from the currently active server and reassigned to the currently passive server without a need
to update DNS. Clients continue to communicate to the same Public IP address that was used before the
failover.
WAN Deployment
When configured for a WAN deployment, configure the VMware Channel to use static routes over switches
and routers to maintain continuous communications independent from corporate or public traffic.
DNS in a WAN Deployment
When deployed in a WAN configuration, should a failover occur, vCenter Server Heartbeat automatically
updates DNS with the IP address of the new active server using vCenter Server Heartbeat's own DNSUpdate.exe
utility.
VMware, Inc. 13
Chapter 1 Introduction