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
2vCenter Server Heartbeat Monitoring
After installation of vCenter Server Heartbeat, initial operational configuration and day-to-day operations are
performed using the vCenter Server Heartbeat Console. vCenter Server Heartbeat operates over a Pair of
vCenter Server Heartbeat nodes and is administered in these Pairs. The vCenter Server Heartbeat Console
is used to administer one or more Pairs.
This chapter includes the following topics:
■
“Supported vCenter Server Heartbeat Clients,” on page 19
■
“vCenter Server Heartbeat Console,” on page 20
■
“vSphere Web Client Plug-in,” on page 25
■
“vSphere Client Plug-in,” on page 27
■
“Server Monitoring,” on page 29
■
“Network Monitoring,” on page 30
■
“Application Monitoring,” on page 34
■
“Performance Monitoring,” on page 35
■
“Monitoring Data Replication,” on page 36
Supported vCenter Server Heartbeat Clients
vCenter Server Heartbeat allows the use of multiple clients to provide basic management of vCenter Server
Heartbeat pairs. vCenter Server Heartbeat communicates with the following clients:
Note Each client permits differing levels of permissions based upon either vCenter Server role or user account
permissions as indicated below.
Available Clients:
■
vSphere Web Client (NGC)
■
vSphere Client (C#)
■
vCenter Server Heartbeat Console (local or remote)
■
NFCMD (command line)
The following (table 2-1) provides the level of permissions for each client based upon user role.
VMware, Inc. 19