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
◆
To configure Maximum Disk Usage, click the Logs tab of the Configure Server wizard (Figure 3-7), type
the maximum dedicated disk space allocated for message queue log files, and click Finish.
Managing Heartbeat Settings
The Server: Monitoring page provides three features to manage server monitoring operations:Configure Pings,
Configure Failover, and Configure Response Times.
Configuring Pings
During startup of vCenter Server Heartbeat, the IP addresses of all NICs configured for the VMware Channel
and Management IP addresses are automatically added to the server monitoring ping configuration. Use the
Server: Monitoring Ping Configuration dialog to add additional ping targets. Server Monitoring ping configuration
allows vCenter Server Heartbeat to send pings across the VMware Channel in addition to heartbeat (“I’m alive”
messages). Additionally, it allows vCenter Server Heartbeat to ping the other node in the pair over the Public
network via the Management IP address to confirm that the node is still operational and providing service.
To add additional ping targets:
Procedure
1 Click Configure Pings to open the Server Monitoring: Ping Configuration dialog.
2 Select the Ping Settings tab to configure the Ping Interval.
3 Select the Ping Routing tab to add additional ping targets.
4 Click OK.
Managing Public Network Connection Checks
The Network Monitoring page allows you to make adjustments to IP addresses used to ping multiple nodes
within the network and view the status of the network.
The Public network monitoring feature is enabled by default during the installation of VMware vCenter Server
Heartbeat. This feature integrates the polling of designated waypoints around the network through the active
node’s Public connection to ensure connectivity to the Public network is operational. By default, the Primary
DNS server, Default Gateway, and Global Catalog server IP addresses are all selected. When one or more of
the automatically discovered waypoints are co-located on a single node (leading to duplication of IP addresses),
the ability to override existing settings and specify additional waypoints manually becomes an advantage.
Procedure
1 To manually specify a ping target for Public network checking, click Configure Pings.
2 When the Ping Configuration dialog is displayed, select the Ping Routing tab.
48 VMware, Inc.
vCenter Server Heartbeat Administrator's Guide