ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 84 of 381
Nodes should have the same GMT so that availability data can be correlated. ASAP
maintains all times internally in GMT and then converts them to the local civil time of
the Collect server. This lets you view system performance in the system’s own local
time and ignore time zone differences when correlating statistics.
ASAP’s clock synchronization algorithm makes instantaneous time changes if the time
difference between the central Collect node and the Remote node is greater than two
minutes, and uses slow synchronization only if the time difference between the Central
node and the Remote node is less than two minutes. To avoid sudden time changes
on the Remote nodes, set the ASAP SET Command option SET SYNCSLOW ON |
OFF to ON to slowly synchronize the time of day between selected nodes.
You can set synchronization between nodes to occur automatically with the SET
SYNC min, freq option. This option periodically resynchronizes its node’s GMT to the
Collection node’s GMT.
Monitoring Different Sets of Network Nodes
You can configure multiple sets of ASAP Monitor and ASAP Collector processes to
operate autonomously with different designated collection locations and options. This
lets geographically separate operation groups monitor selectively different sets of
network nodes.
The following figure shows an example of such a configuration. Examples A and B
illustrate two possible ASAP process configurations.
Figure 3-1. Monitoring Different Sets of Network Nodes
\San Fran
\Chicago\Seattle
\LA
\Dallas
\Atlanta
\New York
\Tampa
A
B
VST001.vsd