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. 49
Chapter 6 Status and Control
To add a vCenter Server Heartbeat Group
1 Open vCenter Server Heartbeat Console and click Add Group in the tool bar, select Add Group from the
File menu, or right-click an existing group in the navigation panel and select Add Group form the menu.
2 Type the name for the new group into the text box and click OK. The newly created group appears in the
navigation panel on the left of the vCenter Server Center Heartbeat window.
Remove a vCenter Server Heartbeat Group
The Remove Group feature in vCenter Server Heartbeat allows you to remove existing vCenter Server
Heartbeat Groups from management.
To remove a vCenter Server Heartbeat Group
1 Select the Group to be removed in the navigation panel of vCenter Server Heartbeat Console. Click
Remove Group in the tool bar or select Remove Group from the File menu.
2 A confirmation message appears. Click Yes.
Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
When you created a vCenter Server Heartbeat Group using the instructions in “A d d o r R e m o ve a v C e n t e r
Server Group” on page 48, you created an empty container. Next you must add the connections to the Pair or
Pairs that make up your new vCenter Server Heartbeat Group.
Add a New Connection
The Add Connection feature in the vCenter Server Heartbeat Console allows you to add a new Pair Connection
to an existing vCenter Server Heartbeat Group.
To Add a new connection
1 In the navigation panel, select the vCenter Server Heartbeat Group to receive the new connection. Click
Add Connection in the tool bar, select Add Connection from the File menu, or right-click an existing
group in the navigation panel and select Add Connection to invoke the Add Connection dialog.
2 Type the Host Name or IP address for the new connection into the text box, select the Port Number (if
different from the default value of 52267), and select a group from the Add to Group drop-down list (to
add the connection to a Group other than the one currently selected).
3Click OK. The newly created connection appears in the navigation panel on the left of the vCenter Server
Heartbeat Console window and vCenter Server Heartbeat Console attempts to connect to the server. You
may be prompted to accept a secure connection certificate from the server. This allows the
communications between vCenter Server Heartbeat Console and the server to be encrypted. The Server:
Summary page updates to represent any existing network relationships of the added server.
Once you have connected to a particular server and have a valid secure connection certificate, the next
time you use vCenter Server Heartbeat Console on this client system is will automatically connect to the
server. If the certificate expires or becomes invalid, the connection may be removed from vCenter Server
Heartbeat Console and you will have to reconnect and accept the new certificate.
N
OTE If the Heartbeat vSphere Plug-in is being used during a switchover or failover the user will be
asked to accept a new Security Certificate each time the server roles change.
NOTE You may be prompted to login. If so, login using a valid administrator-level Username and
Password for the server for which you are adding a connection, and click OK.
N
OTE If the IP address of the client system changes, you may have to re-enter the username and
password credentials.