User Guide

3-7
Cisco AlarmTracker Client User Guide
OL-1501-01
Chapter 3 Getting Started
Connecting to an LGMapper Server
This dialog shows you information about each server currently connected. For
each server, it displays some information about the health and status of the
server's operation.
The first two items below the Name indicate the status of the server's connection
to the Listener server. The Listener Messages Processed field indicates the total
number of messages processed since the server started. If you re-display this
dialog every now and then, this number should increase.
The Seconds Since Last Listener Message is perhaps more important. Since
Listener sends out heartbeat messages every 5 seconds, even if there is no input
from customer sites, this field should never display a number greater than 5. If so,
it indicates a potential problem with the Listener connection.
The third field shows the number of Active Connections to this server. This is a
count of the number of active AlarmTracker Client sessions running against the
LGMapper server. This field is a good indicator of the load on the server.
Disconnect allows you to sever your connection to the indicated LGMapper
server. If you disconnect your active connection and you have a standby server,
AlarmTracker Client will automatically create an active connection to the standby
server.
Dealing With Server Failures
AlarmTracker Client has the ability to connect to two LGMapper Servers although
only one Server is active at any one time. As you will see in the description of the
StatusBar in Chapter 6, “StatusBar” and, as in Figure 3-4, you can see two icons
which indicate the status of the Servers you connected to.
The AlarmTracker Client and LGMapper are intended to operate in a
fault-tolerant way. Because you have the opportunity to connect to two LGMapper
Servers, the software attempts to minimize the down time in the event of a Server
failure or network interruption. Table 3-1 describes how the AlarmTracker Client
deals with Server failures or network failures.