Modulo Resultados

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.

Chapter 4 LGMapperCnfg and LGArchiverCnfg Tools

LGArchiverCnfg Tool

Figure 4-8 LGArchiver Configuration - Archiver Database Tab

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

Chapter 4 LGMapperCnfg and LGArchiverCnfg Tools LGArchiverCnfg Tool

• 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.

Chapter 4 LGMapperCnfg and LGArchiverCnfg Tools

LGArchiverCnfg Tool

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.

Chapter 4 LGMapperCnfg and LGArchiverCnfg Tools LGArchiverCnfg Tool

Figure 4-10 LGArchiver Configuration - Log Files Tab

This tab includes the following fields: • Location

– the path to the folder containing the log files (he 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 Release 4 feed from Listener)

Chapter 4 LGMapperCnfg and LGArchiverCnfg Tools

LGArchiverCnfg Tool

Note See Chapter 11, “Backwards Compatibility Considerations” for information about the differences between a Release 4 and Release 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.

Chapter 4 LGMapperCnfg and LGArchiverCnfg Tools LGArchiverCnfg Tool

C H A P T E R

5

LGMapperNM and LGArchiverNM