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
Reviewing the VMware Channel Status
The Data: Traffic/Queues page displays the VMware Channel status.
VMware Channel status can be displayed as:
■
Connected – A green solid arrow icon
■
Waiting – A solid orange icon is displayed when the channel has just disconnected. vCenter Server
Heartbeat will wait for a configured amount of time before deciding the channel is disconnected
■
Not connected – A red broken line icon
Statistics of the connection with regards to the data sent by either node, and the size and age of the oldest
entry in the active node’s send queue and passive node’s receive queue are displayed on this page.
The Channel Connection tab in the lower pane displays the IP addresses used by the VMware Channel for
Primary to Secondary connections and the port that communications are using.
Network Isolation Protection
vCenter Server Heartbeat monitors the network to identify when a network failure has occurred and takes the
appropriate action to maintain communications and prevent the occurrence of two active nodes.
Typical Failover and Active Node Isolation Scenarios
Failover
The following scenario assumes that vCenter Server Heartbeat is deployed in a LAN and the active node has
failed and is no longer available.
Upon detection of missed heartbeats, vCenter Server Heartbeat on the passive node performs the following
steps:
1 As soon as the passive node detects that the VMware Channel is experiencing missed heartbeats, it
attempts to ping the active node's Management IP address via the Public network using the passive node's
NIC configured with the Management IP address. If the ping is successful, the passive node will veto the
failover. If the ping is unsuccessful, it will continue to the next step.
Note Since the passive node assumes that active node has failed, the passive node will not attempt to
verify synchronization with the active node.
2 At this point, the passive node checks the configured value of the Failover timeout and starts a "Heartbeat
lost" countdown.The passive node continues with the next step.
3 The passive node attempts to ping the configured waypoints on the Public network to determine if it is still
visible on the Public network. If pings to the waypoints on the Public network are unsuccessful, the passive
node remains passive and takes no action. If pings to the waypoints on the Public network are successful,
the passive node continues to the next step.
4 At this point, failover to the passive node is postponed until the value of the Failover timeout has elapsed.
5 The passive node changes its role to active, assumes the Public IP address, and starts all services.
6 As the new active node, it will begin accepting traffic from clients.
VMware, Inc. 31
Chapter 2 vCenter Server Heartbeat Monitoring