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
Table 2- 1. VMware vCenter Server Heartbeat Account Permissions
NFCMDvCSHB ConsolevSphere ClientvSphere Web ClientClient
N/AN/AUserAdministratorUserAdministratorvCenter
Server role
Local System Administrators
Group
Local System
Administrators
Group
N/AN/AN/AN/AWindows role
YesYesYesYesYesYesView
YesYesNoYesNoYesMake Active
YesYesNoYesNoYesStart/Stop
Applications
YesYesNoYesNoYesStart/Stop
Replication
YesYesNoYesNoYesShutdown
Permissions derived from the
permissions of the currently
logged in user
3
Permissions
derived from
vCSHB Console
login account
1, 2
Permissions derived
from vSphere Client
login
Permissions derived
from vSphere Client
login
Comments
Notes:
1 Only the Administrator or members of the Administrator Group can login to the vCenter Server Heartbeat
Console. User level accounts are not permitted. The account used to login will be validated against the
virtual machine where vCenter Server Heartbeat is installed. If the user account is validated as a member
of the Administrator Group, login can proceed. If the user account is not a member of the Administrator
Group, login will fail.
2 Once an Administrator has logged in to a vCenter Server Heartbeat pair using the vCenter Server Heartbeat
Console, they are not prompted for username and password during subsequent logons to that specific
pair.
3 The NFCMD utility connects to the vCenter Server Heartbeat instance and logs in using the credentials
of the currently logged in user. The vCenter Server Heartbeat service allows administrators on the local
node to log on using NFCMD and execute commands. If you are running NFCMD on another node, then
you must setup a TrustedClient relationship for the hostname and user name you want to use by connecting
first using the vCenter Server Heartbeat Console.
vCenter Server Heartbeat Console
The vCenter Server Heartbeat Console runs from either of the two nodes in the Pair or remotely from another
node in the same subnet that has vCenter Server Heartbeat or the vCenter Server Heartbeat Client Tools
installed.
Note You can install vCenter Server Heartbeat on a Windows XP and Windows Vista SP1 or later workstation
to act as a client to the Pair or on Windows Server 2003. Download and run Setup similar to vCenter Server
Heartbeat installation on the workstation and select Install Client Tools Only on the Setup Type page.
20 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide