Guest

Cisco Remote Monitoring Suite Option

LGCnfg Tool (Release 4.6)

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

LGCnfg Tool

Overview

Starting LGCnfg

Opening a Database

Using Server-Side Filters

Customer Instance Filters

Setting Customer Instance Filters

Clearing Customer Instance Filters

Product Filters

Setting Product Filters in the OID Nodes Tree View

Clearing Product Filters in the OID Nodes Tree View

Setting Product Filters in the Objects View

Clearing Product Filters in the Objects View

OID Node Filters

Setting OID Node Filters

Clearing OID Node Filters

Class Filters

Setting Class Filters

Clearing Class Filters

Message ID Filters

Setting Message ID Filters

Clearing Message ID Filters

Instance Node Deletion

Deleting an Instance Node

Creating a New Database

Cloning a Database

Modifying the OID Node Hierarchy and Rules


LGCnfg Tool

Overview

The LGCnfg tool is used to manage the Alarms Databases at your site and provides the following capabilities:

•Manage server-side Filters

•Delete Instance Nodes

•Create new Configuration Databases

•Edit existing Configuration Databases

•Create and edit OID Nodes and Attributes

•Create and edit Rules for mapping Listener Objects

This section provides a brief overview of the capabilities of the LGCnfg tool.

Starting LGCnfg

To start the LGCnfg tool:

•Select Start>Programs>LGMapper2>LGCnfg.

- or -

•Run LGCnfg2.exe from the bin folder under the installation folder.

Opening a Database

When the LGCnfg starts, it initially has no open Alarms Database.

To open a database, use the File > Open... menu option (Figure 7-1).

Figure 7-1 LGCnfg Tool - Opening an Alarms Database

Initially, the server is set to the local host (i.e., Kevinm-W2K1) as shown in Figure 7-2.

Figure 7-2 Open Database Dialog Box

The Open Database dialog box (Figure 7-2) indicates if there is an Alarms Database configured for the LGMapper Server and the LGArchiver Server. If none is specified, the option is grayed out.

The Server status is shown to the right of the database name. The status is important because if the LGMapper Server is enabled, the database is opened as read only (Figure 7-3). If the LGArchiver Server is running, its database is opened as read only.

Figure 7-3 Database Opens as Read Only

In order to make changes to a LGMapper database, the LGMapper Server must be disabled. Similarly, the LGArchiver Server must not be running if you want to make changes to the LGArchiver database.

You can alternatively select a database that is not attached to either the LGMapper Server or the LGArchiver Server. Attach to a database on a different server by either selecting a database from a known SQL Server machine from the Server drop down list (or by clicking Other...) and selecting a different server name (refer to Figure 7-2). When the selection is made, the dialog attempts to refresh contents of the LGMapper and LGArchiver databases for the new server.

Figure 7-4 shows a sample of the Intelligent Contact Manager (ICM) OID Node hierarchy for an open database:

Figure 7-4 LGCnfg Showing the ICM OID Hierarchy

Using Server-Side Filters

The LGMapper Server and the LGArchiver Server support the filtering of Listener data in order to present a subset of information to the attached AlarmTracker clients. The filters are actually applied to the data before it is updated in the Alarms database so that filtered data is not logged at all.

The following types of server-side filters can be applied using the LGCnfg tool:

•Customer Instance filters

–Filters out specific customer instances. This type of filter is useful for a support center that is responsible for a subset of the customer base tracked by the Listener.

For example, an international company has two customer contact centers, one in San Jose and one in Brussels.

Assume the customer contact center in San Jose is responsible for monitoring only US-based customers. In this case, the LGCnfg tool can be used to filter out all non-US customers from the set of instance nodes.

If the customer contact center in Brussels is responsible for only European-based customers, the LGCnfg tool can be used to filter out all non-European customers.

•Product filters

–Filters out specific products. This type of filter is used to segment support groups for different product support.

For example, one set of LGMapper Servers is dedicated to support for the ICM product, and another set for the ISN product, etc.

•OID Node filters

–Filters out specific OID Nodes (and implicitly their children).

For example, a Network Applications Manager (NAM) customer has two customer contact centers. The first customer contact center supports NICM instances. The second customer contact center supports individual customers. The OID Node filter is configured on the first LGMapper Server to filter out specific kinds of OID Nodes (in this case, NICs).

•Class filters

–Filter out specific Classes for a given product.

•Message ID filters

–Filters out specific EMS Message IDs for a given product.

These filters are set in the different views that display nodes and objects. Objects filtered out are marked with a red 'X' in the check box associated with the object.

Caution When an object filter is set, the LGCnfg tool also deletes all Alarm objects related to the filter setting. This is one reason why the database cannot be attached to a running instance of LGMapper or LGArchiver. Be very sure of your selection before you set any filter. A dialog box is always displayed to confirm any filter setting.

Customer Instance Filters

Setting Customer Instance Filters

Set and clear Customer Instance filters in the Instance Nodes Tree view.

Step 1 Select the customer you want to filter.

Step 2 Select Edit > Filter Out (or right-click and select Filter Out).

The filter setting takes effect the next time the LGMapper or LGArchiver server is started.

Clearing Customer Instance Filters

Step 1 Select the customer you want to clear.

Step 2 Select Edit > Filter Out (or right-click and select Filter Out).

This toggles the filter setting and resets the filter.

Product Filters

Set and clear Product filters in either the OID Nodes Tree View or the Objects View.

Setting Product Filters in the OID Nodes Tree View

Step 1 Select the Product to filter.

Step 2 Select Edit > Filter Out (or right-click and select Filter Out).

The Product filter setting takes effect the next time the LGMapper or LGArchiver server is started.

Clearing Product Filters in the OID Nodes Tree View

Step 1 Select the Product to clear

Step 2 Select Edit > Filter Out (or right-click and select Filter Out).

This toggles the filter setting and resets the filter.

Setting Product Filters in the Objects View

Step 1 Select any entry containing the product you want to filter.

Step 2 Select Edit->Filter Product Out (or right-click and select Filter Product Out).

Clearing Product Filters in the Objects View

Step 1 Select any entry containing the Product to clear.

Step 2 Select Edit > Filter Product Out (or right-click and select Filter Product Out).

This toggles the filter setting and resets the filter.

Note When you filter out a Product, the Product node in the OID Nodes Tree View is marked with a red "X". All objects in the Objects View for that product are also marked with a red "X". In addition, all Instance Nodes for that product are similarly marked.

OID Node Filters

Setting OID Node Filters

Set and clear OID Node filters in the OID Nodes Tree View.

Step 1 Select the OID Node to filter.

Step 2 Select Edit > Filter Out (or right-click and select Filter Out).

The setting takes effect the next time the LGMapper or LGArchiver server is started.

Clearing OID Node Filters

Step 1 Select the node to clear.

Step 2 Select Edit->Filter Out (or right-click and select Filter Out).

This toggles the filter setting and resets the filter.

Note When you filter out an OID Node, the node and all of its children are marked with a red 'X'. In addition, all Instance Nodes that refer to that OID and its children are similarly marked.

Class Filters

Set and clear Class filters in the Objects View.

Setting Class Filters

Step 1 Select any entry containing the Class to filter.

Step 2 Select Edit > Filter Class Out (or right-click and select Filter Class Out).

Clearing Class Filters

Step 1 Select any entry containing the Class to clear.

Step 2 Select Edit > Filter Class Out (or right-click and select Filter Class Out).

This toggles the filter setting and resets the filter.

Note When you filter out a Class, all Message IDs associated with that Class are marked with a red "X".

Message ID Filters

Set and clear Message ID filters in the Objects View.

Setting Message ID Filters

Step 1 Select any entry containing the Message ID to filter.

Step 2 Select Edit > Filter MsgID Out (or right-click and select Filter MsgID Out).

Clearing Message ID Filters

Step 1 Select any entry containing the Message ID to clear.

Step 2 Select Edit > Filter Msg ID Out (or right-click and select Filter Msg ID Out).

This toggles the filter setting and resets the filter.

Caution Exercise extreme care when filtering on Message IDs. Make sure you filter both the raise and clear messages, or you could end up in a situation where some Alarms are not being cleared, or some Alarms are not seen as raised.

Instance Node Deletion

It may be necessary to delete instance nodes. One possible scenario is when you no longer need to monitor a customer. Another scenario is when certain sub-system instances (such as a PG or a NIC) are no longer valid. For these situations and others, delete the instance nodes and their children from the Alarms Database using the LGCnfg tool.

Note As when filtering, if you delete an Instance Node, all associated Alarm objects for that Instance Node are also deleted.

Deleting an Instance Node

Step 1 Select the node to delete in the Instance Nodes Tree View.

Step 2 Select Edit > Delete (or the Delete context menu option, or press the Delete key).

Creating a New Database

To create a new, completely empty (no OID Nodes or Rules) database:

Step 1 Select File > New...

Step 2 When prompted provide the Server location and Database Name.

This database can now be used to create new product instances and rules.

Cloning a Database

To clone the currently open database:

Step 1 Select File > Clone Database...

Step 2 When prompted, select the Server location and new Database Name.

Step 3 Select the aspects of the database you want to copy (see Figure 7-5).

Figure 7-5 Clone Database Options

The Copy Options are as follows:

•Include OID Nodes, Rules and Objects

–Copy all OID Nodes, Rules and objects to the new database.

•Include Customer Instances

–Copy all customer instances to the new database.

•Include Instance Nodes

–Copy all Instance Nodes to the new database.

•Include Alarms

–Copy all Alarms objects to the new database

Any relevant filter settings are always copied.

The cloned database can now be used to create or edit any aspect of a database. Cloning a database is a good way to experiment and test out any important changes in a controlled environment before putting it into a production mode.

Modifying the OID Node Hierarchy and Rules

The Alarms databases created during the installation process contain the proper OID Node hierarchy and Rule set for use by the LGMapper and its clients. If changes need to be made to the OID hierarchy or the Rule definitions, contact the Cisco Technical Assistance Center (TAC) for assistance. Proper Rules definition requires detailed knowledge of Listener message field contents. If you feel the Instance Nodes are improperly defined, or that objects are mapped to the wrong nodes (or not mapped at all), please contact the Cisco Technical Assistance Center (TAC).