Specifications
Table Of Contents
- Reference Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- vCenter Server Heartbeat Installation on Windows Server 2003
- vCenter Server Heartbeat Installation on Windows Server 2008
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel IP Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Enabling Network Monitoring
- Configuring Split-Brain Avoidance
- Managing vCenter Server Heartbeat License Keys
- Configuring Message Queue Logs
- Configuring the Maximum Disk Usage
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Status and Control
- Performance Protection
- Data Protection
- Data Protection Overview
- Other Administrative Tasks
- Troubleshooting
- Troubleshooting Unexpected Behaviors
- Two Active Servers
- Two Passive Servers
- Synchronization Failures
- Registry Status is Out of Sync
- Channel Drops
- Subnet or Routing Issues
- MaxDiskUsage Errors
- MaxDiskUsage Error Messages
- [L9]Exceeded the Maximum Disk Usage (VCChannelExceededMaxDiskUsageException)
- [L9]Exceeded the Maximum Disk Usage on the ACTIVE Server
- [L9]Exceeded the Maximum Disk Usage on the PASSIVE Server
- [L20]Out of Disk Space (VCChannelOutOfDiskSpaceException)
- Application Slowdown
- Poor Application Performance
- Both Servers Can Accommodate the Initial Load but the Load Has Increased
- One Server Can Provide Adequate Resource Support, but the Other Cannot
- Scheduled Resource Intensive Tasks
- Appendix - Setup Error Messages
- Glossary
Reference Guide
26 VMware, Inc.
LAN
When deployed in a LAN environment, vCenter Server Heartbeat requires that both servers use the same
Principal (Public) IP address. Each server also requires a separate VMware Channel IP address on a separate
dedicated subnet.
Primary Server
Three NICs (1 x Public and 2 x Channel) are recommended for redundancy in the event one channel fails. A
minimum of two NICs (one for the Channel, and one for the Public) are required in this configuration.
Split-brain Avoidance should be configured.
Principal (Public) network connection configured with the following:
Static IP address
Correct network mask
Correct Gateway address
Correct preferred and secondary (if applicable) DNS server address
NetBIOS enabled
Channel Network connection(s) configured with the following:
Static IP address in a different subnet than the Principal (Public) network with a different IP address
than the Secondary server channel NIC
Correct network mask
No Gateway IP address
No DNS server address
NetBIOS enabled (setup will disable this during the installation process)
Secondary Server
Networking components on the Secondary server must be configured as follows:
Same number of NICs as the Primary server
Principal (Public) network connection configured with temporary network settings
Channel network connection(s) configured with the following:
Static IP address in a different subnet than the Principal (Public) network with a different IP address
than the Primary server channel NIC
Correct network mask
No Gateway IP address
No DNS IP address
NetBIOS enabled (setup will disable this during the installation process
File and print sharing enabled
WAN
Deploying vCenter Server Heartbeat in a WAN environment requires additional considerations. Each server
within the vCenter Server Heartbeat pair requires its own separate Principal (Public) IP address and a VMware
Channel IP address in a separate dedicated subnet.
N
OTE When installing vCenter Server Heartbeat in a LAN environment, do not enable the Low Bandwidth
Module as this is designed for WAN deployments.