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
Reference Guide
20 VMware, Inc.
Configuring the Machine
The Machine tab is used to set the server Physical Hardware Identity, Active Server, and Client Connection
Port.
The Machine Identity
The machine identity is either Primary or Secondary and once assigned does not normally change during the
life of the server.
To change the machine identity
1Click the Machine tab and select a Physical Hardware Identity for the local machine.
2Click Next or Finish.
Configuring the Server Role
To change the server role, click the Machine tab, select the Current Role of the local machine, and click Next
or Finish.
Configuring the Client Connection Port
Clients such as the vCenter Server Heartbeat Console use the Client Connection Port to connect to vCenter
Server Heartbeat. Do not change this port unless another application is using it. To change the Client
Connection Port, click the Machine tab, edit the default entry (52267) and click Next or Finish.
Configuring the Channel
The Channel tab is used to configure the Channel Routing, Default Channel Port, and Low Bandwidth
Optimization.
CAUTION The machine Identity should only be changed when directed to do so by VMware Support or
when instructed to by a knowledge base article. vCenter Server Heartbeat is designed not to allow two
passive or two active servers to connect.
NOTE Before changing the role of the local server, verify that the other (remote) server in the pair is not already
performing the same role.