Table of Contents

Introduction

Starting the Configuration Tool
The Configuration Manager

Conversions

Changing a Conversion
Adding a Conversion
Deleting a Conversion

Visuals

Column Visuals Window
Changing a Visual
Adding a Visual
Deleting a Visual

Classes

Classes Window
Changing a Class
Adding a Class
Deleting a Class
Class Defined for Cisco Info Center

Menus

Menus Window
Add a Menu
Change a Menu
Delete a Menu
Add a Menu Option to a Menu
Change Menu Options in a Menu
Delete a Menu Option From a Menu
Setting the Order of Menu Options
Create Commands

Commands with Elements
Commands with Parameters

Cisco Info Center Menus - Menu Options Table
Cisco Info Center Tools Description

Cisco WAN Manager Equipment Manager
Administration GUI
Get Configuration
Real Time Counters
Test Delay
Test Connection
Add Loopback
Delete Loopback
Decode BitMap
Create Event List
Cisco Info Admin Desktop Information
HP OpenView Network Node Manager
Cisco WAN Manager Desktop

Using Automation to Run Tools

An Example of Using Automation to Run Remote Tools

Resolutions

The Resolutions Window
Add a Resolution
Change a Resolution
Delete a Resolution

Cisco Info Server Properties

Modifying Cisco Info Server Properties
Property Controls

AllowConnections
AllowISQL
AuditAutomation
AuditConfig
AuditNames
AutoTick
DeackOnReawaken
DebugActions
DebugLevel
DebugTriggers
Granularity
LogInterval
MonitorConnections
ReawakenClosed
UpdateAlertKey
UpdateSummary

Configuration

This chapter describes the utility available to administer tool configuration, appearance, menus, and classes within the Cisco Info Center system.

This chapter includes the following sections:

• Introduction

• Conversions

• Visuals

• Classes

Table 4-2 lists all of the Classes defined for the Objective View. This provides the administrator with an easy way of dragging and dropping the icons from the Symbol Palette. No menus have been defined for the classes below. This table also describes the icons for the Objective View.

• Cisco Info Center Tools Description

• Cisco Info Server Properties

Introduction

Configuration options in Cisco Info Center include the ability to configure the following:

• conversions that take place internally on fields (conversions)

• default visual layout for fields in the Event List (visuals)

• menus and icons associated with particular classes of object (objects)

• menus displayed (menus)

• predominate resolutions for particular classes of problems (resolutions)

You can configure these options from the Configuration Manager.

You can also edit the Cisco Info Server properties; however, this is available only to super users.

Starting the Configuration Tool

To start the Configuration Manager, select the Configuration button from the Conductor button bar.

You can also start configuration from the command line with the following command:

The Configuration Manager

Figure 4-1 shows the Configuration Manager window.

Conversions

When Cisco Info Center displays information, it can translate numeric values into strings for readability. This translation is associated with a named column in the Cisco Info Server status table and is called a conversion.

To display the Conversions window, click on the Conversions button. The Conversions window is displayed, as shown in Figure 4-2.

Changing a Conversion

Select any existing conversion in the list to display the details. You can change the Value and Conversion fields. You cannot change the Column field.

When you click on the arrow buttons next to the Value field, the Value field increments or decrements by one. When the required changes have been made, click on the Update button to update the entry in the displayed list. When you do not click on the Update button, the changes are discarded. When you wish to discard the changes made, click on the Cancel button.

Adding a Conversion

To add a conversion, click on the New button. You can then edit the Column, Value, and Conversion fields. The Column field should be populated with the name of the column in the Cisco Info Server status table.

Deleting a Conversion

To delete a conversion, select the conversion in the list, then click on the Delete button.

Visuals

When information about alerts in the Cisco Info Center system is displayed in the Event List and other tools, the visual appearance has default settings. These default settings are called the column visuals. The system comes with these visuals predominate.

For each field in an alert, you can set the title text, title justification, data justification, and the default and maximum widths for the field.

Column Visuals Window

You click on the Visuals button to display the Column Visuals window, as shown in Figure 4-3.

Changing a Visual

Selecting any column name in the list displays the visual attributes in the fields below the scrolled list. All these fields, except for Column, can be edited. You can change the values at this point. Once the changes are made, click on the Update button to specify the changes into the list. To cancel the changes, click on the Cancel button.

Adding a Visual

To add a visual attribute, click on the New button. The fields below the scrolled list become editable. You should now specify the column name you wish to create visual attributes for in the Column field and adjust the other fields as appropriate. Once the fields are filled in or set, click on the Update button. To cancel the addition, click on the Cancel button.

Deleting a Visual

To delete a visual, select the column name from the scrolling list, then click on the Delete button.

Classes

Alerts in Cisco Info Center can be tagged with a class value, which is assigned at the Cisco Info Mediator level. Class values are used as a way of categorizing the alerts.

Class values allow the alert to inherit information about the type of alert it is and how it should be presented. Each class has a name, an associated menu and an icon. The menu is used whenever a GUI tool wishes to display tools associated with the object class. The icon is used in the Objective View when an unplaced alert arrives to characterize the alert.

Classes Window

To modify the classes, click on the Classes button. The Classes window is displayed, as shown in Figure 4-4.

Changing a Class

Selecting any existing class in the list displays the details for that class in the lower fields. You can now change the Name, Menu, and icon image. The Identifier field cannot be changed.

When the required changes are made, click on the Update button to update the entry displayed in the list. When you do not click on the Update button, the changes are discarded. When you wish to discard the changes, click on the Cancel button.

Adding a Class

To add a new class, click on the New button. The Identifier, Name, Menu, and icon image are editable. Specify the identifying value for the class in the Identifier field, class name in the Name field, then select an image in the Image Selector. The Menu field should be filled with the name of a menu. Table 4-2 lists all of the Classes defined for the Objective View. This provides the administrator with an easy way of dragging and dropping the icons from the Symbol Palette. No menus have been defined for the classes below. This table also mentions the icons for the Objective View.

Deleting a Class

To delete a class, select the class in the list of classes, then click on the Delete button.

Class Defined for Cisco Info Center

Table 4-1 lists all of the classes for the Cisco Info Center. These classes define the context sensitive tools available in the Event List.

Table 4-2 lists all of the Classes defined for the Objective View. This provides the administrator an easy way of dragging and dropping the icons from the Symbol Palette. No menus are defined for the classes below. This table also lists the icons for the Objective View.

Table 4-2: Objective View Classes

Class Name	Class Number	Menu	Icon
BPX-sm	1130	BPX-oview-menu	SMBPX2.XPM
BPX-md	1131	BPX-oview-menu	SMBPX.XPM
BPX-lg	1132	BPX-oview-menu	BPX.XPM
IGX-sm	1133	IGX-oview-menu	SMIGX2.XPM
IGX-md	1134	IGX-oview-menu	SMIGX.XPM
IGX-lg	1135	IGX-oview-menu	IGX32.xpm
AXIS-sm	1136	AXIS-oview-menu	SMAXIS2.XPM
AXIS-md	1137	AXIS-oview-menu	SMAXIS.XPM
AXIS-lg	1138	AXIS-oview-menu	AXIS.xpm
3800-sm	1139	3800-oview-menu	SM38002.XPM
3800-md	1140	3800-oview-menu	SM3800.XPM
3800-lg	1141	3800-oview-menu	3800.xpm
ESP-sm	1142	3800-oview-menu	SM38002.XPM
ESP-md	1143	3800-oview-menu	SM3810.XPM
ESP-lg	1144	3800-oview-menu	3810.xpm
VNS-sm	1145	ESP-oview-menu	SMESP2.XPM
VNS-md	1146	ESP-oview-menu	SMESP.XPM
VNS-lg	1147	ESP-oview-menu	ESP.xpm
DAS-sm	1148	VNS-oview-menu	SMVNS2.XPM
DAS-md	1149	VNS-oview-menu	SMVNS.XPM
DAS-lg	1150	VNS-oview-menu	VNS.XPM
VNS-md	1149	VNX-oview-menu	SMVNS.XPM
VNS-lg	1150	VNS-oview-menu	VNS.XPM
DAS-sm	1151	DAS-oview-menu	SMDAS2.XPM
DAS-md	1152	DAS-oview-menu	SMDAS.XPM
SV-sm	1153	DAS-oview-menu	DAS.xpm
SV-md	1154	SV-oview-menu	SMSV2.XPM
SV-lg	1155	SV-oview-menu	SMSV.XPM
IPX-md	1156	SV-oview-menu	SV.XPM
IPX-lg	1157	IGX-oview-menu	SMIPX.XPM
FRP-sm	1158	IGX-oview-menu	IPX32.xpm
FRP-md	1159		SMFR2.XPM
FRP-lg	1160		SMFR.XPM
2000-lg	1161		FRPORT.xpm
3000-lg	1162	Router-oview-menu	2000.xpm
4000-lg	1163	Router-oview-menu	3000.xpm
7000-lg	1164	Router-oview-menu	4000.xpm
ATM-sm	1165	Router-oview-menu	7000.xpm
ATM-md	1166	ATMP-oview-menu	SMAP2.XPM
ATM-lg	1167	ATMP-oview-menu	SMAP.XPM
DataP-sm	1168	ATMP-oview-menu	ATMPORT.xpm
DataP-md	1169	DataP-oview-menu	SMDP2.XPM
DataP-lg	1170	DataP-oview-menu	SMDP.XPM
VoiceP-sm	1171	DataP-oview-menu	DATAPORT.xpm
VoiceP-sm	1172	VoiceP-oview-menu	SMVP2.XPM
VoiceP-md	1173	VoiceP-oview-menu	SMVP.XPM
VoiceP-lg	1174	VoiceP-oview-menu	VOICEPORT.xpm

Menus

Cisco Info Center allows you to create and associate menus with particular tools or classes of alerts. For example, you can create:

• the Alerts menu's Tools option, which runs a command on a selected alert in the Event List window

• the Tools menu on any window of displayed alerts

• the Tools menu on the Monitor Box window.

A menu comprises a menu name and a list of menu options. Each of these menu options has a title and a command. The command can include internal Cisco Info Center variables, UNIX environment variables (called elements), and prompts for strings or values (called parameters).

For menus associated with a selected alert, the elements can also include references to the fields in an alert record. This allows you to select an alert and run a program, passing information about the alert to the program.

When a menu option is selected, the command is built using templates. First, the values for the various elements in the template are substituted into the command. A prompt then appears requesting a value for each of the parameters in the template. These parameter values are substituted into the final command. The completed command is then run on the system where the Cisco Info Admin Desktop tools are running. Note, when the command is run, it is passed to /bin/sh. This means the command itself could be a shell script.

Note, when you are using X to display the Cisco Info Center tools remotely from a server, tool commands are run on the server. These tool commands, when they are also to be displayed remotely, must be told to do so using command line options. For example, -display.

Menus Window

To display the Menus window, shown in Figure 4-5, click on the Menus button.

The Menus frame displays the menus that have been created. Table 4-3 shows the default menus available.

Table 4-3: Menus Associated with Cisco Info Center Tools

Menu	Cisco Info Center Tool
ConductorMenu	Tools menu on the Conductor.
DefaultMenu	Alerts menu's Tools menu in the Event List, when you select an alert.
MainEventListMenu	Tools menu on the Monitor Box window of the Event List.
SubEventListMenu	Tools menu on any window of displayed alerts.
ObjViewMenu	Tools menu on the objective view main window.
ObjViewMapMenu	Tools menu on any open objective view map page and the Unplaced Events window.
Class1005-Menu	Context Sensitive Tools Menu for Class 1005.
Class1010-Menu	Context Sensitive Tools Menu for Class 1010.
Class1015-Menu	Context Sensitive Tools Menu for Class 1015.
Class1020-Menu	Context Sensitive Tools Menu for Class 1020.
Class1025-Menu	Context Sensitive Tools Menu for Class 1025.
Class1030-Menu	Context Sensitive Tools Menu for Class 1030.
Class1035-Menu	Context Sensitive Tools Menu for Class 1035.
Class1040-Menu	Context Sensitive Tools Menu for Class 1040.
Class1045-Menu	Context Sensitive Tools Menu for Class 1045.
Class1050-Menu	Context Sensitive Tools Menu for Class 1050.
Class1055-Menu	Context Sensitive Tools Menu for Class 1055.
Class1060-Menu	Context Sensitive Tools Menu for Class 1060.
Class1065-Menu	Context Sensitive Tools Menu for Class 1065.
Class1070-Menu	Context Sensitive Tools Menu for Class 1070.
Class1075-Menu	Context Sensitive Tools Menu for Class 1075.
Class1080-Menu	Context Sensitive Tools Menu for Class 1080.
Class1085-Menu	Context Sensitive Tools Menu for Class 1085.
Class1090-Menu	Context Sensitive Tools Menu for Class 1090.
Class1095-Menu	Context Sensitive Tools Menu for Class 1095.
Class1020-BPX-Menu	Context Sensitive Tools Menu for Class 1100.
Class1065-Menu	Context Sensitive Tools Menu for Class 1105.
BPXEndpointMenu	Context Sensitive Tools Menu for Class 1115.
FREndpointMenu	Context Sensitive Tools Menu for Class 1120.

Add a Menu

To add a new menu:

1. Click on the New button in the Menus frame.

2. Specify the name of the menu in the Name field. This should be a name that has been defined in the Class window. See Section, "Classes" for more information.

3. Adjust the Columns slider.

4. Click on the Update button.

Change a Menu

To alter the settings of a menu, select the menu, then modify the settings. When the modifications are complete, click on the Update button.

Delete a Menu

To delete a menu, select the menu to delete, then click on the Delete button.

Note, deleting a menu deletes the menu and all its associated options.

Add a Menu Option to a Menu

To add an option to the Tools menu, you must select a menu. The Menu Items frame is enabled and displays the menu options. To add the new menu option to the menu:

1. Click on the New button in the Menu Items frame.

2. Specify the name of the menu option in the Title field; this is the name that is displayed when the Tools menu is used.

3. Specify the command this menu option runs, in the Command field. For example, specify a command for starting a local tool, for example, xterm. See Section, "Create Commands", for information about the complete format and content of a command.

4. Select the Redirect Output toggle button. This controls what happens with the output, that is stdout, when a command is run. The output is echoed through a window in the tool that uses the command. When this is not selected, the output is discarded.

5. Select the Redirect Errors toggle button. This controls what happens with the errors, that is stderr, when a command is run. The errors are echoed through the window in the tool that used the command. When this is not selected, the error messages are discarded.

6. Click on the Update button.

7. Click on the Apply button when you have completed all the menu options.

Change Menu Options in a Menu

To alter the menu options in a menu:

1. Select the menu.

2. Select the menu option to be changed.

3. Edit the Title, Command, Redirect Output, and Redirect Errors fields.

4. Click on the Update button. To discard the changes, click on the Cancel button.

Delete a Menu Option From a Menu

To delete a menu option from a menu, select the menu, select the menu option, then click on the Delete button.

Setting the Order of Menu Options

To change the order of menu options, select the menu, select the menu option to be moved, then use the four buttons directly below the list: Top, Up, Down, and Bottom. These buttons move the currently selected menu option to the top of the list, up one in the list, down one in the list, or to the bottom of the list, respectively.

Create Commands

The following sections describe how to use elements and parameters with a command in the Command field.

Commands with Elements

Elements are used for passing information to the command. The types of elements you can insert are:

• Field Values, which pass alert data to the command. Note, when field values are defined and no event is selected when the tool is run from the Alerts menu's Tools option, you are prompted for the field values.

• Internal Variables, which are internal Cisco Info Center variables

• Environment Variables, which are the UNIX environment variables required for Cisco Info Center to run.

To add an element:

1. Move the cursor in the Command field to where the information is to be inserted.

2. Click on the Elements button.

The Elements window is displayed.

1. Select the type of variable you wish to insert from the Type option button.

2. When you have selected a type, scroll down the list and select the variable to insert into the scrolled list. Click on the Apply button. The Elements window remains open, however, the appropriate string is inserted into the command string.

3. Click on the Close button to close the Elements window.

Commands with Parameters

Parameters are used where a command requires information before starting. For example, a Telnet session may require a host name and password. The command in this case would contain two parameters; one for the host name and one for the password.

These parameters are gathered before a tool starts running and the information entered is substituted into the command.

To add a parameter:

1. Move the cursor in the Command field to where you wish the substitution to take place.

2. Click on the Parameters button.

The Parameter Builder window is displayed.

For any one parameter, the system must be provided a name for the prompt, the text to use in the prompt, the type of entry, for example, string or integer, and when required, a default setting for the field.

1. Specify the name of the parameter in the Name field.

2. Specify a prompt in the Prompt field.

3. Select a parameter prompt type: String, Integer, Float, Choice, Lookup, or Password:
When you select either String, Integer, or Float parameters, the only active field is the Default field, which should contain the string which initially appears in the field. The only difference between these three types of parameters is what characters each field accepts. A String parameter accepts any character, Integer accepts the characters 0-9, and Float accepts 0-9 and decimal point (.).

When you select the Choice parameter type, this allows you to create an option button with a fixed set of options. When you select Choice, this enables the scrolling list below the Default entry. Below the list are the list editing buttons, which operate in the same manner as the other list editors in nco_config. There is one additional button, Clear which deletes all the entries in the list.

When you select the Lookup parameter type, this works the same as Choice, except that instead of entering the choices into the scrolled list, the parameter refers to a file on disk. Each line of this file is used as a choice. To select the file, either specify the file name in the Filename field or click on the Browse button, which displays a file selection dialog to select the file. Note, this file must be available on the machine running the Cisco Info Admin Desktop tools.

When you select the Password parameter type, this operates the same as the String type, except that when the command prompt appears, any text entered is obscured.

4. Click on the Apply button.

Cisco Info Center Menus - Menu Options Table

Table 4-4 lists the menu options (tools) for the defined Menus.

Table 4-4: Menu Options

Menu	Menu Options
ConductorMenu	Create Event List
DefaultMenu
MainEventListMenu	Desktop Information Create Event List Ovw
SubEventListMenu	StrataView Desktop
ObjViewMenu
ObjViewMapMenu
Class1005-menu	Administration GUI Get Configuration Equipment Manager
Class1010-Menu	Administration GUI Decode BitMap Equipment Manager
Class1015-Menu	Administration GUI Get Configuration Equipment Manager
Class1020-Menu	Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Del Loopback
Class1025-Menu	Administration GUI Get Configuration Real Time Counters Decode BitMap Equipment Manager
Class1030-Menu	Administration GUI Get Configuration Real Time Counters Decode BitMap Equipment Manager
Class1035-Menu	Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback Decode BitMap Equipment Manager
Class1040-Menu	Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback Equipment Manager
Class1045-Menu	Administration GUI Get Configuration Real Time Counters
Class1050-Menu	Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback
Class1055-Menu	Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback
Class1060-Menu	Administration GUI Get Configuration
Class1065-Menu	Administration GUI Get Configuration
Class1070-Menu	Administration GUI
Class1075-Menu	Administration GUI Get Configuration Decode BitMap
Class1080-Menu	Administration GUI Get Configuration Real Time Counters Equipment Manager
Class1085-Menu	Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback Equipment Manager
Class1090-Menu	Administration GUI Decode BitMap Equipment Manager
Class1095-Menu	Administration GUI Get Configuration Decode BitMap Equipment Manager
Class1020-BPX-Menu	Administration GUI Get Configuration Real Time Counters Test Delay Add Loopback Del Loopback
BPXEndpointMenu	Administration GUI Get Configuration Real Time Counters Test Delay Add Loopback Delete Loopback
FREndpointMenu	Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback
SubEventListMenu	StrataView Plus Desktop

Cisco Info Center Tools Description

This section describes the functionality for each of the menu options in Table 4-4.

Cisco WAN Manager Equipment Manager

This tool displays the Equipment Manager tool that displays the shelf view for the AXIS network elements.

This tool is available only for events reported by the AXIS NEType network elements and runs on the Cisco WAN Manager (formerly known as Cisco StrataView Plus) machine. This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

The variables passed to the Cisco WAN Manager Equipment Manager tool are:

• $DISPLAY

• @NEAddress

Administration GUI

This tool uses the Cisco WAN Manager machine to Telnet to the network element using the IP address in the Event List and displays an Xterm with a Telnet session to the network element.

This tool displays an error message when the network element is not reachable.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

The variables passed to the Administration GUI are:

• $DISPLAY

• @NEAddress

Get Configuration

This tool displays the configuration of the alarmed resource as stored in the Cisco WAN Manager database. The data reported from the Informix OnLine database is dependent upon the value in the ObjectType field. For example, for all card events, (ObjectType = card), the Get Configuration script displays the configuration for the card as stored in the Cisco WAN Manager Informix OnLine database.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

Table 4-5 lists the Informix tables used for the Get Configuration:

Real Time Counters

This tool is useful for diagnosing resources that are in an alarm state. For example, for a port alarm, this tool can launch either an SNMP grapher or an ASCII display that shows the real time counters for frames/cells transmitted and received on that port, to verify that indeed, the port is not passing traffic.

The Real Time Counters tool launches a GUI that allows you to pick a list of the counters you would like to monitor. The list is dynamically created based on the value in the ServiceType field. This selection tool provides you with the option to pick an interval for launching the polls to the network element and the display mechanism, grapher or textual.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

The variables passed to the Real Time Counters tool are:

• $DISPLAY

• @NEName

• @Slot

• @NEType

• @ServiceType

• @ObjectType

• @PSAP

• @LSAP

• @DSAP

• @NEAddress

Test Delay

The Test Delay tool uses the ConnProxy SNMP Agent on the Cisco WAN Manager machine to check the delay for a connection. This tool sends an SNMP request to determine the delay for a connection and displays the time taken for the delay on the Cisco Info Admin Desktop.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

The variables passed to the Test Delay tool are:

• $DISPLAY

• $Proxy - ConProxy Agent

• @NEType

• @Node

• @NEName

• @Slot

• @PSAP

• @LSAP

• @DSAP

• @ObjectType

• @ServiceType

• Delay (Conn|Delay)

Test Connection

The Test Connection tool uses the ConnProxy SNMP agent on the Cisco WAN Manager machine to test the connectivity for a connection. This tools send an SNMP request to determine the status of the connection and displays the result of the test on the Cisco Info Admin Desktop.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

The variables passed to the Test Connection tool are:

• $DISPLAY

• $Proxy - ConProxy Agent

• @NEType

• @Node

• @NEName

• @Slot

• @PSAP

• @LSAP

• @DSAP

• @ObjectType

• @ServiceType

• Delay (Conn|Delay)

Add Loopback

The Add Loopback script provides a mechanism for you to add a soft loopback on the network element port. This tool is very useful in trouble shooting problems with connectivity. This tool prompts you for a user name and password for the Cisco WAN Manager machine, followed by the user name and password for the network element.

The tool performs the loopback addition by logging into the Cisco WAN Manager machine using the user name and password provided above, and then logging into the network element from the Cisco WAN Manager machine and sending the appropriate Add Loopback Command. An Xterm window is displayed on the Cisco Info Admin Desktop machine from where the tool is launched, indicating the progress of this tool.

This tool is run in two parts. The Cisco Info Admin Desktop launches the tool loopback.desktop in the $OMNIHOME/utils/loopback/loopback.desktop script. This script performs an nco_sql insert into the Cisco Info Server, which in turn, executes the loopback.server script.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

Table 4-6 lists the commands used to add a loopback.

Table 4-7 lists the variables passed to the Add Loopback tool.

Delete Loopback

The Delete Loopback script provides a mechanism for you to delete a soft loopback that may have been added on the network element port. This tool is very useful in trouble shooting problems with connectivity. This tool prompts you for a user name and password for the Cisco WAN Manager machine, followed by the user name and password for the network element.

The tool performs the loopback deletion by logging into the Cisco WAN Manager machine using the user name and password provided above, and then logging into the network element from the Cisco WAN Manager machine and sending the appropriate Delete Loopback command. An Xterm window is displayed on the Cisco Info Admin Desktop machine from where the tool is launched, indicating the progress of this tool.

This tool is run in two parts. The Cisco Info Admin Desktop launches the tool loopback.desktop in the $OMNIHOME/utils/loopback/loopback.desktop script. This script performs an nco_sql insert into the Cisco Info Server, which in turn, executes the loopback.server script.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

Table 4-8 lists the commands used to delete a loopback.

Table 4-9 lists the variables passed to the Delete Loopback tool.

Decode BitMap

This tool provides you with the ability to decode the bitmap that is sent as an SNMP VarBind from the network element and received by the Cisco Info Mediators. The value stored in the BitMap field is dependent upon the trap. For example, for some traps, the BitMap field contains values indicating the status of the trap, while for other traps, it contains the starting DS0 port.

The tool converts the value stored in the BitMap by using the contents of the Convert field which stores a pointer to an external lookup file. Upon conversion, this tool displays the converted values with the set bit positions on the Cisco Info Admin Desktop screen.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco Info Server machine and to display to the Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

The variables passed to the Decode BitMap Tool are:

• $DISPLAY

• @BitMapField

• @Convert

Create Event List

The Create Event List tool, available from the Tools and Main Event List Tools menus, provides a quick way of creating filtered Event Lists based on any single fields in the Cisco Info Server, by prompting for the Field Name.

For example, to create a filtered Event List with monitor boxes for all ObjectTypes present in the Cisco Info Server alerts table, specify the field name ObjectType when prompted with:

Pick Database Field

This tool runs on the Cisco Info Admin Desktop and creates an Event List configuration with monitor boxes for all ObjectTypes named by_ObjectType.elc in the user's Personal Library. See the Cisco Info Center User Guide for more information.

Cisco Info Admin Desktop Information

The Cisco Info Admin Desktop Information tool provides you with information regarding the Cisco Info Admin Desktop. This tool is available from the Main Event List Tools menu.

This tools runs on the Cisco Info Admin Desktop and provides the following information:

• Info Center User - user name logged into the Cisco Info Server

• Cisco Info Server - name of Cisco Info Server connected to

• License Servers - indicates where the Cisco Info Admin Desktop is getting the license

• UNIX User - UNIX user that started the Conductor

• Internal X Display - X display set by the Conductor

• External X Display - X display as set in shell that executed the Conductor

• Calculated Display - X display where the tools send the display

• UNIX Host Info - architecture, operating system, and name of the UNIX host

• Info Center version and patch information.

HP OpenView Network Node Manager

This tool launches the HP OpenView Network Node Manager application from the Cisco WAN Manager machine onto the Cisco Info Admin Desktop. This tool is available from the Main Event List Tools menu. The $DISPLAY variable is passed to the HP OpenView Network Node Manager.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

Cisco WAN Manager Desktop

This tool launches the Cisco WAN Manager desktop from the Cisco WAN Manager machine onto the Cisco Info Admin Desktop. This tool is available from the Sub Event List Tools menu. The $DISPLAY variable is passed to the Cisco WAN Manager Desktop Tool.

This tool uses the External Action in Automations to launch the tool remotely on the Cisco WAN Manager machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.

Using Automation to Run Tools

Tools, by default, run on the local Desktop, that is, the server running the Desktop. As Cisco Info Center is designed to be a client/server application, it is necessary to install the application in the tool to be installed, and configure it on every client Desktop. As this is difficult to administer, the remote launching of tools has been configured using automation so as to centralize the management of these tools.

The tool is normally configured to run on every Cisco Info Admin Desktop, using the command:

host% xterm -e telnet @NEAddress

This launches Xterm locally, and within the Xterm, spawns the Telnet session.

While the xterm and telnet commands (and applications) are available on all X sessions running client/server, there is no guarantee of a route from the Desktop to the network elements. There may be security constraints in adding these routes, and as a result, this tool has been configured to run on the Cisco WAN Manager machine using Automation, with the results displayed back to the Desktop that had originated the request.

This process works by the Desktop adding an Automation in the auto.triggers and auto.actions tables. The auto.actions for each event performs a data effect and an external effect. See Chapter 5, "Automation", for more information.

Data effect deletes the trigger and the action, as the external action would have already been passed to the Process Control on the host specified in the external effect host parameter.

External effect queues the external action, passed as a parameter from the tool executed from the Event List to the Process Control specified in the external effect host parameter. One of the arguments passed is the DISPLAY variable, which provides the executable on the host to run the application and display the results back to the DISPLAY variable.

Mandatory requirements for launching processes using automation are:

1. The DISPLAY variable must always be passed.

2. Process Control must always be configured and running on the application server.

3. Process Control record must be configured on the Cisco Info Server host when the application servers are different than the Cisco Info Server host.

An Example of Using Automation to Run Remote Tools

Node to run the tool on, passed to the host field in the external actions in Automation:

NODE=<Cisco WAN Manager host>

Set up the OMNIHOME variable:

OMNIHOME=/opt/Omnibus

The absolute path of the executable:

EXEC=$OMNIHOME/utils/AdminGUI/admingui

The following five lines set up the DISPLAY variable to be passed as a parameter:

if [ "x\Qecho %display|cut -d: -f1\Q" = "x" ]; then

DISPLAY=\Qhostname\Q:0.0

else

DISPLAY=%display

fi

export DISPLAY

Argument line to be passed to the external actions in automation:

ARGLINE="$DISPLAY @NEAddress"

The following two lines set up the unique ID for the automation:

ID=${NODE}agui%display\Qdate|sed 's/[ :]//g'\Q

IDENT=\Qecho $ID|sed 's/[ :/.]//g'\Q

The following six lines add the automations to the auto.triggers and auto.actions tables using nco_sql:

$OMNIHOME/bin/nco_sql -server %server -user %username -password %password <<EOF

insert into auto.triggers values ('$IDENT','select * from auto.actions;','','','','$IDENT','',0,1,1,1,0,0,0,'','','','');
insert into auto.actions values ('$IDENT',1,'delete from auto.actions where Name = \'$IDENT\';delete from auto.triggers where Name = \'$IDENT\';','','','',1,'$EXEC','$ARGLINE','$NODE',0,0,'','','','','','','','' );
go
quit
EOF
auto.triggers:
select * from auto.actions
auto.actions:
Internal Effect: delete from auto.actions where Name = $IDENT;
External Effect: 
Executable - $EXEC
Arguments - $ARGLINE
Host - $NODE
User - 0

Resolutions

Resolutions are used to ensure fast and consistent clearing of alerts. A single resolution contains a title for a menu option and text to be stored in the journal. Resolutions are grouped by class allowing each class to have a set of related resolutions.

When you select the Alerts menu's Resolve option with an alert selected, the menu displays all the resolutions defined for the class value of that alert. When you select a resolution, the text defined for the resolution is appended to the alerts journal, along with user name and timestamp, and the alert is set to clear.

The Resolutions Window

You click on the Resolutions button to display the Resolutions window, as shown in Figure 4-8.

Add a Resolution

To add a resolution:

1. Select the class you want to associate with the resolution in the upper list of classes.

2. Click on the New button.

3. Specify the title for the resolution in the Title field; this text becomes the displayed menu option.

4. Click in the Resolution Text field and specify the text for the resolution; this text becomes the entry in the Journal when the resolution is used.

5. Click on the Update button, which is highlighted in red, to add the resolution.

Change a Resolution

To change a resolution:

1. Select the class that has the resolution associated with it in the upper list of classes. The Resolutions List is modified to show the currently installed resolutions.

2. Select the resolution you wish to change. You can now edit the Resolution Text but not the Title.

To create a new title, create a new resolution and delete the old resolution. Once the Resolution Text has been changed, the Update button turns red. Click on the Update button to make the changes.

Delete a Resolution

To delete a resolution, select the class that has the resolution associated within it in the upper list of classes. The Resolutions List is modified to show the currently installed resolutions. Select the resolution you wish to delete in the Resolutions List, then click on the Delete button.

Cisco Info Server Properties

The Cisco Info Server uses a set of properties to control its behavior. These properties can only be changed by a super user.

It is essential you are familiar with the properties before modifying them. Incorrect configuration can severely impact the performance of the system.

Modifying Cisco Info Server Properties

To display the Properties window, shown in Figure 4-9, click on the Properties button.

The Configuration Manager creates the properties information dynamically by querying the Cisco Info Server to determine which properties are available. The display shown in Figure 4-9 is for the standard Cisco Info Server. It is made up of text fields and checkboxes for each option.

When you click on the Apply button, the properties are set in the Cisco Info Server but are not saved. When you click on the Save button, the properties are set in the Cisco Info Server and then saved. The saved properties are then used when the Cisco Info Server is next restarted.

Property Controls

AllowConnections

This property controls whether or not anyone can connect to the Cisco Info Server. It should be enabled unless you wish to block new connections to the Cisco Info Server.

AllowISQL

This property controls whether or not anyone can connect to the Cisco Info Server using the isql or nco_sql commands. Enable this property to allow this type of connection; disable this property to block isql and nco_sql connections.

AuditAutomation

This property controls whether or not changes to the Automation system, that is, to triggers or actions, should generate SystemWatch alerts. SystemWatch alerts notify users that changes have taken place and can subsequently be logged for future reference. Enable this option to generate SystemWatch alerts. Disable this option to allow Automation changes to occur without generating alerts.

AuditConfig

This property controls whether or not changes to the configuration, that is, changes made by this tool, should generate SystemWatch alerts. SystemWatch alerts notify users that changes have taken place and can subsequently be logged for future reference. Enable this option to generate SystemWatch alerts. Disable this option to allow configuration changes to occur without generating alerts.

AuditNames

This property controls whether or not changes to the User List, that is, changes made by the User Administration tool, should generate SystemWatch alerts. SystemWatch alerts notify users that changes have taken place and can then be subsequently logged for future reference. Enable this option to generate SystemWatch alerts. Disable this option to allow user changes to occur without generating alerts.

AutoTick

This property controls the timing of the Automation system. It is set to 1 by default, allowing Automation to wake up every second. Do not change this property, unless you are advised by technical support.

DeackOnReawaken

This property extends the functionality of the ReawakenClosed property. When ReawakenClosed and DeackOnReawaken are enabled and an alert is reawakened, the Acknowledged field is cleared, making the alert deacknowledged.

DebugActions

This property controls whether or not actions in Automation should be logged. Enable this option to log the execution of actions by the Automation system in the Cisco Info Server log. When this option is disabled, the actions are executed without logging.

DebugLevel

This property controls the level of messages generated by the Cisco Info Server. The higher the value, the more debug messages are placed in the Cisco Info Server log.

DebugTriggers

This property controls whether or not triggers in Automation should be logged. Enable this option to log the execution of triggers by the Automation system in the Cisco Info Server log. When you disable this option, the triggers are executed without logging.

Granularity

This property controls the regularity of IDUC broadcasts to client tools. The value is in seconds. Reducing this value increases the refresh rate of Desktop tools, however, it increases the load on the Cisco Info Server. It is recommended this value be left at the default of 60.

LogInterval

This property controls the regularity of the Cisco Info Server consolidation of its persistently stored files. The value is in seconds. The default is 300, which means that every 5 minutes, the Cisco Info Server writes out the database tables and clears the transaction record files. Reducing this value increases the I/O load on the Cisco Info Server and the system it is running on.

MonitorConnections

This property controls whether or not an alarm is generated, which indicates that a process has connected to the Cisco Info Server.

ReawakenClosed

This property controls whether or not new alerts reawaken duplicate alerts that are closed in the Cisco Info Server. When you enable this option (the default), and a new alert arrives which matches an existing alert in the Cisco Info Server, only the Count field is incremented and the LastOccurrence time is updated from the new alert. When you disable this option, the same process occurs with one additional element; when the alert in the Cisco Info Server has been closed (that is, Severity=0), the Severity field is updated with the severity value from the incoming alert.

UpdateAlertKey

This property controls the updating of the AlertKey field in an alert when deduplication occurs. When you enable this option, and an alert is deduplicated, the AlertKey field from the new alert is copied into the existing alert before the new alert data is discarded.

UpdateSummary

This property controls the updating of an alert's Summary field when deduplication occurs. When you enable this option, and an alert is deduplicated, the Summary field from the new alert is copied into the existing alert before the new alert data is discarded.

Posted: Thu Mar 18 11:22:20 PST 1999
Copyright 1989-1999©Cisco Systems Inc.