|
|
This chapter includes the following sections:
Configuration options in Cisco Info Center include the ability to configure the following:
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.
To start the Configuration Manager, select the Configuration button from the Conductor button bar.
You can also start the Configuration Manager from the command line as follows:
host% $OMNIHOME/bin/nco_config &
Figure 4-1 shows the Configuration Manager window.

Select the File menu's Exit option to exit the Configuration Manager tool.
The following sections describe each of the configuration options.
When Cisco Info Center displays information, it can translate numeric values into strings making them easier to read. 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.

At the top is a list of all the currently known conversions, displayed as column name, value, and string.
Below the list are fields used to specify and edit new conversions. These fields are Column, which displays the name of the column in the Cisco Info Server, Value, which displays the integer value for the conversion, and Conversion, which displays the string the value is converted to.
Below these fields are the list editing buttons, New, Update, Delete, and Cancel.
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.
To delete a conversion, select the conversion in the list, then click on the Delete button.
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.
You click on the Visuals button to display the Column Visuals window, as shown in Figure 4-3.

At the top of the window is a list of all columns which have visual settings defined. Below this is a set of fields which are used for the entry and editing of the visuals.
The Column field displays the name of the column with which the attributes are associated. To the right is an option button which controls the justification of data displayed for that field, which can be Left, Right, or Center.
Below this is the Title field, which contains the title to be displayed for that column. To the right of this field is an option button for controlling the justification of the title text.
Below this are two sliders. The Default Width slider controls the default character width of the field when displayed. The Maximum Width slider controls the maximum width for the field in the View Builder.
To delete a visual, select the column name from the scrolling list, then click on the Delete button.
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 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 that alert.
To modify the classes, click on the Classes button. The Classes window is displayed, as shown in Figure 4-4.

At the top of the window, a list is displayed showing all of the known classes in the system.
Below this are fields used for displaying, specifying, and editing the class information. The Identifier field is used to display the numeric value of the class. Note, an identifier value of 0 is used as the default class and is used when no class has been set in an alert.
The Name field is used to specify the text string to be displayed when you refer to the class.
The Menu field is used to specify the name of a menu associated with the class.
Below this is an Image Selector pane for selecting the icon associated with the class. Move the slider or click on the left and right arrow buttons to move through the library of available images.
Selecting an existing class in the list displays the details for that class in the lower fields. You can 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 not applied. When you wish to discard the changes, click on the Cancel button.
To delete a class, select the class in the list of classes, then click on the Delete button.
lists all of the classes for the Cisco Info Center. These classes define the context sensitive tools available in the Event List.
| Class Name | Class Number | Menu |
|---|---|---|
Default Class | 0 | DefaultMenu |
AXISCard | 1005 | Class1005-Menu |
AXISCard | 1006 | Class1006-Menu |
Class20 | 1010 | Class1010-Menu |
Class20 | 1011 | Class1011-Menu |
System | 1015 | Class1015-Menu |
System | 1016 | Class1016-Menu |
IPX/IGX/ Connections | 1020 | Class1020-Menu |
IPX/IGX/ Connections | 1021 | Class1021-Menu |
AXISLine | 1025 | Class1025-Menu |
AXISLine | 1026 | Class1026-Menu |
AXIS Ports | 1030 | Class1030-Menu |
AXIS Ports | 1031 | Class1031-Menu |
Class70 | 1035 | Class1035-Menu |
Class70 | 1036 | Class1036-Menu |
AXIS Connections | 1040 | Class1040-Menu |
AXIS Connections | 1041 | Class1041-Menu |
IPX/BPX/IGXLine | 1045 | Class1045-Menu |
IPX/BPX/IGXLine | 1046 | Class1046-Menu |
BPX-Port | 1050 | Class1050-Menu |
BPX-Port | 1051 | Class1051-Menu |
IPXPort | 1055 | Class1055-Menu |
IPXPort | 1056 | Class1056-Menu |
BPXCard | 1060 | Class1060-Menu |
BPXCard | 1061 | Class1061-Menu |
IPX/IGX/3800 | 1065 | Class1065-Menu |
IPX/IGX/3800 | 1066 | Class1066-Menu |
Peripheral | 1070 | Class1070-Menu |
Peripheral | 1071 | Class1071-Menu |
Class150 | 1075 | Class1075-Menu |
Class150 | 1076 | Class1076-Menu |
AXISLine-SRM3T3 | 1080 | Class1080-Menu |
AXISLine-SRM3T3 | 1081 | Class1081-Menu |
Class170 | 1085 | Class1085-Menu |
Class170 | 1086 | Class1086-Menu |
Class180 | 1090 | Class1090-Menu |
Class180 | 1091 | Class1091-Menu |
AXISLine-X21 | 1095 | Class1095-Menu |
AXISLine-X21 | 1096 | Class1096-Menu |
BPX Connections | 1100 | Class1020-BPX-Menu |
UserLogin | 1105 | Class1065-Menu |
BPXEndpoint | 1115 | BPXEndpointMenu |
FREndpoint | 1120 | FREndpointMenu |
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.
| 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 |
Cisco Info Center allows you to create and associate menus with particular tools or classes of alerts. For example, you can create:
A menu comprises a menu name and a list of menu options. Each of these menu options has a title and a command associated with it. 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.
To display the Menus window, shown in Figure 4-5, click on the Menus button.

The Menus pane displays the menus that have been created. Table 4-3 shows the default menus available.
| 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. |
Class1006-Menu | Context Sensitive Tools Menu for Class 1006. |
Class1010-Menu | Context Sensitive Tools Menu for Class 1010. |
Class1011-Menu | Context Sensitive Tools Menu for Class 1011. |
Class1015-Menu | Context Sensitive Tools Menu for Class 1015. |
Class1016-Menu | Context Sensitive Tools Menu for Class 1016. |
Class1020-Menu | Context Sensitive Tools Menu for Class 1020. |
Class1021-Menu | Context Sensitive Tools Menu for Class 1021. |
Class1025-Menu | Context Sensitive Tools Menu for Class 1025. |
Class1026-Menu | Context Sensitive Tools Menu for Class 1026. |
Class1030-Menu | Context Sensitive Tools Menu for Class 1030. |
Class1031-Menu | Context Sensitive Tools Menu for Class 1031. |
Class1035-Menu | Context Sensitive Tools Menu for Class 1035. |
Class1036-Menu | Context Sensitive Tools Menu for Class 1036. |
Class1040-Menu | Context Sensitive Tools Menu for Class 1040. |
Class1041-Menu | Context Sensitive Tools Menu for Class 1041. |
Class1045-Menu | Context Sensitive Tools Menu for Class 1045. |
Class1046-Menu | Context Sensitive Tools Menu for Class 1046. |
Class1050-Menu | Context Sensitive Tools Menu for Class 1050. |
Class1051-Menu | Context Sensitive Tools Menu for Class 1051. |
Class1055-Menu | Context Sensitive Tools Menu for Class 1055. |
Class1056-Menu | Context Sensitive Tools Menu for Class 1056. |
Class1060-Menu | Context Sensitive Tools Menu for Class 1060. |
Class1061-Menu | Context Sensitive Tools Menu for Class 1061. |
Class1065-Menu | Context Sensitive Tools Menu for Class 1065. |
Class1066-Menu | Context Sensitive Tools Menu for Class 1066. |
Class1070-Menu | Context Sensitive Tools Menu for Class 1070. |
Class1071-Menu | Context Sensitive Tools Menu for Class 1071. |
Class1075-Menu | Context Sensitive Tools Menu for Class 1075. |
Class1076-Menu | Context Sensitive Tools Menu for Class 1076. |
Class1080-Menu | Context Sensitive Tools Menu for Class 1080. |
Class1081-Menu | Context Sensitive Tools Menu for Class 1081. |
Class1085-Menu | Context Sensitive Tools Menu for Class 1085. |
Class1086-Menu | Context Sensitive Tools Menu for Class 1086. |
Class1090-Menu | Context Sensitive Tools Menu for Class 1090. |
Class1091-Menu | Context Sensitive Tools Menu for Class 1091. |
Class1095-Menu | Context Sensitive Tools Menu for Class 1095. |
Class1096-Menu | Context Sensitive Tools Menu for Class 1096. |
Class1123-Menu | Context Sensitive Tools Menu for Class 1123. |
Class1125-Menu | Context Sensitive Tools Menu for Class 1125. |
Class1127-Menu | Context Sensitive Tools Menu for Class 1127. |
Class1305-Menu | Context Sensitive Tools Menu for Class 1305. |
Class1306-Menu | Context Sensitive Tools Menu for Class 1306. |
Class1307-Menu | Context Sensitive Tools Menu for Class 1307. |
Class1308-Menu | Context Sensitive Tools Menu for Class 1308. |
Class1020-BPX-Menu | Context Sensitive Tools Menu for Class 1100 and 1101. |
BPXEndpointMenu | Context Sensitive Tools Menu for Class 1115 and 1116. |
FREndpointMenu | Context Sensitive Tools Menu for Class 1120 and 1121. |
FTCPortMenu | Context Sensitive Tools Menu for Class 1110 and 1111. |
1. Click on the New button in the Menus pane.
2. Specify the name of the menu in the Name field. This should be an already defined name in the Class window. See Section, "Classes" for more information.
3. Adjust the Columns slider.
4. Click on the Update button.
To delete a menu, select the menu entry to delete, then click on the Delete button.
Note, deleting a menu deletes the menu and all of its associated options.
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 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, "Creating Commands", for information about the complete format and content of a command.
4. Select the Redirect Output option. 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 specified command. When this option is not selected, the output is discarded.
5. Select the Redirect Errors option. 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 specified command. When this option 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 of the menu options.
1. Select the menu entry.
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.
To delete a menu option, select the menu, select the menu option, then click on the Delete button.
The following sections describe how to use elements and parameters with a command in the Command field.
Elements are used for passing information to the command. The types of elements you can insert are:
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.
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.
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 the 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.
Table 4-4 lists the menu options (tools) for the defined Menus.
| Menu | Menu Options |
|---|---|
ConductorMenu | Create Event List |
DefaultMenu |
|
MainEventListMenu | Desktop Information |
SubEventListMenu | StrataView Desktop |
ObjViewMenu |
|
ObjViewMapMenu |
|
Class1005-menu | Administration GUI |
Class1006-menu | Administration GUI |
Class1010-Menu | Administration GUI |
Class1011-Menu | Administration GUI |
Class1015-Menu | Administration GUI |
Class1016-Menu | Administration GUI |
Class1020-BPX-Menu | Administration GUI Get Configuration Real Time Counters Test Delay Add Loopback Delete Loopback |
Class1020-Menu | Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback |
Class1021-Menu | Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback CiscoView |
Class1025-Menu | Administration GUI Get Configuration Real Time Counters Decode BitMap Equipment Manager |
Class1026-Menu | Administration GUI Get Configuration Real Time Counters Decode BitMap CiscoView |
Class1030-Menu | Administration GUI Get Configuration Real Time Counters Decode BitMap Equipment Manager |
Class1031-Menu | Administration GUI Get Configuration Real Time Counters Decode BitMap CiscoView |
Class1035-Menu | Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback Decode BitMap Equipment Manager |
Class1036-Menu | Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback Decode BitMap CiscoView |
Class1040-Menu | Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback Equipment Manager |
Class1041-Menu | Administration GUI Get Configuration Real Time Counters Test Connections Test Delay Add Loopback Delete Loopback CiscoView |
Class1045-Menu | Administration GUI Get Configuration Real Time Counters |
Class1046-Menu | Administration GUI Get Configuration Real Time Counters CiscoView |
Class1050-Menu | Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback |
Class1051-Menu | Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback CiscoView |
Class1055-Menu | Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback |
Class1056-Menu | Administration GUI Real Time Counters Add Loopback Delete Loopback CiscoView |
Class1060-Menu | Administration GUI Get Configuration |
Class1061-Menu | Administration GUI Get Configuration CiscoView |
Class1065-Menu | Administration GUI Get Configuration |
Class1066-Menu | Administration GUI Get Configuration CiscoView |
Class1070-Menu | Administration GUI |
Class1071-Menu | Administration GUI CiscoView |
Class1075-Menu | Administration GUI Get Configuration Decode BitMap |
Class1076-Menu | Administration GUI Get Configuration Decode BitMap CiscoView |
Class1080-Menu | Administration GUI Get Configuration Real Time Counters Equipment Manager |
Class1081-Menu | Administration GUI Get Configuration Real Time Counters CiscoView |
Class1085-Menu | Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback Equipment Manager |
Class1086-Menu | Administration GUI Get Configuration Real Time Counters Add Loopback Delete Loopback CiscoView |
Class1090-Menu | Administration GUI Decode BitMap Equipment Manager |
Class1091-Menu | Administration GUI Decode BitMap CiscoView |
Class1095-Menu | Administration GUI Get Configuration Decode BitMap Equipment Manager |
Class1096-Menu | Administration GUI Get Configuration Decode BitMap CiscoView |
Class1123-Menu | Administration GUI Get Configuration Real Time Counters CiscoView |
Class1125-Menu | Administration GUI Get Configuration CiscoView |
Class1127-Menu | Reserved |
Class1305-Menu | Administration GUI Get Configuration Equipment Manager |
Class1306-Menu | Administration GUI Get Configuration CiscoView |
Class1307-Menu | Administration GUI Real Time Counters Equipment Manager |
Class1308-Menu | Administration GUI Real Time Counters CiscoView |
BPXEndpointMenu | Administration GUI |
FREndpointMenu | Administration GUI |
FTCPort | Administration GUI |
This section describes the functionality for each of the menu options listed in Table 4-4.
This tool displays the Equipment Manager tool that displays the shelf view for the 4.05 and earlier versions of AXIS network elements.
This tool is available only for events reported by the AXIS 4.05 NEType network elements and runs on the Cisco StrataView Plus (SV+) machine. This tool uses the External Action in Automations to launch the tool remotely on the Cisco SV+ 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 SV+ Equipment Manager tool are:
This tool displays the 4.11 CiscoView tool that manages Switch Software releases BPX 8.4/8.5/9.1, IGX 8.5/9.1, and AXIS 4.1.
This tool is available only for events reported by the BPX, IGX, and AXIS 4.0.15 NEType network elements and runs on the Cisco StrataView Plus (SV+) machine. This tool uses the External Action in Automations to launch the tool remotely on the Cisco SV+ 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 SV+ Equipment Manager tool are:
This tool uses the Cisco SV+ 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 SV+ 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:
This tool displays the configuration of the alarmed resource as stored in the Cisco SV+ 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 SV+ Informix OnLine database.
This tool uses the External Action in Automations to launch the tool remotely on the
Cisco SV+ 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:
| Object Type | Informix Table |
|---|---|
network element | node |
card | card |
connection | user_connection |
port.ATM | NEType=AXIS: ausm_port |
port.FR | SubObjectType=frp: FRP |
line.access | AXIS: line |
line.trunk | AXIS: line |
endpoint.ATM | atm_connection |
endpoint.FR | AXIS: connection |
endpoint.CE | user_connection |
endpoint.VoiceData | user_connection |
The variables passed to the Get Configuration tool are:
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 SV+ 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:
This tool uses the External Action in Automations to launch the tool remotely on the
Cisco SV+ 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:
This tool uses the External Action in Automations to launch the tool remotely on the
Cisco SV+ 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:
The tool performs the loopback addition by logging into the Cisco SV+ machine using the user name and password provided above, and then logging into the network element from the Cisco SV+ 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 SV+ 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.
| ObjectType | NEType | Command | Parameters |
|---|---|---|---|
Port.ATM, Port.FR | IPX,IGX,BPX | addlp | @Slot, @PSAP |
Connection | IPX,IGX,BPX | addlocrmptlp | @Slot, @PSAP, @DSAP |
Endpoint Connection | BPX | addlocl | @Slot, @PSAP, @DSAP |
Endpoint Connection | IPX/IGX | addlocl | @Slot, $Port, @DSAP |
Endpoint Connection | AXIS | addchanloop | Channel number, returned from query into Informix database. |
Port.CE | AXIS | addlp | @Slot, @PSAP |
Port.VoiceData | Not applicable | Not applicable | Not applicable |
Table 4-7 lists the variables passed to the Add Loopback tool.
| Parameters |
|---|
<Cisco Info Server Name> |
<Cisco Info Server User Name> |
<Cisco Info Server Password> |
$DISPLAY |
<StrataView+ Host Name> |
<StrataView+ User ID> |
<StrataView+ Password> |
@ObjectType |
@ServiceType |
@NEType |
@NEName |
@NEAddress |
<network element Login ID> |
<network element Login Password> |
@Slot |
@PSAP |
@LSAP |
@DSAP |
<Type> (Add|Del) |
Loopback Command |
The tool performs the loopback deletion by logging into the Cisco SV+ machine using the user name and password provided above, and then logging into the network element from the Cisco SV+ 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 SV+ 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.
| ObjectType | NEType | Command | Parameters |
|---|---|---|---|
Port.ATM, Port.FR | IPX, IGX, BPX | dellp | @Slot, @PSAP |
Endpoint Connection | BPX | dellp | @Slot, @PSAP, @DSAP |
Endpoint Connection | IPX/IGX | dellp | @Slot, $Port, @DSAP |
Endpoint Connection | AXIS | delchanloop | Channel number, returned from query into Informix database. |
Port.CE | AXIS | dellp | @Slot, @PSAP |
Port.VoiceData | Not applicable | Not applicable | Not applicable |
Table 4-9 lists the variables passed to the Delete Loopback tool.
| Parameters |
|---|
<Cisco Info Server Name> |
<Cisco Info Server User Name> |
<Cisco Info Server Password> |
$DISPLAY |
<StrataView+ Host Name> |
<StrataView+ User ID> |
<StrataView+ Password> |
@ObjectType |
@ServiceType |
@NEType |
@NEName |
@NEAddress |
<network element Login ID> |
<network element Login Password> |
@Slot |
@PSAP |
@LSAP |
@DSAP |
<Type> (Add|Del) |
Loopback command |
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:
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.
This tools runs on the Cisco Info Admin Desktop and provides the following information:
This tool uses the External Action in Automations to launch the tool remotely on the
Cisco SV+ machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.
This tool launches the Cisco SV+ Desktop from the Cisco SV+ 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 SV+ Desktop Tool.
This tool uses the External Action in Automations to launch the tool remotely on the
Cisco SV+ machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.
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 SV+ 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.
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.
Node to run the tool on, passed to the host field in the external actions in Automation:
NODE=<Cisco SV+ host>Set up the OMNIHOME variable:
OMNIHOME=/opt/OmnibusThe absolute path of the executable:
EXEC=$OMNIHOME/utils/AdminGUI/adminguiThe following lines set up the DISPLAY variable to be passed as a parameter:
if [ "x\Qecho %display|cut -d: -f1\Q" = "x" ]; thenDISPLAY=\Qhostname\Q:0.0elseDISPLAY=%displayfiexport DISPLAYxhost $NODEArgument line to be passed to the external actions in automation:
ARGLINE="$DISPLAY @NEAddress"The following lines set up the unique ID for the automation:
ID=${NODE}agui%display\Qdate|sed 's/[ :]//g'\QIDENT=\Qecho $ID|sed 's/[ :/.]//g'\QThe following 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 <<EOFinsert 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
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.
You click on the Resolutions button to display the Resolutions window, as shown in Figure 4-8.

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.
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.
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.
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.
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.
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.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Apr 1 10:58:29 PST 1999
Copyright 1989-1999©Cisco Systems Inc.