6.3
Table Of Contents
- Administrator Guide
- Contents
- About This Book
- Getting Started
- Introduction
- Configuring vCenter Server Heartbeat
- Server Configuration Wizard
- Configuring the Machine Identity
- Configuring the Server Role
- Configuring the Client Connection Port
- Configuring Channel Routing
- Configuring the Default Channel Port
- Configuring Low Bandwidth Module
- Configuring Public IP Addressing
- Configuring for Identical Nodes
- Configuring for Non-Identical Nodes
- 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
- vCenter Server Heartbeat Console
- About vCenter Server Heartbeat Console
- Work with Groups and Pairs
- Add, Edit, Move, and Remove Pairs in VCenter Server Heartbeat Groups
- Review the Status of vCenter Server Heartbeat Groups and Pairs
- Exit vCenter Server Heartbeat Console
- Shut Down Windows Without Stopping vCenter Server Heartbeat
- 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
- Glossary
VMware, Inc. 39
4
Thischapterincludesthefollowingtopics:
“CommunicationStatus”onpage 39
“ReviewingtheVMwareChannelStatus”onpage 39
“ConfiguringPublicNetworkConnectionChecks”onpage 39
“SettingMaxServerTimeDifference”onpage 40
Communication Status
UsetheData:Traffic/QueuespagetocheckthestatusoftheVMwareChannel,theactiveserver’ssend,and
passiveserver’sreceivequeues.
Reviewing the VMware Channel Status
TheData:Traffic/QueuespagedisplaystheVMwareChannelstatusasconnected(Greensolidicon)ornot
connected(redbrokenicon),thestatisticsoftheconnectionwithregardstothedatasentbyeitherserver,and
thesizeandageoftheoldestentryintheactiveserver’ssendqueueandpassive
server’sreceivequeue.The
ChannelConnectiontabinthelowerpanedisplaystheIPaddressesusedbytheVMwareChannelforthe
PrimarytoSecondaryconnectionsandtheportthatthecommunicationsareusing.
Configuring Public Network Connection Checks
TheNetworkMonitoringpageallowsyoutoviewthestatusofthenetworkandmakeadjustmentstotheIP
addressesusedtopingmultipleserverswithinthenetwork.
ThePrincipal(Public)networkmonitoringfeature,previouslydiscussed,isenabledbydefaultduringthe
installationofVMwarevCenterServerHeartbeat.Thisfeatureintegrates
thepollingofdesignatedwaypoints
aroundthenetworkthroughtheactiveserver’sPrincipal(Public)connectiontoensureconnectivitywiththe
Principal(Public)networkisoperational.Bydefault,theIPaddressesofthedefaultgateway,theprimaryDNS
server,andtheGlobalCatalogserverareallselected.Whenoneormoreof
theautomaticallydiscovered
waypointsareco‐locatedonaphysicalmachine(leadingtoduplicationofIPaddresses),theabilitytospecify
additionalwaypointsmanuallybecomesanadvantage.TospecifyamanualtargetforPrincipal(Public)
networkchecking,clickConfigurePingstoinvokethePingConfigurationdialog.SelectthePingRouting
tabtoaddtoormodifytheexistingtargetIPaddressesforeachservertoping.
InaWANenvironment,thetargetaddressesforPrincipal(Public)networkmonitoringontheSecondary
servermaybedifferenttothoseautomaticallyselectedonthePrimaryserver.Again,theabilitytooverride
automaticallydiscoveredselections
isprovidedbymanuallyspecifyingthetargetaddress.
Principal(Public)NetworkMonitoringiscarriedoutbytheactiveservereffectivelypingingthetarget
addressesatregulartimeintervals.Thetimeintervalissetbydefaulttoevery10secondsbutthefrequency
maybeincreasedordecreasedasrequired.
Network Protection
4