Specifications
Table Of Contents
- Reference Guide
- Contents
- About This Book
- Getting Started
- Installation
- vCenter Server Heartbeat Implementation
- vCenter Server Heartbeat Installation on Windows Server 2003
- vCenter Server Heartbeat Installation on Windows Server 2008
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel IP Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Enabling Network Monitoring
- Configuring Split-Brain Avoidance
- Managing vCenter Server Heartbeat License Keys
- Configuring Message Queue Logs
- Configuring the Maximum Disk Usage
- System Administration and Management
- Server Protection
- Network Protection
- Application Protection
- Status and Control
- Performance Protection
- Data Protection
- Data Protection Overview
- Other Administrative Tasks
- 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
- Appendix - Setup Error Messages
- Glossary
Reference Guide
176 VMware, Inc.
The preconfigured WScript command creates an event in the Application Event Log and can be
customized to include vCenter Server Heartbeat specific informational variables as detailed in Table 12-1.
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"
3Click Apply to save the changes and enforce the defined notification rules.
4 To restore the configuration to the last saved state, click Reset.
Test Alert Reporting
Click Test Alert Reporting to run a test alert email. This way you can avoid triggering an actual alert during
the operation of the active server.
Table 12-1. Script Variables
Variable Value
$EventId Id of event as listed above
$EventName Human-readable name of event
$EventDetail Detail message for event
$EventTime Time at which event occurred