This article provides information about how to use the vCenter Server Heartbeat Console to configure network monitoring and view the network status of your vCenter Server Heartbeat server pair.
The vCenter Server Heartbeat Console provides you the opportunity to configure network monitoring and view the status of your network. Configuration of network monitoring follows the procedure listed below.
To configure network monitoring, navigate to Start > Programs > VMware > VMware vCenter Server Heartbeat > Manage Server . When vCenter Server Heartbeat Console opens, select the Network tab.
The Network Monitoring page provides the opportunity to view the status of your network and configure the network monitoring IP addresses and options.
vCenter Server Heartbeat monitors the network by sending pings to designated servers in the network. By default, vCenter Server Heartbeat configures the default gateway, DNS server, and global catalog server. The configuration can be modified to ping any server available on the Principal (Public) network.
To modify the ping configuration:
Click the Configure Pings button to open the Network Monitoring: Ping Configuration dialog.
Edit the current settings as desired.
Click OK to apply the changes.
Review the Ping Targets From Currently Active Server panel to ensure the ping targets are reachable.
Split-brain Avoidance ensures that only one server becomes active if the channel connection is lost, but all servers remain connected to the Principal (Public) network. Split-brain Avoidance works by pinging from the passive server to the active server across the Principal (Public) network. If the active server responds, the passive does not failover, even if the channel connection is lost. WAN installations require different IP addresses on the Principal (Public)
network for the local and remote servers.
To enable Split-brain Avoidance, open the Server Monitoring page in the vCenter Server Heartbeat Console, click Configure Failover , and selecting Prevent failover if channel heartbeat is lost but Active server is still visible to other servers (recommended) .
You must have Management IP addresses configured on the Principal (Public) network cards of each server to allow the passive server to send a ping. If you don't already have Management IP addresses configured on your servers, follow the procedure below to configure them. Management IP addresses are additional IP addresses assigned to the network card connected to the Principal (Public) network. They are used to allow the passive server to communicate, because unlike the Principal (Public) IP address, they are not filtered.
This allows the passive server to send pings, and is also required to allow the passive server to send email alerts.
To configure a Management IP address:
Open the network properties for the Principal (Public) network connection.
Double-click TCP/IP to display the properties.
Click Advanced .
Enter an additional (currently unused) IP address in the table.
Reposition the IP addresses in the list so that the additional (Management) IP address appears first, and the Principal (Public) network address (by which clients connect to the server) appears second.
Click OK on all three dialogs to accept the configuration changes to the network connection.
The active server must respond within the time period value specified in the
to prevent a failover
from occurring. If the active server responds in a timely manner, the failover process ceases. If the active server does
not respond, the failover proceeds.
How to View the Network Status Using the vCenter Server Heartbeat Console
Launch the vCenter Server Heartbeat Console, and then select the Network tab to display the Network Monitoring page. This page indicates the Principal (Public) network connection. The Principal (Public) Network Connection status is determined by pinging a selection of hosts on the network. If there is no response, and active server connections have been compromised, then a switchover can be initiated to the other server.
You can configure vCenter Server Heartbeat 's behavior by clicking the Configure Pings button and changing the settings in the Network Monitoring: Ping Configuration dialog. This dialog allows you to select the Ping interval and Ping echo timeout .
Click OK to save the changes.
Additionally, you can configure vCenter Server Heartbeat to auto-switchover in the event of lost pings. To configure auto-switchover, click on the Configure Auto-switchover button and select the number of missed pings to initiate an auto-switchover. Click OK to accept the settings.
VMware vCenter Server Heartbeat 6.3 and later