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
Procedure
1 Select the task from the task list.
2 Right-click on the existing task and select Run Now from the menu or click Run Now at the top of the
pane.
vCenter Server Heartbeat immediately launches the task.
Managing Rules
Rules are implemented by plug-ins (there are no user-defined rules). Rules can be configured with rule actions,
which are tasks to be performed when a rule triggers. Rules have two trigger properties:
■
Timed – They must evaluate as true continuously for the specified duration to trigger.
The timed rule provides three recovery actions, labeled as On First Failure, On Second Failure, and On
Third Failure in the vCenter Server Heartbeat Console.
Timed rules are triggered when a specific condition registers as true for a specified length of time.Timed
rules are normally used in conditions where immediate triggering is undesirable; for example, when the
CPU is configured to trigger when it exceeds 90% for five minutes, the timed rule requires that the threshold
must be exceeded for 5 minutes before it can trigger rather than the moment the CPU exceeds 90%.
■
Latched – They trigger as soon as they evaluate to true.
The latched rule provides only one recovery action, labeled as On Failure in the vCenter Server Heartbeat
Console.
Latched rules are triggered only once and then are disabled until they are re-enabled by manual intervention
from the administrator. Usually latched rules should be used in situations where multiple triggering is
undesirable or could cause problems. Latched rules provide the functionality to alert the administrator
about a problem once and then stop triggering until the problem has been fixed.
Editing a Rule
Rules are implemented by plug-ins and cannot be created by users. Each plug-in contains a default set of rules
with options that may be modified by the user.
Procedure
1 Right-click on the rule and select Edit from the menu or click Edit at the top of the pane.
The following parameters can be edited for each rule:
■
Condition – the condition being evaluated
■
Duration – the length of time the condition exists (if a timed rule)
■
Interval – the length of time between rule checks
■
First Failure – action to take upon first failure (default setting is Alert)
■
Second Failure – action to take upon second failure (default setting is Alert)
■
Third Failure – action to take upon third failure (default setting is Alert)
2 Edit the parameters of the rule and click OK.
VMware, Inc. 61
Chapter 3 Managing vCenter Server Heartbeat