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
VMware, Inc. 41
Chapter 3 vCenter Server Heartbeat Installation on Windows Server 2003
14 Select the Principal (Public) NIC(s). The IP address information is displayed for each NIC.
vCenter Server Heartbeat software can be deployed in a configuration where both servers have the same
Principal (Public) IP address, for instance, in a standard Local Area Network (LAN) deployment where
both machines are in the same subnet.
Alternatively vCenter Server Heartbeat can be deployed where the Principal (Public) IP addresses differ,
for instance, in a Wide Area Network (WAN) deployment where the Primary and Secondary servers are
located in different sites and subnets where client access is therefore bound by the standard network
routing to allow the correct connectivity to the server according to its locale.
15 Select LAN: Configure Primary and Secondary servers with the same Public IP addresses or
WAN: Configure Primary and Secondary servers with different Public IP addresses.
You have the following options:
For a WAN installation with different subnets, go to Step 17.
For LAN installation or same subnet WAN installs, continue with Step 16.