Guest

Cisco Remote Monitoring Suite Option

LGMapperCnfg and LGArchiverCnfg Tools (Release 4.6)

  • Viewing Options

  • PDF (207.2 KB)
  • Feedback
LGMapperCnfg and LGArchiverCnfg Tools

Table Of Contents

LGMapperCnfg and LGArchiverCnfg Tools

LGMapperCnfg Tool

Overview

Clients Tab

Displaying Current Users

Disabling/Enabling the LGMapper Server

Alarms Database Tab

Listener Tab

Log Files Tab

LGArchiverCnfg Tool

Overview

Archiver Database Tab

Listener Tab

Log Files Tab


LGMapperCnfg and LGArchiverCnfg Tools


LGMapperCnfg Tool

Overview

The LGMapperCnfg tool provides the capability for you to:

Enable/disable the LGMapper Server

Display the names of the currently connected client(s)

Display and edit the configuration options related to the Alarms database

Specify the location of the Listener to connect to

Select log file options

Start the LGMapperCnfg tool using:

Start>Programs>LGMapper2>LGMapperCnfg

the LGMapperCnfg.exe executable found in the bin folder under the installation folder.

Since the application is a property-page based GUI application, you can navigate through the tabs to both view the options and change them.

Clients Tab

The Clients tab (Figure 4-1) shows the current list of connected users and those with active connections to the LGMapper. It also provides a mechanism to enable/disable the LGMapper Server for maintenance.

Displaying Current Users

The Clients tab (Figure 4-1) contains two list boxes. The Connected list box indicates the user names of the connected users. The Active Connections list box contains the user names of the active users. Be aware that not every connection is an active connection. This is because the LGMapper is duplexed and users may connect to both LGMapper Servers. One of the connections is active (the LGMapper sends Listener messages to the client), while the other connection is a standby (or backup) connection used in the event the active connection is lost. Thus, the number of connections is always greater than or equal to the number of active connections. This display is not dynamic, so to refresh this list, click Refresh.

Figure 4-1 LGMapper Configuration - Clients Tab

Disabling/Enabling the LGMapper Server

Disable the LGMapper Server if:

the machine itself is going down for maintenance

the Listener is going down for maintenance

to perform maintenance on the Alarms database

Use the Disable Server/Enable Server button (Figure 4-2) to disable the LGMapper Server. The button label changes based upon the current state of the LGMapper. If the LGMapper Server is enabled, the text reads Disable Server. If the LGMapper Server is disabled, the text reads Enable Server.

Figure 4-2 Clients Tab - Disable Server

Clicking Disable Server pops up the confirmation dialog box as seen in Figure 4-3.

Figure 4-3 Disable Server Confirmation Dialog Box

Enter a reason for disabling the LGMapper Server (if desired) and click OK. The Server attempts a graceful shutdown and notifies all connected clients that it is disabled and will no longer accept new connections from Clients. The Clients see a message box telling them the LGMapper is disabled and the Reason text. Since the Reason information is stored in the Registry, Clients only see this text if the LGMapper Server machine is actually up and reachable. If it is not, the Client sees a network or RPC related error message.

When the LGMapper Server is disabled, you see the text you entered in the Reason edit box (Figure 4-4).

Figure 4-4 Clients Tab - Reason

To re-enable the LGMapper Server, click Enable Server (Figure 4-5). This provides connecting Clients immediate access to the LGMapper Server.

Figure 4-5 Clients Tab - Enable Server

Alarms Database Tab

The Alarms Database tab (Figure 4-6) provides information about the Alarms database maintained by the LGMapper. This database maintains configuration and Alarm object information while the LGMapper Server is running.

Figure 4-6 LGMapper Configuration - Alarms Database Tab

On this tab you can observe/modify the:

Database Catalog Name

the name of the SQL Server database used

Alarms Objects History

the number of hours of cached Alarm object history you want the LGMapper to maintain

this value controls how long closed Alarm objects (records in the database) are retained in the Alarms Database before being purged.


Note A higher number means more history is maintained, but it also means that more disk space is required to store the information. The LGMapper Server occasionally purges the Alarms database of any closed Alarm object whose closed time falls outside the time history window. Open Alarm objects are never purged.


Maximum Event Count per Alarm

limits the total number of events associated with an Alarm by implementing a form of event suppression, or filtering, to prevent the Alarms database from growing unbounded

This type of suppression is useful for an Alarm that has been excluded for a long time. Such an Alarm could see the object going up and down a large number of times, especially for an object that has been excluded for months. This suppression is accomplished by deleting the oldest events first.


Note The first event (the event resulting in the creation of the Alarm object) is never deleted until after the alarm is closed.


Maximum Event Repeat Count

use to implement a form of event suppression, or filtering, to prevent the Alarms database from growing unbounded by limiting the number of repeat events for an Alarm

Some Alarms result in an event being phoned home every 5 minutes or so (up to a maximum of 5 phone homes per hour), indicating the Alarm is still down, and results in a large number of events being associated with the Alarm. There is little additional information contained in these repeat events.

Listener Tab

The Listener tab allows you to specify the location of the Listener machine the LGMapper is connected to.


Note The installation procedure does not fill in any values on this tab. You must enter the correct information shown on this page in order for the LGMapper to properly connect to a Listener.


On this tab you can observe/modify the following five (5) fields:

Listener Host

the Listener machine name

User Name

a valid user name on that machine

Domain_Name/User_Name required if the LGMapper Server and Listener machines are in different domains

Password

the password for user specified by the User Name

Time Zone Offset

the time zone difference between the location of the Listener machine and the LGMapper machine (in hours)

i.e., The Listener machine is in San Jose, CA and the LGMapper Server machine is in Lowell, MA, Since Lowell is three (3) hours ahead of San Jose, you would enter a 3 in this field. This is because both Listener and LGMapper store times in their local time zone.

Use Compression

If this option is checked, the Listener sends data to the LGMapper in compressed form.

This option should only be used when both the network connection between the Listener and LGMapper is very slow, and there are a large number of customers monitored (over 75).

Normally, you should leave this option unchecked since compressing and decompressing data is a CPU-intensive process.

Log Files Tab

The Log Files tab (Figure 4-7) allows you to select the log files to be generated by the LGMapper Server.

Figure 4-7 LGMapper Configuration - Log Files Tab

This tab includes the following fields:

Location

indicates the path to the folder containing the log files (this should be the log folder under the installation folder for the LGMapper).

LGMapper Log File

select to create a log file containing LGMapper information named LGMapperddmmyy_nn.log, where ddmmyy is the current date, and nn is a unique number for the file


Note These log files are simple ASCII files and contain information about initialization, connecting Clients, and any errors that occur. Cisco strongly suggests you use this log file since this is the only way you can report problems about the LGMapper to Cisco customer support. These LGMapper Log files are not purged, so periodically delete them.


Configuration Database Transactions Log File

select to create a log file named LGMDBTrans.log containing information about additions made to the Configuration database InstanceNodes table when LGMapper is running


Note This log file is less important than the LGMapper Log and the Listener Messages Log files. However, when in a "steady state" situation, turn this file on to see if any new Instance nodes are being added to the database. When selected, data is appended to this log file each time the LGMapper Server starts up.


Listener Messages Log File

select to create an ASCII log of all Listener messages received named LGMapperV5.log (or LGMapperV4.log if you are connecting with a Version 4 feed from Listener)


Note See "Backwards Compatibility Considerations" for information about the differences between a Version 4 and Version 5 Listener feed.


overwritten each time you start the LGMapper

useful if you find a logic error in the Client displays and want Cisco customer support to investigate


Note This file can be used to "play back" the full set of events to the Client displays in order to recreate the sequence of events seen in real time. If you see a problem, copy this file to another file, save it (remember, the next time LGMapper is restarted, the log file will be overwritten), and notify Cisco customer support.


LGArchiverCnfg Tool

Overview

The LGArchiverCnfg tool provides the capability for you to:

Display and edit the configuration options related to the Archiver database

Specify the location of the Listener to connect to

Select log file options

Start the LGArchiverCnfg tool using:

Start>Programs>LGMapper2>LGArchiverCnfg

the LGArchiverCnfg.exe executable found in the bin folder under the installation folder.

Since the application is a property-page based GUI application, you can navigate through the tabs to both view the options and change them.


Note To start and stop archiving, use the LGArchiverNM Windows Service (refer to "LGMapperNM and LGArchiverNM").


Archiver Database Tab

The Archiver Database property tab (Figure 4-8) provides information about the Alarms database maintained by LGArchiver. This database maintains configuration and Alarm object information while LGArchiver is running.

Figure 4-8 LGArchiver Configuration - Archiver Database Tab

You can observe and/or modify four (4) fields on this tab:

Database Catalog Name

the name of the SQL Server database

Alarms Objects History

the number of days of cached Alarm object history you want the LGArchiver to maintain

controls how long closed Alarm objects (records in the database) are retained in the database before being purged


Note A higher number means more history is maintained, however, more disk space is required to store the information. During LGArchiver operation, occasionally purges the Alarms database of any closed Alarm objects whose closed time fall outside the time history window. Alarm objects still open are never purged.


Maximum Event Count per Alarm

used to implement a form of event suppression or filtering to prevent the Alarms database from growing unbounded

this value limits the total number of events associated with an Alarm

This type of suppression is useful for an Alarm that has been excluded for a long time. Such an Alarm could see the object going up and down a large number of times, especially for an object that has been excluded for months. The suppression is accomplished by deleting the oldest events first.


Note The first event (the event resulting in the creation of the Alarm object) is never deleted.


Maximum Event Repeat Count

used to implement a form of event suppression, or filtering, limiting the number of repeat events for an Alarm and preventing the Alarms database from growing unbounded.

Some Alarms result in an event being phoned home every 5 minutes or so (up to a maximum of 5 phone homes per hour), indicating the Alarm is still down. This could result in a large number of events associated with the Alarm. There is little additional information contained in these repeat Events.

Listener Tab

The Listener tab (Figure 4-9) allows you to specify the location of the Listener machine the LGMapper connects to.

Figure 4-9 LGArchiver Configuration - Listener Tab

This tab allows you to observe/modify the following fields:

Listener Host

the Listener machine name

User Name

a valid user name on that machine

Domain_Name/User_Name required if the LGArchiver Server and Listener machines are in different domains

Password

the password for user specified by the User Name

Time Zone Offset

the time zone difference between the location of the Listener machine and the LGMapper machine (in hours)

i.e., The Listener machine is in San Jose, CA and the LGMapper Server machine is in Lowell, MA, Since Lowell is three (3) hours ahead of San Jose, you would enter a 3 in this field. This is because both Listener and LGMapper store times in their local time zone.

Log Files Tab

The Log Files tab (Figure 4-10) allows you to select the log files to be generated by the LGArchiver Server.

Figure 4-10 LGArchiver Configuration - Log Files Tab

This tab includes the following fields:

Location

indicates the path to the folder containing the log files (this should be the log folder under the installation folder for the LGArchiver).

LGArchiver Log File

select to create a log file containing LGMapper information named LGArchiverddmmmyy_nn.log, where ddmmyy is the current date, and nn is a unique number for the file


Note These log files are simple ASCII files and contain information about initialization, connecting Clients, and any errors that occur. Cisco strongly suggests you use this log file since this is the only way you can report problems about the LGMapper to Cisco customer support. These LGArchiver Log files are not purged, so periodically delete them.


Configuration Database Transactions Log File

select to create a log file named LGADBTrans.log containing information about additions made to the Configuration database InstanceNodes table when LGArchiver is running


Note This log file is less important than the LGArchiver Log and the Listener Messages Log files. However, when in a "steady state" situation, turn this file on to see if any new Instance nodes are being added to the database. When selected, data is appended to this log file each time the LGArchiver Server starts up.


Listener Messages Log File

select to create a log of all Listener messages received named LGArchiverV5.log (or LGArchiverV4.log if you are connecting with a Version 4 feed from Listener)


Note See "Backwards Compatibility Considerations" for information about the differences between a Version 4 and Version 5 Listener feed.


overwritten each time you start the LGArchiver

useful if you find a logic error in the Client displays and want Cisco customer support to investigate

This file is used to "play back" the full set of events to the Client displays in order to recreate the sequence of events seen in real time. If you see a problem, copy this file to another file, save it (remember, the next time LGArchiver is restarted, the log file will be overwritten), and notify Cisco customer support.