6.4
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Application Protection Overview
- Applications: Applications Tab
- Reset the Application Health Status
- View Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Start and Stop 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
- Status and Control
- vCenter Server Heartbeat Console
- About vCenter Server Heartbeat Console
- Work with Groups and Pairs
- Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
- Review the Status of vCenter Server Heartbeat Groups and Pairs
- Exit vCenter Server Heartbeat Console
- Shut Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Client Plug-in
- Uninstall vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- 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
- Glossary
VMware, Inc. 21
Chapter 2 Configuring vCenter Server Heartbeat
Configuring Channel Routing
Channel IP routing defines the IP addresses used to communicate between the Primary and Secondary
servers. Each link has a pair of addresses, one for the Primary, and one for the Secondary.
To add an additional VMware Channel after installing the NICs and configuring them
1Click the Channel tab. Click Add Row to add the new IP addresses for both the Primary and Secondary
server to the VMware Channel IP Routing table.
2 Use the drop-down menu to view a list of available IP addresses on the local server.
3 Type the remote server IP address.
4 To change the VMware Channel IP addresses, select and edit the entry in the table.
5Click Next or Finish.
Configuring the Default Channel Port
VMware Channel uses the Default Channel Port to communicate between the Primary and Secondary server.
Do not change this port unless another application is using it. To change the Default Channel Port, click the
Channel tab, edit the default entry (57348), and click Next or Finish.
Configuring Low Bandwidth Module
This feature is automatically enabled during installation when configured for a WAN. To disable this feature,
click the Channel tab and clear the Low Bandwidth Optimization check box. When enabled, the VMware
Channel optimizes communications for low bandwidth connections. Low Bandwidth Optimization (LBO)
stores data on disk rather than in memory and is essential for WAN installations or when bandwidth is limited.
This setting should not be changed unless directed to do so by VMware Support.
N
OTE This feature is designed for implementations where the available throughput on the VMware Channel
is slower than 10 Mbit/s. Do not enable the Low Bandwidth Module in a LAN, this feature is not designed to
work in a LAN where the throughput is much faster.