Knowledge Base
Configuring Network Monitoring and Viewing the Network Status
Purpose
This article provides information about configuring network monitoring using the Server Configuration wizard and viewing network status in the VMware vCenter Server Heartbeat Console.
Resolution
Network Monitoring
To monitor a network:
- Click Start > Programs > VMware > VMware vCenter Server Heartbeat Console > Configure Server.
- Click the Network Monitoring tab. On the screen, you see that there are two options, the Public Network Connection pane and the Split-Brain Avoidance pane.
Public Network Connection
The connection between the active server and the principal (public) network can be monitored. VMware recommends that you enable this option, which allows the set of addresses to be chosen automatically. This is not enabled by default.
Split-Brain Avoidance
This setting can be used in WAN installations to ensure that only one server becomes active if the VMware vCenter Server Heartbeat Channel connection is lost with both servers still connected to the principal (public) network.
This operates by pinging from the passive server to the active server across the principal (public) network. If the active server responds, the passive server does not failover, even if the VMware vCenter Server Heartbeat Channel connection is lost. This requires the active and passive servers to have different IP addresses on the principal (public) network, which is typically the case for WAN installations.
To enable this test, you need to enter the principal (public) IP address used by each server.
You also need to configure auxiliary IP addresses on your principal (public) network cards. This is required to allow the passive server to send a ping. When you have made your changes, click Finish to apply them and close the wizard. Clicking Reset reverts the settings to the last applied values. Both servers can be independently configured by running the wizard and following these instructions.
Auxiliary IP Addresses
These are additional IP addresses assigned to the network cards connected to the principal (public) network. They are used to allow the passive server to communicate on the principal (public) network, because, unlike the principal (public) network IP address, they are not filtered.
The auxiliary IP address is used by the passive server to send pings, and is required by the passive server to send email alerts.
To configure an Auxiliary IP address:
-
Open the network properties for the principal (public) network connection,open the TCP/IP properties, and click Advanced.
-
Enter an additional (currently unused) IP address in the table. Reposition the IP addresses in the list so that the additional address appears first, and the principal (public) network address, by which clients connect to the server, appears second. You can reposition the IP addresses by removing the top one and adding it again at the bottom.
Viewing the Network Status Using the VMware vCenter Server Heartbeat Console
Launch the VMware vCenter Server Heartbeat Console, and click Advanced > Communication > Status to bring up the Communication Status screen. This screen indicates the principal (public) network connection and the split-brain prevention check, if these have been enabled. The 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 is initiated to the other server.
You can configure VMware vCenter Server Heartbeat’s behavior by clicking the Configuration tab and changing the settings in Public Network Connection Check.
Remember to click Apply to save the changes. Alternatively,you can use Reset to revert to the last saved settings.
Additional Information
vCSHB-Ref-838
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
