cc/td/doc/product/rtrmgmt/cwm/9_2_06
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

CWM Administrator

CWM Administrator

This chapter describes the functions of the CWM Administrator. CWM Admin provides a Topology Configurator, the System Error Log, and the Event Log. You use the Topology Configurator to provide IP address and other ID information about the nodes in your network. The error and event logs help you to monitor your network and the events that transpire.

Click the CWM Admin icon to launch the CWM Administrator application. When launched, the User Administration window is displayed, as shown in Figure 8-1.


Figure 8-1: User Administration Window


User Administration Window

The User Administration Window displays the System Error Log. This window provides a time-stamped list of each CWM process, along with a text message describing the process. The log can be cleared so you can watch current CWM messages. When you close the window and re-open it, all messages are displayed again.

Topology Configurator

To launch the Topology Configurator, enter configurator & on a shell's command line where Cisco WAN Manager 9.2 is installed.

Before using the Topology Configurator, you must edit the Topod.conf file located in directory /usr/users/svplus/config to disable automatic unique node ID generation. The third line of Topod.conf describes the next line as the Auto Node Id Generation flag. On line four, change the TRUE to FALSE to disable automatic node ID generation.

The Topology Configurator window is displayed as shown in Figure 8-2.


Figure 8-2: Topology Configurator


Click the Stand Alone button to change the view of the Topology Configurator to manage Stand Alone MGX 8850 nodes, as shown in Figure 8-3.


Figure 8-3: Topology Configurator (Stand Alone)


Only one instance of the Topology Configurator should be used at a time for performing any of the following operations. CWM provides tools that generate a unique node ID, but if multiple sessions of Topology Configurator are used at the same time, problems will occur.

Changes made using the Topology Configurator are not saved in the nodes.conf file until you press the Apply button. If the Cancel button is pressed, no changes will be made to the nodes.conf file.

nodes.conf File

The Topology Configurator is the only way you should display or edit the contents of the nodes.conf file. The nodes.conf file is created and saved in the /usr/users/svplus/config directory.

Configuring Stand Alone Nodes

You use the Topology Configurator to add new stand alone nodes or to modify or delete existing stand alone nodes.

Adding New Stand Alone Nodes

To add a new stand alone node, complete the following steps:

Step 1 Launch the Topology Configurator by entering configurator from a command line of the CWM station through which the new node is to be added, then click on Stand Alone.

Any existing information is displayed in the top panel of the Topology Configurator window labeled Stand Alone Node Information.

Step 2 In the Edit panel of the Topology Configurator, enter the new node name, the node ID, the IP address in the appropriate fields.

Step 3 Click on the browse button to select the model number of the stand alone node you are adding.

Step 4 Press the Add button.

The new information is displayed in the top panel of the Topology Configurator window labeled Stand Alone Node Information.

Step 5 Press the Apply button to save the new information to the /usr/users/svplus/config/nodes.conf file.

Step 6 Copy the nodes.conf file from the CWM station to which any new nodes have been added to all the other CWM stations connected to the same network.

The copy operation can be done while CWM is running on the destination CWM station. Be sure to use binary mode if the copy operation is done using FTP.

Step 7 On the destination workstation, launch the Topology Configurator and ensure that it displays all of the nodes to verify that the nodes.conf file was copied properly.

Step 8 Add the new node or nodes to the network.

When a new node is reported, CWM looks for the Node ID in the nodes.conf file. CWM rejects the node and issues a warning message if the Node ID is not found in the nodes.conf file.

Deleting Nodes

You can delete a node, complete the following steps:

Step 1 Launch the Topology Configurator by entering configurator from a command line of the CWM station.

Step 2 Click Stand Alone to display any existing Stand Alone Node Information.

Step 3 Select the node to delete by double-clicking on it in the Stand Alone Node Information panel.

The node ID information is displayed in the Edit field of the Topology Configurator.

Step 4 Make any changes and click the Delete button.

Step 5 Click Apply to save your changes.

Step 6 Copy the modified nodes.conf file from the CWM station to all the other CWM stations connected to the same network.

Modifying a Node

To modify a node, complete the following steps:

Step 1 Launch the Topology Configurator by entering configurator from a command line of the CWM station.

Step 2 Click Stand Alone to display any existing Stand Alone Node Information.

Step 3 Select the node to modify by double-clicking on it in the Stand Alone Node Information panel.

The node ID information is displayed in the Edit field of the Topology Configurator.

Step 4 Make any changes and click the Modify button.

Step 5 Copy the modified nodes.conf file from the CWM station to all the other CWM stations connected to the same network.

Step 6 Change the node name in the network.

Error Log Administration

The CWM System Error Log is displayed in the User Administration window. To display this window, select the CWM Admin button from the CWM Desktop window.

This window provides a time-stamped list of each CWM process, along with a text message describing the process. The log can be cleared so you can watch current CWM messages. When you close the window and re-open it, all of the previously cleared messages are again displayed.


Figure 8-4: User Administration Window


Event Log

The CWM Event Log displays descriptions of network- and operator-generated occurrences. This log can be viewed only in an HP OpenView window.

Event Categories

When you start an OpenView session, two windows are displayed, the OpenView Root window, which displays the Cisco CWM Network icon, and the Event Categories window, shown in Figure 8-5.


Figure 8-5: Event Categories Window


This window categorizes events for the Event Log display. Click on the square button adjacent to a category to display the Event Browser window for all events belonging to the selected category.

The color of the button indicates the level of severity of the worst case among the events listed in that category.

You can also display the Event Browser window for all events by selecting the Events option from the OpenView window's Fault menu.


Figure 8-6: Events Browser Window


Information is displayed in the All Events Browser window in the following columns.

Ack

When you click on an entry in the Severity column, a check mark is placed in the Ack column for that row, as a reminder you have acknowledged the severity of the message.

Severity

This column displays the severity of the event. Severity values are: critical, major, minor, warning, and normal. You can modify event severity by selecting the Action menu's Assign Severity option.

Date/Time

This column displays the day of the week, the calendar date, and the time of day the event occurred.

Source

This column displays the source of the event.

Message

This column displays a description of the event.

The Events Browser window has the following menu options:

File---Save

Select this option to display a submenu with the following options:

Each of these options opens a window which allows you to name the file to which the data is saved. The Messages pane reports back the results of the save operation.


Figure 8-7: Save... Window


Enter a valid path and file name in the File Name field then click on the Save button to save the events.

Click on the Close button to dismiss this window without taking any further action.

File---Save Browser State

Select this option to save the current set of undeleted events to a file so the next time a restore operation is performed, the same set of events (plus any new events) are loaded.

File---Restore Browser State

Select this option to reload the set of events saved when you last chose the Save Browser State option; or by either a map change or an exit of xnmevents (assuming the session was not read-only). The Browser displays this saved set of events ---including any events you may have deleted in the interim---plus any new events that have occurred. This operation is useful when you accidently deleted an event, or you performed a Reload Event Log operation and you want to restore the state of your Event Browser.

File---Reload Event Log

Select this option to display a submenu with the following choices:

File---Close

Select this option to close the Events Browser window.

Action---Highlight Source on Map Menu

Select this option to highlight the source of selected events in the Network Topology window.

Action---Acknowledge

Select this option to display a submenu with the following choices:

Action---UnAcknowledge

Select this option to display a submenu with the following choices:

Action---Delete

Select this option to display a submenu with the following choices:

Action---Configure Event

Select this option to display the Event Configuration window, which allows you to manage event details (add, edit, and other operations). This window is described elsewhere in this chapter.

Action---Assign Category

Select one or more events in the Events Browser window, then select this option to display the Assign Category window. This window allows you to change the category to which the selected events belong.


Figure 8-8: Assign Category Window


Action---Assign Severity

Select one or more events in the Events Browser window, then select this option to assign one of the following severity levels to the selected events:

Action---Additional Actions Menu

Select this option to display the Additional Actions window. This window allows you to pipe selected events into user-written shell commands via standard input.


Figure 8-9: Additional Actions Window


Select a button from the Scope of Action group (choose whether you want to perform an action on the selected events in the Events Browser window, all events meeting the current filter conditions, all acknowledged events displayed in the Events Browser window, all unacknowledged events displayed in the Events Browser window, or all events in the category.

Select an action from the list in the Action pane, then click on either the OK or Apply button. When you click on the OK button, the Additional Actions window is dismissed. When you click on the Apply button, the action is performed and the window remains displayed.

Select an action from the list then click on the Describe button to display an information window explaining the action, or click on the Help button to display an OpenView help topic for the selected action.

View---Describe Event

Select this option to display the Describe Event window, with a detailed explanation of the currently selected event.


Figure 8-10: Describe Event Window


View---Set Filters

Select this option to set the filter conditions which determine which events are listed in the Event Browser window.


Figure 8-11: Set Filters Window


View---Clear Filters

Select this option to restore the filter conditions to their default values.

Event Configuration Window

To configure an event, select it in the Event Browser window, then select the Action menu's Configure Event option. The Event Configuration Window is displayed. Use this window's menu options to access the event configuration tools.


Figure 8-12: Event Configuration Window


File---Save

Select this option to save any changes you have made using the Event Configuration window. This option is disabled when you have not made any changes.

File---Close

Select this option to close the Event Configuration window. When you have made changes in the Event Configuration window and have not used the File menu's Save option, your changes are lost.

Edit---Add

Select this option to display a submenu with the following choices:


Figure 8-13: Add Event Window


Enter data for the event in the medium grey fields, then click on the OK button. (The event record is not saved until you select the Save option from the Event Browser's File menu.)

Edit---Delete

Select this option to display a submenu with the following choices:

Edit---Modify Event

Select this option to display the Modify Event Window for the selected event in the Event Configuration window's Event Identification pane. The Modify Event Window is the same as the Add and Copy Event windows, except all of its data fields are filled in with data for the selected event.

Edit---Copy Event

Select this option to display the Copy Event Window. This window is the same as that used for the Add and Modify Event windows; the data fields are filled with data for the selected event in the Event Configuration window, except for the Event Name. This field is blank. You should assign the event a unique name so as to save it as a copy of the selected event.

Edit---Describe Event

Select this option to display the Describe Event window. This window displays information about the event selected in the Event Configuration window's Event Identification pane.


Figure 8-14: Describe Event Window


Edit---Configure

Select this option to display a submenu with the following choices:


Figure 8-15: Event Configuration: Event Categories Window



Figure 8-16: Event Configuration: Additional Actions Window


View---Sort

Select this option to display a submenu with the following choices:

View---Event Identifiers

Select this option to display a submenu with the following choices:

Events Defined

Internally, event descriptions are generated as a result of trap information, which transpires between the network management system and the network agents. These traps are controlled by Simple Network Management Protocol (SNMP) processes.

An SNMP agent is software capable of answering valid queries from an SNMP station (such as your CWM workstation), about information defined in the Management Information Base (MIB). A network device that provides information about the MIB to CWM, has an SNMP agent.

CWM and the SNMP agents exchange messages over the network's Transport Layer protocol. SNMP conducts five valid types of messaging:

Get-Request

Used by CWM to retrieve information from network devices with SNMP agents.

Get-Response

Response by a network agent to the Get-Request message. The response typically includes system information such as the name of the system, how long the system has been running, and the number of network interfaces on the system.

Get-Next-Request

Used with Get-Request, when compiling the list of objects, to ask for the next object in the table.

Set-Request

Enables remote configuration of parameters on a device.

Trap

An unsolicited message by an SNMP agent to CWM. Trap messages inform the server about the occurrence of a specific events.

The CWM SNMP traps are enhanced by a Robust Trap Mechanism (RTM) to ensure detection and retrieval of missed traps. With RTM, CWM can maintain sequential tracking of traps from specific agents. CWM detects missed traps based on sequence numbers, and uploads the missing number from the agent using SNMP Get-Requests.


Note HP OpenView expects to receive SNMP traps only on port 162. Therefore, the RTM front end registers with the agent on a different pre-configured port (default: 2500) for receiving traps.

The MGX 8220 node reports the aggregate shelf alarm status. This is evident at the LED on the node which is affected by a specific new trap.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Nov 4 21:19:40 PST 1999
Copyright 1989-1999©Cisco Systems Inc.