6.6
Table Of Contents
- vCenter Server Heartbeat Administrator's Guide
- Contents
- About This Book
- Introduction
- vCenter Server Heartbeat Monitoring
- Supported vCenter Server Heartbeat Clients
- vCenter Server Heartbeat Console
- vSphere Web Client Plug-in
- vSphere Client Plug-in
- Server Monitoring
- Network Monitoring
- Application Monitoring
- Performance Monitoring
- Monitoring Data Replication
- Managing vCenter Server Heartbeat
- Server Configuration Wizard
- Managing Heartbeat Settings
- Managing Application Protection
- Managing Services
- Managing Tasks
- Managing Rules
- Managing Plug-ins
- Managing Data Protection
- Maintaining vCenter Server Heartbeat
- vCenter Server Heartbeat Diagnostics
- Collecting Diagnostic Logs
- Two Active or Two Passive Nodes
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Node Does Not Meet Minimum Hardware Requirements
- Hardware or Driver Issues on VMware Channel NICs
- Firewall Connection
- Channel Fails to Connect After Configuring Firewall Ports
- Incorrect VMware Channel Configuration
- VMware vCenter Server Heartbeat Packet Filter Is Enabled on the Channel NIC(s)
- Subnet or Routing Issues
- MaxDiskUsage Errors
- Application Slowdown
- Glossary
Resetting the Application Health Status
If a problem occurs (for example, a failed service or rule), the Application Health status becomes Degraded.
Even if vCenter Server Heartbeat corrects the problem (for example, restarts the failed service) or the user
corrects the problem, the Degraded status remains until manually cleared by the Administrator. In this state,
the Service Discovery Task will not run.
To reset the Application Health status
Procedure
◆
After acknowledging the problem and solving it, click Clear in the Application Health pane of the Applications:
Summary page to reset the Application Health status.
The status updates to provide the actual current Application Health status.
Setting the Application Timeout Exception
vCenter Server Heartbeat can alert the Administrator if the time taken to start or stop an entire application
exceeds the expected time during the following operations:
■
vCenter Heartbeat startup
■
Shutdown with protected applications
■
Failover
■
When the Administrator selects Start Application
■
When the Administrator selects Stop Application
Note If there are multiple applications installed, vCenter Server Heartbeat will total the individual timeouts
set for each application and issue a single Application Timeout Exception alert.
Configuring Timeout Settings
Note The Start Timeout value should be configured according to vCenter inventory size and the Stop Timeout
values according to inventory size and operational load. For example, if the inventory is large (more than 500
hosts and 15K virtual machines, the Start time can be 20-30 minutes. Use the resulting Start Timeout experienced
as a guide to assist in determining the Stop Timeout value.
Procedure
1 Right-click the selected application and select Edit from the menu or select the application and click Edit
at the top of the pane to invoke the Edit Application dialog.
2 Enter new values (seconds) into the Stop Timeout and Start Timeout text boxes or use the arrow buttons
to adjust the values.
3 ClickOK.
VMware, Inc. 55
Chapter 3 Managing vCenter Server Heartbeat