6.4

VMware, Inc. 37
4
This chapter includes the following topics:
 “Communication Status” on page 37
 “Reviewing the VMware Channel Status” on page 37
 “Configuring Public Network Connection Checks” on page 37
 “Setting Max Server Time Difference” on page 38
Communication Status
Use the Data: Traffic/Queues page to check the status of the VMware Channel, the active server’s send, and
passive server’s receive queues.
Reviewing the VMware Channel Status
The Data: Traffic/Queues page displays the VMware Channel status as connected (Green solid icon) or not
connected (red broken icon), the statistics of the connection with regards to the data sent by either server, and
the size and age of the oldest entry in the active server’s send queue and passive server’s receive queue. The
Channel Connection tab in the lower pane displays the IP addresses used by the VMware Channel for the
Primary to Secondary connections and the port that the communications are using.
Configuring Public Network Connection Checks
The Network Monitoring page allows you to view the status of the network and make adjustments to the IP
addresses used to ping multiple servers within the network.
The Principal (Public) network monitoring feature, previously discussed, 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 server’s Principal (Public) connection to ensure connectivity with the
Principal (Public) network is operational. By default, the IP addresses of the default gateway, the primary DNS
server, and the Global Catalog server are all selected. When one or more of the automatically discovered
waypoints are co-located on a physical machine (leading to duplication of IP addresses), the ability to specify
additional waypoints manually becomes an advantage. To specify a manual target for Principal (Public)
network checking, click Configure Pings to invoke the Ping Configuration dialog. Select the Ping Routing
tab to add to or modify the existing target IP addresses for each server to ping.
In a WAN environment, the target addresses for Principal (Public) network monitoring on the Secondary
server may be different to those automatically selected on the Primary server. Again, the ability to override
automatically discovered selections is provided by manually specifying the target address.
Principal (Public) Network Monitoring is carried out by the active server effectively pinging the target
addresses at regular time intervals. The time interval is set by default to every 10 seconds but the frequency
may be increased or decreased as required.
Network Protection
4