6.5
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Introduction
- Configuring vCenter Server Heartbeat
- Server Protection
- Checking the Server Pair Status
- Monitoring the Status of Servers
- Configuring Heartbeat Settings
- Network Protection
- Application Protection
- Applications: Summary Tab
- Resetting the Application Health Status
- Viewing Application Status
- Setting the Application Timeout Exception
- Remove an Application
- Manually Stop and Start 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
- Applications: Summary Tab
- Status and Control
- About vCenter Server Heartbeat Console
- Working with Groups
- Working with Pairs in vCenter Server Heartbeat Groups
- Reviewing the Status of vCenter Server Heartbeat Groups and Pairs
- Exiting vCenter Server Heartbeat Console
- Shutting Down Windows Without Stopping vCenter Server Heartbeat
- Controlled Shutdown
- vSphere Web Client Plug-in
- Uninstalling vCenter Server Heartbeat
- Performance Protection
- Data Protection
- Alerts and Events
- Troubleshooting
- Two Active or Two Passive Servers
- Synchronization Failures
- Registry Status is Out-of-Sync
- Channel Drops
- Performance Issues
- Passive Server 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
Configuring Alert Email Triggers (Alternate Method)
vCenter Server Heartbeat allows an alternate method to congure sending an alert notication that allows the
Administrator to create an event in the Application Event Log that can be customized to include vCenter Server
Heartbeat specic information variables.
Procedure
1 Select Run Command under the pertinent alert state.
2 Browse to the script to run or use a command line argument to run on the alert trigger.
The precongured WScript command creates an event in the Application Event Log and can be customized
to include vCenter Server Heartbeat specic informational variables as shown in Table 9-1.
Table 9- 1. Customized Information Variables
ValueVariable
Id of event as listed above
$EventId
Human-readable name of event
$EventName
Detail message for event
$EventDetail
Time at which event occurred
$EventTime
The following command line argument creates an event in the Application Event Log listing the machine
that caused the alert, the time the alert occurred, the name, and details of the alert:
WScript //T:10 $(installdir)\bin\alert.vbs "VMware vCenter Server Heartbeat alert on $EventHost
at $EventTime because $EventName ($EventDetail). Event Id is $EventId"
3 Click OK.
Testing Alert Reporting
vCenter Server Heartbeat allows you to test alert reporting without triggering an actual alert during the
operation of the active server.
Procedure
1 Navigate to the Logs page.
2 Click Test Alert Reporting.
A Test Alert email is sent to the congured email recipients.
Configuring Event Log Files
vCenter Server Heartbeat allows you to congure Event Log les to direct where the log le is stored and the
number of events to be recorded.
Procedure
1 Navigate to the Logs page and click Congure.
2
Select the General tab to dene the lename and path of the exported comma-separated variable (.CSV)
le.
VMware, Inc. 79
Chapter 9 Alerts and Events