|
|
You can access most Cisco Info Center configuration tasks from the Configuration Manager window. Figure 3-1 shows the Configuration Manager Win dow with the Automations tab selected.

The tabs on the Configuration Manager window allow you to select the following areas of configuration:
Each tab has its own toolbar and menu bar which are displayed at the top of the Configuration Manager window.
For information on the Users option and user administration, refer to "User Administration."
For information on the Automations option, refer to "Automation."
This chapter describes all of the other configuration options.
You can start the Configuration Manager in two ways:
To start the Configuration Manager from the Conductor, click the Configuration icon.
To start the Configuration Manager from the UNIX command line, enter one of the following commands:
$OMNIHOME/bin/nco_adminwhere option specifies the option you want to appear when the Configuration Manager starts.
In this form of the command, -option is one of the following:
-automations -users -properties -menus -classes -conversions -visuals
The Configuration Manager window tabs display an icon and text. To select a configuration category, click on the tab in the left column frame of the Configuration Manager window.The selected tab appears in front of the other tabs.
The Configuration Manager window toolbar and menu bar are different for each tab. The menu bar contains drop down menus. The toolbar contains buttons for the most frequently used functions.
You can resize the Configuration Manager window by dragging an edge or corner. If the window content is too large for the resized window, scroll bars appear. If the tabs on the left of the Configuration Manager window do not fit in the window, scrolling arrows appear. Click on the arrows to scroll through the tabs.
When Cisco Info Center displays information in the event list, it can translate numeric values into strings for readability. This translation is called a conversion. It is associated with a named column in the Info Server status table.
To edit the specification for converting numeric data, select the Conversions icon on the Configuration Manager window. The Conversions tab appears, shown in Figure 3-2.

The Conversions tab displays a list of columns in the alerts.status database table that have conversions set. Double-click on the column icon to display the conversions currently applied. The conversions are shown indented below each column name.
To add a conversion, complete these steps:
The Add Conversion window appears, shown in Figure 3-3:

Step 2 To select the database column for which to convert the data, click on the Class button and then select the column to convert from the pull-down menu.
Step 3 In the Value field, enter the numeric value that you want to convert.
Step 4 In the Conversion field, enter the string value that you want to replace the numeric value.
Step 5 Click OK to save the converson entry.
To edit a conversion, complete these steps:
The Edit Conversion window appears.
The Edit Conversion and New Conversion windows are identical, except that you cannot modify the Column and Value fields in the Edit Conversion window.
Step 2 In the Conversion field, edit the string to which the value is to be converted.
Step 3 Click OK to save your changes.
To delete a conversion, complete these steps:
Step 2 Do one of the following:
Click on the Delete Conversion button:
The conversion is removed from the column.
To refresh the display and update the list of conversions from the Info Server, select Refresh Conversions from the View menu.
When information about alerts in the Cisco Info Center system is displayed in the event list and other tools, the visual appearance is defined by the settings for the column visuals. Using the Column Visuals tab, you can control the following settings for each field in an alert:
To edit the column visuals, select the Column Visuals tab on the Configuration Manager window. Figure 3-4 shows the Column Visuals tab.

The Column Visuals tab has two columns. The left column lists the fields in the alerts.status table. The right column lists the associated column title displayed in the event list. The icon on the left of the field name indicates the justification of the column.
Table 3-1 shows examples of column visual table field icons
| Icon | Description |
|---|---|
| Title and column justified left. |
| Title justified center and column justified right. |
To add a column visual, complete these steps:
The New Column Visual window appears, shown in Figure 3-5.

Step 2 Select the Column button and choose the column whose appearance you want to edit from the drop down list.
Step 3 Specify the column visual attributes that you want. You can specify the following:
Step 4 Click OK to accept the settings you have added.
Complete these steps to edit a column visual setting.
The Edit Column Visual window appears. This window is identical to the New Column Visual window (shown in Figure 3-5) except that you cannot modify the Column field in the Edit Column Visual window. It appears in gray.
Step 2 Specify the values that you want to change. You can specify the following:
Step 3 Click OK to accept the settings you have changed.
To delete a selected column visual definition, do one of the following:
The column visual definition is removed from the window.
To refresh the display, select Refresh Column Visuals from the View menu.
Alerts in the Info Server have a class assigned by the Info Mediator. Each class can be associated with a tool menu that contains useful tools for alerts of that class.
To edit the classes, select the Classes tab on the Configuration Manager window. Figure 3-6 showsthe Classes tab.
Each entry in the tab displays a unique identifier number and the name of the class.
To add a class, complete these steps:
The New Class window appears, shown in Figure 3-7.

Step 2 In the Identifier field, enter the identifier for the new class. This identifier must be defined in the rules file for each Info Mediator that will use the class.
Step 3 In the Name field, enter a name for the class.
Step 4 If you want to associate an image with the class, select an image from the image frame by using the slider to move from one image to the next. Then click on the image you want to select it.
Step 5 Click OK to create the new class.
To edit an existing class, complete these steps:
The Edit Class window appears
The Edit Class window is identical to the Add Class window, except that you cannot modify the Identifier field in the Edit Class window. It appears in gray.
Step 2 If you want to change the name for the class, change the name that appears in the Name field.
Step 3 If you want to associate an image with the class or change an existing image, select an image from the image frame by using the slider to move from one image to the next. Then click on the image you want to select it.
Step 4 Click OK to modify the class.
To delete a class, complete these steps:
Step 2 Do one of the following:
The class definition is removed from the Classes tab.
Tools allow you to control all alert management functions within Cisco Info Center. Each tool has an associated SQL statement, an executable, or both. You can group tools in tools menus, which you can associate with a class or classes of alert.
You can assign access settings that ensure only authorized users are able to use a particular tool.
You create and edit tools using the Tools window. When you create a tool, it is added to the Info Server tools database. The tools which appear in the Menus tab on the Configuration Manager window and the Tools window are links to entries in this database.
You can configure the menus from the Menus tab in the Configuration Manager window. You can assign menus to the following:
The alert is assigned a class by the alert source. This class can be associated with a menu using the Classes tab of the Configuration Manager window.
Each menu comprises a menu name and a list of menu items. These menu items can be a tool, a separator, or a submenu.
To set up menus, select the Menus tab of the Configuration Manager window.
Figure 3-8 shows an example of the Menus tab.

The Menus tab contains a list of available menus.
Double-click on a menu item to display its associated tools and submenus, if any. Tools and submenus are displayed below the menu name, indented to the right. Click on a sub-menu to display its associated tools.
Each tool has a menu item name and an associated tool name. The tool name is the link to the tool in the tools database. The menu item name appears when the menu is opened. You can modify the menu name as required.
Menu items are tools, separators and sub menus. The status of a tool is indicated by its icon as shown in the "Icons in Tool List" section.
The view can be filtered by selecting a specific group or class from the Configuration Manager window toolbar. See the "Filtering Views" section for more information.
Table 3-2 shows the customized menus that are provided with Cisco Info Center 2.0 and the tools that are associated with them. You can add items to these menus, or remove items from them, but you cannot delete them
| Menu | Menu Description and Associated Tools |
Conductor Menu:Tools | Tools menu on the main Conductor menu. Includes the following tools:
|
Event List: AlertsMenu | Alerts menu on the event list. This menu appears when you select an alert and includes the following tools:
|
MainEventListMenu : Tools | Tools menu on the Monitor Box window of the event list. Lists the following tools:
|
MainOVMenu | Tools menu on the objective view main window. |
SubEventListMenu: Tools | Tools menu on any window of displayed alerts. Lists the CWM Desktop tool, which starts the Cisco WAN Manager desktop on a specified host. |
MapPageOVMenu | Tools menu on any open objective view map page and the Unplaced Events window. |
SymbolToolsMenu | Tools menu on right click on an objective view symbol. |
The following sections describe the Cisco tools that are listed on the menus described in Table 3-2.
This tool displays the 4.11 CiscoView tool that manages Switch Software releases BPX 8600 8.4/8.5/9.1, IGX 8400 8.5/9.1, and MGX 8220 4.1.
This tool is available only for events reported by the BPX 8600, IGX 8400, and MGX 8220 4.0.15 NEType network elements and runs on the Cisco Wan Manager (CWM) machine. This CWM machine and to display to the Info Admin Desktop. See the"Using Automation to Run Tools" section for more information.
The variables passed to the CWM Equipment Manager tool are:
This tool uses the CWM 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
CWM machine and to display to the Cisco Info Admin Desktop. See the"Using Automation to Run Tools" section for more information.
The variables passed to the Administration GUI are:
This tool displays the configuration of the alarmed resource as stored in the CWM 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 CWM Informix OnLine database.
This tool uses the External Action in Automations to launch the tool remotely on the CWM machine and to display to the Cisco Info Admin Desktop. See the"Using Automation to Run Tools" section for more information.
Table 3-3 lists the Informix tables used by the Get Configuration tool.
| Object Type | Informix Table |
|---|---|
network element | node |
card | card |
connection | user_connection |
port.ATM | NEType=MGX 8220: ausm_port |
port.FR | SubObjectType=frp: FRP |
line.access | MGX 8220: line |
line.trunk | MGX 8220: line |
endpoint.ATM | atm_connection |
endpoint.FR | MGX 8220: 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 CWM machine and to display to the Cisco Info Admin Desktop. See the "Using Automation to Run Tools" section 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
CWM machine and to display to the Cisco Info Admin Desktop. See the "Using Automation to Run Tools" section 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 CWM machine and to display to the Cisco Info Admin Desktop. See the "Using Automation to Run Tools" section for more information.
The variables passed to the Test Connection tool are:
The tool performs the loopback addition by logging into the CWM machine using the user name and password provided above, and then logging into the network element from the CWM 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 CWM machine and to display to the Cisco Info Admin Desktop. See the "Using Automation to Run Tools" section for more information.
Table 3-4 lists the commands used to add loopback
| ObjectType | NEType | Command | Parameters |
|---|---|---|---|
Port.ATM, Port.FR | IPX,IGX 8400,BPX 8600 | addlp | @Slot, @PSAP |
Connection | IPX,IGX 8400,BPX 8600 | addlocrmptlp | @Slot, @PSAP, @DSAP |
Endpoint Connection | BPX 8600 | addlocl | @Slot, @PSAP, @DSAP |
Endpoint Connection | IPX/IGX 8400 | addlocl | @Slot, $Port, @DSAP |
Endpoint Connection | MGX 8220 | addchanloop | Channel number, returned from query into Informix database. |
Port.CE | MGX 8220 | addlp | @Slot, @PSAP |
Port.VoiceData | Not applicable | Not applicable | Not applicable |
Table 3-5 lists the variables passed to the Add Loopback tool.
| Parameters |
|---|
<Cisco Info Server Name> |
<Cisco Info Server User Name> |
<Cisco Info Server Password> |
$DISPLAY |
<CWM+ Host Name> |
<CWM+ User ID> |
<CWM+ 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 CWM machine using the user name and password provided above, and then logging into the network element from the CWM 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
CWM machine and to display to the Cisco Info Admin Desktop. See the "Using Automation to Run Tools" section for more information.
Table 3-6 lists the commands used to delete a loopback.
| ObjectType | NEType | Command | Parameters |
|---|---|---|---|
Port.ATM, Port.FR | IPX, IGX 8400, BPX 8600 | dellp | @Slot, @PSAP |
Endpoint Connection | BPX 8600 | dellp | @Slot, @PSAP, @DSAP |
Endpoint Connection | IPX/IGX 8400 | dellp | @Slot, $Port, @DSAP |
Endpoint Connection | MGX 8220 | delchanloop | Channel number, returned from query into Informix database. |
Port.CE | MGX 8220 | dellp | @Slot, @PSAP |
Port.VoiceData | Not applicable | Not applicable | Not applicable |
Table 3-7 lists the variables passed to the Delete Loopback tool.
| Parameters |
|---|
<Cisco Info Server Name> |
<Cisco Info Server User Name> |
<Cisco Info Server Password> |
$DISPLAY |
<CWM+ Host Name> |
<CWM+ User ID> |
<CWM+ 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 the "Using Automation to Run Tools" section 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:
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 CWM machine and to display to the Cisco Info Admin Desktop. See Section, "Using Automation to Run Tools", for more information.
This tool launches the CWM Desktop from the CWM 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 CWM Desktop Tool.
![]() |
Note Each display can only invoke one Desktop. |
This tool uses the External Action in Automations to launch the tool remotely on the CWM machine and to display to the Cisco Info Admin Desktop. See the "Using Automation to Run Tools" section, 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 @NEAddressThis 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 CWM 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 , "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.
This section describes how to create, copy, rename and delete sub-menu entries.
To create a new submenu, complete these steps:
The New Sub-Menu window appears
Step 2 Enter a submenu name and click OK.
If the name already exists, you are prompted to enter an alternative name.
Once the window has closed, a new sub-menu entry appears below the parent menu. The sub-menu does not yet contain any tools.
To delete a submenu, complete these steps:
Step 2 Do one of the following:
The submenu is removed from the list.
![]() |
Note You cannot delete default menus. |
To copy a submenu, complete these steps:
Step 2 Do one of the following:
Step 3 To paste the sub-menu, select the destination menu and do one of the following:
![]() |
Note You can move the submenu by cutting it, using the Cut option, instead of copying it. |
To rename a submenu, complete these steps:
Step 2 Do one of the following:
Step 3 The Rename Menu Label window appears.
Step 4 In the Name field, enter the new name for the submenu.
Step 5 Click OK.
When the window closes, the submenu name is updated.
You can control how the menus are populated, change the order of items in a menu, filter the tools displayed, and test the menu display. All tools are linked to entries in the Info Server tools database.
When you add a new tool to a menu, you create a new tool in the tools database. An entry for this tool automatically appears in the Tools window, if open, and in the selected menu.
When you create a new tool in the Tools window, no entry appears in a menu.
When you modify a tool, the change is made to the entry in the tools database. The modification affects the entries in the Menus tab and the entries in the Tools window that are linked to this modified tool.
The Tools window contains the master version of each tool. Menu items are links to the tool.
Tools that appear as menu items on the Menus tab of the Configuration Manager window are automatically assigned an icon based on the enable status of the tool.
Table 3-8 shows the icons that can be assigned to a menu item.
| Icon | Description |
|---|---|
| Enabled Tools. |
| Disabled Tools. |
| The broken icon represents an item which is linked to a tool which does not exist in the tools.actions table. |
When you create a tool using options from the Menus tab, the tool is added to the tools database. In addition, the tool appears in the selected menu and in the Tools window if open.
To add a tool to a menu or sub-menu, complete these steps:
Step 2 Do one of the following:
The New Tool window appears.
For details on the use of the New Tool window see the "Creating and Editing Tools" section.
To add an existing tool to a menu, complete these steps:
Step 2 Do one of the following:
and then select New Tool from the popup menu that appears.
Step 3 Select a tool from the list of tool names.
The new tool appears in the list of items under the menu.
The tool entry in the menu consists of the tool name, which refers to the tool in the tools database, and a label that appears in the menu.
To change the label for a tool, complete these steps:
Step 2 Do one of the following:
The Rename Menu Label window appears.
Step 3 Enter the new name for the menu label and click OK.
The Menus tab displays the new name for the tool.
To edit a tool, complete these steps:
Step 2 Do one of the following:
The Edit Tool window appears.
For information on using the Edit Tool window see the "Creating and Editing Tools" section.
When you delete a tool from a menu, only the menu entry is removed. The tool remains in the database. The tool also remains in the Tools window, and in any other menu in which it appears.
To delete a tool, complete these steps:
Step 2 Do one of the following:
You are prompted to delete the selected tool.
Step 3 If you are sure that you want to delete the tool, click OK; otherwise click Cancel.
The tool is removed from the listing on the Menus tab.
You can add a horizonal line that separates menu items. To add a separator to a menu, complete these steps:
Step 2 Do one of the following:
A separator appears at the bottom of the menu. You can change the position of the separator by using the reposition buttons. For information on the reposition buttons, see the "Arranging Items in a Menu" section.
To rearrange the order of the tools, the separators, or submenus, select the item to be moved and then click on one of the reposition buttons in the toolbar. Table 3-9 shows the buttons that you can use to reposition the menu items.
| Button | Description |
|---|---|
| Move item up one position |
| Move item down one position |
| Move item to top |
| Move item to bottom |
The window is refreshed automatically with the item in its new position.
You must assign class access and group access to each tool. For detailed information on assigning access to tools, see the "Tool Window Access Tab" section.
The Configuration Manager window toolbar includes two filter drop down lists. The first list allows you to select a group. The default entry is (All Groups). The second list allows you to select a class. The default entry is (All Classes).
When the filters are changed from these default options, the text is grayed on any tool that does not match the filter. This shows the menu items that are available for use when the specified group or class does not apply to the alert with which the tool is associated.
You can test menus by clicking on the Test button:
When you choose the Test button, the selected menu appears as a popup menu.
Not all menu items in the Menus tab are displayed. The class or group filter in use affects the menu as follows:
Broken tools do not appear in the menu. Tools that appear in the test menu do not run when selected.
To open the Tools window, click on the Tools Window button:
The Tools window displays all available tools in the left hand column. The other columns show whether the tool has been enabled to do the following:
Tools that are disabled appear in gray.
Figure 3-9 shows an example of the Tools window.

To copy a tool, complete these steps:
Step 2 Do one of the following:
The new tool is added, named Copy of toolname where toolname is the source tool. You do not need to paste it.
The content of the new tool is identical to the source tool. You can now edit the new tool and add it to menus as required.
To edit an existing tool, select the tool and then do one of the following:
For details on the use of the Edit Tool window see the "Creating and Editing Tools" section.
To create a tool, do one of the following:
For details on the use of the New Tool window, see the "Creating and Editing Tools" section.
To delete a tool, do one of the following:
The tool selected is deleted from the Tools window, from the tools database and from every menu which uses the tool.
The New Tool and Edit Tool windows are identical except that you cannot modify the Name field in the Edit Tool window. It appears in gray.
This section describes the New Tool window. You can also refer to it when editing tools.
The New Tool window is divided into five areas. Each is assigned a tab. These tabs are:
Figure 3-10 shows an example New Tool window with the SQL tab selected.

The Name field appears above every tab in the New Tool window. Enter a unique name for the new tool.
The Enable button appears above every tab in the New Tool window. Tools are not available on the Menus tab until they are enabled and the window is closed.
There are separate enable buttons for the SQL command, the executable command and the forced journal entry.
Click OK to close the New Tool window and update the tools.actions table. If SQL has been enabled, the SQL statement is checked. If any errors are found the window remains open until they have been corrected.
By default, the New Tools window is opened with the SQL tab displayed. Figure 3-10 shows an example of the SQL tab.
Type the SQL text or build the SQL statement using the tools provided by the buttons on the right of the frame. The SQL statement appears in the main frame of the SQL tab.
Click this button to enable the SQL effect.
When this button is enabled, the tool is executed once for each row in an event list row selection.
When the tool is executed the expansion tab expands to a string of comma separated values. The string is populated by values from the specified field of each selected row in the event list.
The expansion keyword must not be used with the Execute for All Selected Rows button enabled.
When you click on the SQL Statement Builder button
a popup list appears that contains the following SQL commands:
Click on one of these options to open the associated window.
The delete statement requires a database name and a table name. Enter the details in this window and select the OK button.
The insert statement requires a database name, a table name, and entries for all of the fields in the specified table. When the table is selected, the lower frame changes to show a list of every field name in the selected table. If you do not complete a field, the default value is used. Default values are:
varchar and char fields
time fields
Figure 3-11 shows an example SQL Insert window.

The select statement requires a database name, a table name and a list of fields from the table for selection. When you choose a select statement, the Select window appears. Figure 3-12 shows an example Select window.

Use the arrows to move fields in the Available Fields list to the Selected Fields list, or to remove them from the Selected Fields list. Table 3-10 describes the function of each of these buttons.
| Button | Description |
|---|---|
| Copy all fields to the Selected list. |
| Remove all fields from the Selected list. |
| Copy selected fields to the Selected list. |
| Remove selected fields from the Selected list. |
The service update statement requires a service name and a value. The value can be selected from the options in the drop down list. Values can be Good, Marginal or Poor.
If you select the Sync option, the Sync window appears. In the Sync window, first select either Database or Table. If Database is selected, enter only the database name. If Table is selected, enter the database and table names.
If you select the Update option, the Update window appears, shown in Figure 3-13. The Update window allows you to create an SQL expression, edit an existing expression, or delete an expression.

To update an expression, complete these steps:
The Update window appears.
Step 2 Select a database name from the drop down list.
Step 3 Select a table name from the drop down list.
Step 4 Click the New button.
The Edit Expression window appears. Figure 3-14 shows an example of an Edit Expression window.
You use the Edit Expression window to edit and create value and prompt expressions. The next two sections describe how to do this.
To create or edit a prompt expression, complete these steps:
Step 2 Select a field name from the drop down list.
Step 3 Select a prompt name from the drop down list.
Step 4 Do one of the following.
If you select the New... button, the New Prompt window appears. For information on this window, see the "Prompt Definitions" section.
To create or edit a value expression, complete these steps:
Step 2 Select the field name from the drop down list.
Step 3 Enter a default value in the Value field.
The Value field only allows you to enter values that match the field type.
The use statement specifies the database name to use in the SQL statement.
To open a list of available field names in the alerts.status table, click on the Column Names button:
Click on a column name to add the name to the SQL statement.
The column name is substituted for the corresponding event list row value when the tool is executed.
To open a list of available conversions, click on the Conversion Names button:
When an option is selected it opens a popup window showing the list of conversions. Select a conversion name from the list.
To open a list of Internal Values, click on the Internal button:
Table 3-11 lists and describes the internal values.
| Internal Value | Description |
|---|---|
display | The current display running the application. |
password | The password of the user running the application. |
server | The name of the Info Server to which the tool is currently connected. |
UID | The user identifier of the user running the application. |
username | The username of the user running the application. |
To add a prompt name,. click on the Prompt Names button and select a prompt from the list of prompt names in the popup list:
To open the Filter Builder window, click on the Start Filter Builder button:
See theCisco Info Center User Guide for details on the Filter Builder window.
You use the Executable tab to create external executable commands for a tool.
Figure 3-15 shows an example of an Executable tab on a New Tool window. The Platform frame in the lower part of the tab and the selection arrows to the right of the Platform frame allow you to specify which platform(s) the tool can function on.

Click the Enabled button to enable the executable action.
When this toggle button is enabled, the executable part of the tool is executed once for each row in the event list selection.
The Redirect Output toggle button controls where the output of a command is sent. When it is not selected, the output is discarded. When it is selected, the output is echoed in a read only window.
The Redirect Errors toggle button controls where any error messages from a command are sent. When it is not selected, error messages are discarded. When it is selected, errors are echoed through a read only window in whichever tool used the command.
To open a list of available field names in the alerts.status table, click on the Column Names button:
Click on a column name to add the name to the executable statement.
The column name entry in an executable statement allows values from the selected event list to be used as parameters in the executable commands. The column name is substituted for the corresponding event list row value when the tool is executed.
To open a list of Internal Values, click on the Internal button:
To open a list of available environment variables for the local machine, click on the Environment Variable button:
To open a list of available prompt names, click on the Prompt Names button:
In the Platform frame, select the platforms which are able to run the executable.
There are four buttons to add platforms to the Selected list and remove platforms from the Selected list. Table 3-12 describes the function of each of these buttons.
| Button | Description |
|---|---|
| Copy all platforms to the Selected frame. |
| Remove all platforms from the Selected frame. |
| Copy selected platforms to the Selected frame. |
| Remove selected platforms from the Selected frame. |
The Journal tab is used to write journal text. This text is appended to the journal of the selected alert or alerts when the tool is executed.
An example of a Journal tab on a New Tool window is shown in Figure 3-16.

When you execute a tool that has the Force Journal Entry button enabled, a new window opens and the text from the Journal tab is displayed in it. You can then add more text before clicking the OK button to complete the tool execution.
When this button is enabled the journal par t of the tool is executed once for each row in the selection.
To open a list of available field names in the alerts.status table, click on the Column Names button:
Click on a column name to add the name to the journal statement.
The column name is substituted for the corresponding event list row value when the tool is executed.
To open a list of Internal Values, click on the Internal button:
Select the internal value to add it to the journal entry.
Internal values appear in the SQL script as the expansion keyword %name, where name is the name of the internal value.
To open a list of available prompt names, click on the Prompt Names button:
The Access tab of the New Tool window allows you to specify the classes or user groups which can use the tool.
Figure 3-17 shows an example of the Access tab on the New Tool window.

Use the buttons shown in Table 3-12 to select and deselect one or all of the classes and user groups.
The tool is not available to a user who is not in a selected user group. The tool is not available to an alert which has a class not in the list of selected classes. For details on how an unavailable tool appears in a menu, see the "Filtering Views" section.
The Description tab of the New Tool window allows you to enter notes describing the function of the tool.
An example of a Description tab on a New Tool window can be seen in Figure 3-18.

Enter a description of the tool on this tab.The description does not affect the operation of the tool.
A tool can include a prompt window or a popup menu for the user to enter information. You can enter a prompt in an SQL statement, an external command or a journal entry.
You create prompts from the Prompt Definitions window. To open the Prompt Definitions window, click on the Prompt Definitions button:
The Prompt Definitions window appears, shown in Figure 3-19.

To create a prompt, do one of the following:
The New Prompt window appears. Figure 3-20 shows the New Prompt window with Dynamic Choice selected.

To create a prompt, enter the following details in the window:
The prompt types available are:
The lower section of the window displays the fields for the selected prompt type.
A single dynamic choice prompt in a tool creates a popup menu. The menu is populated by the results of an interrogation of a database table.
Figure 3-20 shows an example of a New Prompt window with the Dynamic Choice type selected.
To complete the prompt details, complete these steps:
Step 2 Select a table within the selected database from the drop down list in the Table field.
Step 3 Use the drop down list next to the Show field to select a table field name.
The Show field defines the table field used to populate the prompt menu.
Step 4 Use the drop-down list next to the Assign field to select a table field name.
The Assign field defines the table field used to return a value to the SQL statement, external command or journal entry that contains the prompt.
Step 5 Enter a search condition in the Where field.
You can use the Filter Builder button to open the Filter Builder window to create this condition.
Step 6 Use the drop down list next to the Order By field to select a table field name.
This table field is used to order the items in the Prompt menu.
Step 7 Select the Ascending or Descending button to set the sort order for the table fields.
A single Fixed Choice prompt in a tool creates a popup menu. The menu is populated by the values that you enter into the list.
All of the values in the list appear in the popup menu.
To add a value to the list, enter the value and click the + button:
To remove a value from the list, select a value from the value frame and click the - button:.
The total number of characters in the prompts in the list cannot exceed 256. For longer lists use the Lookup prompt type.
The Float prompt creates a prompt window which accepts an entry value of any combination of 0-9 and one decimal point.
To complete the prompt details enter a default value to display.
The Integer prompt creates a prompt window which accepts an entry 0-9.
To complete the prompt details enter a default value to display.
A single Lookup prompt in a tool creates a popup menu. The menu is populated by the values in a file.
To complete the prompt details do one of the following:
The Password prompt creates a prompt window which accepts an entry of any character. The characters are hidden by an asterisk as they are entered.
The String prompt creates a prompt window which accepts one or more characters.
To complete the prompt details, enter a default value for the prompt to display.
The Time prompt creates a prompt window which accepts a time. The default display is the current time.
The prompt display depends on the type of the prompt and the number of prompts in the tool.
You can use the following types of prompt display:
In a multiple prompt window, the Dynamic Choice, Fixed Choice and Lookup prompt types appear as fields with drop down lists. The contents of the Prompt field appears as the title for the field.
To edit a selected prompt, do one of the following:
The Edit Prompt window appears. The Edit Prompt window is identical to the New Prompt window except that you cannot modify the Name field in the Edit Prompt window. It appears in gray.
To delete a selected prompt, do one of the following:
The prompt is removed from the Prompt Definitions window.
To rename a selected prompt, complete these steps:
The Rename Prompt window appears.
Step 2 Change the name and then click OK to confirm or Cancel.
If the name entered already exists, a warning message appears and you are prompted to enter an alternative name.
The Info Server uses a set of properties to control its behavior. These properties can only be changed by a super user.
The Properties tab of the Configuration Manager window allows you to edit the information contained in the Info Server properties files while the Info Server is running.
The Info Server's properties file is located in the following directory and file:
$OMNIHOME/etc/servername.props
where servername is the name of the Info Server.
![]() |
Note It is essential that you be familiar with the properties before modifying them. Incorrect configuration can severely impact the performance of the system. |
The Properties tab on the Configuration Manager window reads the properties from the Info Server and displays them for editing.
Figure 3-21 shows the Properties tab of the Configuration Manager window on a UNIX system.

The Toggle Property button becomes active when a property with a Boolean data value is selected:
The button toggles the property between Yes and No. When the boolean value is No the property icon is red. When the boolean value is Yes the property icon is green.
The Edit Value button becomes active when a property with an integer string data value is selected:
The Edit Value button opens a window within which you can enter a new integer.
The Save button saves the changes permanently to the .props file:
When you make a change it is applied instantly, but it is not automatically saved. If you shutdown and restart the Info Server, the original settings would be restored from the .props file.
The following section describe the functions of the properties displayed in the Properties tab of the Configuration Manager window.
This property controls whether or not users can connect to the Info Server. It should be enabled unless you wish to block new connections to the Info Server.
This property controls whether or not anyone can connect to the Info Server using the isql or nco_sql commands. Enable this property to allow this type of connection; disable this property to block isql or nco_sql connections.
This property controls whether or not changes to the automation system, that is to triggers or actions, should generate SystemWatch alerts, which 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.
This property controls whether or not changes to the configuration, that is changes made by the Configuration Manager window, should generate SystemWatch alerts, which 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.
This property controls whether or not changes to the user list, that is changes made by the user administration tool, should generate SystemWatch alerts, which 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.
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 to by Technical Support.
This property extends the functionality of the ReawakenClosed property. By enabling both ReawakenClosed and DeackOnReawaken, each time an alert is reawakened, the Acknowledged field is cleared, making the alert deacknowledged.
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 Info Server log. If it is disabled, the actions are executed without logging.
This property controls the level of messages that are generated by the Info Server. The default value of 0 generates no debug messages. The higher the value, the more debug messages are placed in the Info Server log. The highest debug level is 3.
This property controls whether or not the execution of triggers in automations should be logged. Enable this option to log the execution of triggers by the automation system in the Info Server log. If you disable this option, the triggers are executed without logging.
This property controls the level of detail sent to the log file after an alert is deleted.
A description of the details sent for each log level is shown in Table 3-13
.
| Level | Details logged |
|---|---|
<0 | No log output. |
0 | appid, sql |
1 | time, uid, appid, sql. |
2+ | time, uid, appid, sql + the contents of each alert deleted. |
Outputs for deleted alerts in the log file are stored so that they can be easily reinserted.
This property only functions when the Info Server has been started with the-delete command line option.
Sets the maximum size of the log file. The log size is entered in kilobytes.
When the log file deletelogname.log reaches the specified size, it is renamed deletelogname_old.log and a new log is started.
This property only functions when the Info Server has been started with the -delete command line option.
The results of a single delete command are never split between log files. Therefore log files may be larger than the specified size by the output from a single delete command.
This property controls the frequency of IDUC broadcasts to client tools. The value is in seconds. Reducing this value increases the refresh rate of desktop tools but increases the load on the Info Server. It is recommended that this value is left at the default of 60.
This property controls how often the Info Server checkpoints the database tables. The value is in seconds. The default is 300, which means that every 5 minutes the Info Server writes out the database tables and clears the transaction record files. Reducing this value increases the I/O load on the Info Server and its host system.
This property controls the maximum size that the log file is permitted to reach before the earliest entries are overwritten The size is in bytes. The default is 1024.
This property controls whether or not an alarm is generated when a process connects to the Info Server.
This property controls whether or not new alerts reawaken duplicate alerts that are closed in the Info Server. If you disable this option (the default), when a new alert arrives which matches an existing alert in the Info Server, the Tally field is incremented and the LastOccurrence time is updated from the new alert.
When the ReawakenClosed option is enabled two additional updates can be made:
Severity field is zero, the field is updated with the severity of the incoming alert.
Severity field is updated and the Info Server configuration option DeackOnReawaken is enabled the Acknowledge field is cleared.
This property controls the interval at which statistics are written to the statistics file. The value is in seconds. The default is 900.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Jun 13 15:30:39 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.