cc/td/doc/product/rtrmgmt/cwparent/cw2snm
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

CiscoWorks Getting Started

CiscoWorks Getting Started

This chapter introduces you to some CiscoWorks applications and provides instructions on how to use them. It also contains an overview of how CiscoWorks functions with the SunNet Manager (SNM), HP OpenView, and NetView for AIX platforms. This chapter includes the following sections:

For detailed CiscoWorks application information, refer to the specific section in this guide.

Learning to Use CiscoWorks

There are several tasks you must perform in order to use your CiscoWorks applications. For an overview and related procedures on these tasks, refer to the following platform-specific task list, as appropriate.

SunNet Manager Post-Installation Tasks

Perform the following tasks before using the CiscoWorks application on SunNet Manager:


  1. Run the SunNet Manager (SNM) Discover tool to create an SNM database and a network map with network devices. For more information, refer to the section, "Running the SNM Discover Tool." For detailed information, refer to the SunNet Manager 2.0 User's Guide.

  2. Use the SNM Change Type command to change appropriate SNM devices to Cisco devices. See the section "Identifying Cisco Devices for CiscoWorks on your SNM Map."

  3. Use the CiscoWorks Sync w/Sybase application to synchronize the SNM database with the Sybase database. See the section "Synchronizing the SNM Database with Sybase."

  4. Learn to display or use some basic CiscoWorks applications. See the section "Quick Tutorial on Using CiscoWorks on SNM."

For more details on performing these tasks, refer to the corresponding sections. Before performing the exercises in this chapter, you should be familiar with the SunNet Manager (SNM) Console window and know how to access the menu items in the Console window.

HP OpenView Post-Installation Tasks

Perform the following tasks before using the CiscoWorks application on HP OpenView:


  1. Run the HP OpenView Manage Objects command to discover IP devices on your network map. For more information, see the following section, "Running the Manage Objects Command on HP OpenView." For detailed information, refer to the HP OpenView User's Guide.

  2. Create other network maps and submaps, and add the appropriate devices, as your needs determine. For example, if you want to add a Cisco 7000 to your new network map, perform the following steps:
You see the Add Object Palette.
The Cisco 7000 symbol is copied into the map and you see the Add Object window.

  1. Use the HP OpenView Change Symbol Type command to change appropriate generic devices to Cisco devices. See the section "Identifying Cisco Devices for CiscoWorks on HP OpenView."

  2. Use the CiscoWorks Sync w/Sybase application to synchronize the HP OpenView database with the Sybase database. See the section "Synchronizing the HP OpenView Database with Sybase."

  3. Learn to display or use some basic CiscoWorks applications. See the section "Quick Tutorial on Using CiscoWorks on HP OpenView."

Before performing the exercises in this chapter, you should be familiar with the HP OpenView Console window and know how to access the menu items in the Console window.

NetView for AIX Post-Installation Tasks

Perform the following tasks before using the CiscoWorks application on NetView for AIX:


  1. Run the NetView Manage Objects command to discover IP devices on your network map.

    For more information, see the following section, "Running the Manage Objects Command on NetView for AIX." For detailed information, refer to the NetView User's Guide. If you have a network map or database from another platform you want to transfer, contact your IBM support representative for assistance.



  2. Create other network maps and submaps, and add the appropriate devices, as your needs determine. For example, if you want to add a Cisco 7000 to your new network map, perform the following steps:
You see the Add Object Palette.
The Cisco 7000 symbol is copied into the map and you see the Add Object window.

  1. Use the Change Symbol Type command to change appropriate generic devices to Cisco devices. See the section "Identifying Cisco Devices for CiscoWorks."

  2. Use the CiscoWorks Sync w/Sybase application to synchronize the NetView for AIX database with the Sybase database. See the section "Synchronizing the NetView for AIX Database with Sybase."

  3. Learn to display or use some basic CiscoWorks applications. See the section "Quick Tutorial on Using CiscoWorks on NetView for AIX."

Before performing the exercises in this chapter, you should be familiar with the NetView for AIX main window and know how to access the menu items from this window.

Getting Started with CiscoWorks on SNM

The following sections provide detailed information on the SNM post-installation tasks and contain an overview of how CiscoWorks functions with the SNM network management platform.

The following sections are discussed:

For detailed information on using the CiscoWorks applications, refer to the appropriate sections in this guide.

Starting CiscoWorks on SNM

This section briefly discusses how to start the SNM Console in order to access CiscoWorks. For a more detailed description and options, refer to the SunNet Manager 2.0 User's Guide.

You can use several different commands to start the SNM Console. However, you must be running Open Windows.


Note Do not use the following commands until you install SNM in the default installation directory.

Step 1 To start the SNM Console initially (when there is no database present) or when you want to bring up the last map file, enter the following:

If problems occur, your PATH environment variable might not include a path to SNM executables. You can enter a fully qualified path. In the following example, /usr/snm/bin is the path to the executables:


Step 2 To load a database map file (in ASCII format) into the SNM Console, select File>Load.

Caution Using the snm -i command, described next, will cause the existing SNM database to be lost if you have not saved it.

Step 3 To start the SNM Console enter one of the the following:

% snm -i
% snm <map_name>

For more information on starting the SNM Console or troubleshooting problems with startup, refer to the SunNet Manager 2.0 User's Guide.

Learning about Other CiscoWorks Applications on SNM

This section briefly outlines the steps you must complete in SNM before continuing with CiscoWorks tasks. For instructions on using specific CiscoWorks applications, refer to the appropriate section in this guide.

Follow these steps to learn about CiscoWorks applications that use the Sybase database:

Step 1 Start SNM (if not started already).

Refer to the section "Starting CiscoWorks on SNM" earlier in this chapter to learn how to start SNM.


Step 2 Access the Security Manager application to turn on authentication checking and provide users and groups access privileges to CiscoWorks applications.

For more information, refer to Chapter 7, "Setting Up Domains and Securing Applications."


Step 3 Set up your SNM run-time database using SNM Discover or manually create devices using the SNM Create command.

For SNM Discover information, refer to the section "Getting Started with CiscoWorks on SNM" or to the SNM documentation.


Step 4 Use Sync w/Sybase to synchronize SNM database devices with the CiscoWorks Sybase database.

If you are adding individual devices, use the CiscoWorks Device Management application, the AutoInstall Manager, or the Glyph menu Sync w/Sybase application to add device data to the database. For information on the AutoInstall Manager, refer to Chapter 5, "Managing Cisco Device Configurations." For Sync w/Sybase and Device Management application information, refer to Chapter 6, "Device Management."



Note The Sync w/Sybase application synchronizes, or adds, devices that exist in the SNM database to the CiscoWorks database. The Sync w/SNM tool, located within Sync w/Sybase, allows you to add devices from the CiscoWorks database to the SNM database. Alternatively, you can add devices created in CiscoWorks by manually adding them using the Create command in SNM or the Initialize command in Device Management.

Step 5 Use the CiscoWorks applications and SNM tools to help you monitor and manage your network activity.

Table 2-1 lists some general network management tasks and associates the task with its responsible software application. Use this table to determine which documentation set (CiscoWorks or SNM) to use if you have questions or need information. The X indicates that this information is located in the SNM manual set for the tool or application.



CiscoWorks Versus SNM Task Descriptions
Task SNM CiscoWorks
Starting SNM Console X
Using Discover X
Traversing your network map (run-time database) X
Creating or finding elements or element properties X Device Mgmt
Modifying or changing elements or element properties X Device Mgmt
Moving or connecting elements (devices) X
Copying or deleting elements (devices) X Device Mgmt
Saving your network map (run-time database) X
Using SNM applications (such as Results Browser and Results Grapher) X
Configuring OPEN LOOK graphical interface standards (such as window manipulation and mouse settings) X
Modifying a graph display X
Printing graphs, windows, or text files X
Changing the state of a glyph X
Specifying an event (condition of notification) X Device Monitor
Checking the cause of an event X Log Manager
Changing how glyph state changes propagate X
Viewing or changing the status of requests X
Viewing error and traps X Log Manager
Managing SNMP devices X All CiscoWorks applications

CiscoWorks Use of SNM Tools

CiscoWorks uses two SNM tools: the Result Browser and Grapher. Following is a brief description of each tool and how it is used by CiscoWorks:

For example, the CiscoWorks Polling Summary application uses the Results Browser to display query reports on polled device groups. You can display report data or send this data to the SNM Grapher.

For more detailed information on the Results Browser and Grapher, refer to your SNM documentation.

Running the SNM Discover Tool

Most CiscoWorks applications require a database of network devices. They also require a network map that contains these network devices.

SNM provides the Discover tool, which enables you to find the devices in the primary network to which your system is attached. Use the Discover tool to create a view (map) of your network and a run-time database for SNM. If you did not install the SNM software in the /usr/snm directory, you must set the environment variable for SNMHOME as described in the SunNet Manager 2.0 User's Guide.


Note The amount of time taken by the Discover tool to find all the devices on your network depends on the size of your subnet and the number of devices attached to it.

To run the Discover tool, perform the following steps:

Step 1 At the UNIX prompt, display the SNM Console by entering the following command:

The SNM Console window appears.


Step 2 Select Tools>Discover.

The SNM Discover Program window appears, prompting you to enter your superuser password.


Step 3 Enter your superuser password.

The Discover tool begins to construct views of the network. When the Discover tool completes the process, networks appear in the form of cloud glyphs, and devices appear in the form of workstation icons.


Step 4 To save the database of devices that you created, select File>Save.

For detailed information on how to run the Discover tool, refer to the SunNet Manager 2.0 User's Guide. To add devices to your network map after CiscoWorks installation, you can use any of the following applications: Device Management, AutoInstall Manager, or Sync w/Sybase. For more information adding devices after a CiscoWorks installation, refer to Chapter 6, "Device Management."


Identifying Cisco Devices for CiscoWorks on your SNM Map

Network devices that are discovered by the Discover tool exist as generic devices. You must identify them as Cisco devices to take advantage of CiscoWorks functionality.

To use the Change Type command to change a device from its generic status to the status of a Cisco device, perform the following steps:

Step 1 In the SNM Console window, use the mouse to point to a Cisco device then press the right mouse button.

The Glyph menu for the device appears. It is similar to the window in Figure 2-1.






Figure 2-1: Glyph Menu

Step 2 From the Glyph menu, select Change Type. Move the mouse to the right to display the drop-down menu, which lists device names and types.

Step 3 From the pull-down menu, select the device type that matches the one selected in your network map. For example, if the selected device in your network map is an AGS+, select Cisco-AGS+ from the pull-down menu.

The device appears as a Cisco device.


Step 4 Repeat steps 1 through 3 to identify other devices in the network map.

Step 5 Confirm that the selected devices have the correct Simple Network Management Protocol (SNMP) Community Strings by selecting Tools>Properties to access the SNM Properties Sheet application.

Synchronizing the SNM Database with Sybase

Two distinct databases are used in your work with CiscoWorks. The first is the Sybase relational database that is used by CiscoWorks applications to contain information about network devices, polling data, configuration details, and other data needed by each application. The second is the SNM run-time database that is used by the SunNet Manager to store information about the network. By synchronizing the Sybase database of CiscoWorks with the SNM database of the network platform, you build a complete resource of information.

SNM maintains a run-time database of devices that you discover by using the Discover tool. In order to use CiscoWorks applications, you must list devices in the Sybase database. The Sync w/Sybase application performs the following functions to enable you to use CiscoWorks applications:

Use the Sync w/Sybase application to synchronize the database information. The Sync w/Sybase application appears in the SNM Tools and Glyph menus. Run Sync w/Sybase from the Tools menu if you just initialized SNM, loaded your network map, and want to fully synchronize both databases. Run Sync w/Sybase from the Glyphs menu if you want to synchronize one or more specific devices. In both cases, the Sync w/Sybase window from which you can select other options displays. (See Figure 2-2.)


Figure 2-2: Sync w/Sybase

Depending on the number of database records and the information contained in each, database synchronization can be timely. To adjust for synchronization time and to meet special needs, select one of the following commands from the Options menu of the Sync w/Sybase window:

Copies the complete number and contents of database records from SNM to Sybase. These records might include information about the hardware platforms, community strings, and so forth. Allows you to choose the SNM device records that you want to add to Sybase. With the device name selected, click on Sync. To select contiguous items, hold down the Shift key and click additional device names or drag your mouse through a range of device names. To select discontiguous items, hold down the Control key and select individual device names.
Updates device records for the selected domain in the Sybase database. With the domain name selected, click on Sync.
Creates only entries in the Sybase table for devices listed in SNM--but excludes any specific information, such as inventory details or hardware platforms. Use this command if you need the databases to quickly recognize the devices contained in each. Later, if you decide that you want the complete device information available from SNM, you can copy it using another command from the Options menu of Sync w/Sybase, or the CiscoWorks Device Management application.
Copies only the device records from Sybase that did not yet exist in SNM into the SNM database. This is the inverse process of Devices (Network-->Sybase). When you use Device Management or the AutoInstall Manager application to add a device directly to Sybase, it will not be recognized by SNM until you use the Sybase-->NMS command. Nor will the device name be recognized if you added it directly to Sybase but not yet added the glyph to SNM. If you delete a device from SNM, however, it remains as a record in Sybase until you manually delete it from Sybase. A network cloud appears in your network map that lists the device records that were added from this process.
Displays a dialog box in which you can specify how much time can elapse before synchronization terminates and declares the device unreachable. You can also specify the default timeout using X Resource timeout Interval in your .Xdefaults file. The resource name is synchTimeout.

Figure 2-3 illustrates the relationship between the SNM database and the CiscoWorks database. Although you can directly add device names to either database, you must run the Sync w/Sybase application to confirm that the information about a particular device is correct in both places.


Figure 2-3: Database Creation for SNM and CiscoWorks

For more detailed information about the database and the Sync w/Sybase and Sync with SNM applications, refer to Chapter 6, "Device Management," later in this guide. For more information about the AutoInstall Manager application, refer to Chapter 5, "Managing Cisco Device Configurations," later in this guide.

After you finish running the Discover tool and creating a run-time database with network devices, follow these steps to run the Sync w/Sybase application:

Step 1 From the SNM Console window, select Tools>Sync w/Sybase.

The Sync w/Sybase window appears. (See Figure 2-4.)






Figure 2-4: Sync w/Sybase Window

The synchronization process takes from 3 minutes to over an hour, depending on the size of your network and the number of devices you are synchronizing.


You can stop the synchronization process at any time by selecting File>Exit. The devices that have been synchronized up to this time will be saved in the Sybase database.


Step 2 Select File>Exit to exit this window.

Quick Tutorial on Using CiscoWorks on SNM

This section provides steps for viewing or using four different CiscoWorks applications:

In order to use these applications, you must have at least two network devices in the Sybase database. Use the Sync w/Sybase application to add network devices to the Sybase database. After completing the exercises in this chapter, you will have a general idea of how to use CiscoWorks applications. For a detailed explanation of all the CiscoWorks applications, refer to the appropriate sections later in this guide.

Displaying Devices in the Devices Window

When the SNM database is synchronized with the Sybase database, the device information in the Sybase database can be displayed with the Device Management application by accessing the Devices window.

After you synchronized the SNM database with Sybase, perform the following steps to display the names of devices present in the Sybase database:

Step 1 Select Tools>Device Management.

The Device Management window appears, as shown in Figure 2-5.






Figure 2-5: Device Management Window

The Device Management window uses information stored in the database to display all the devices on the network, the interfaces of the device, and the names of contacts--people who are likely to have more information about a selected device.


Step 2 Select a device name to display the interfaces and contacts associated with that device.

Step 3 To add, modify, or delete interfaces or contacts for a specified device, select a corresponding item from the Edit menu.

Step 4 To modify, add, or delete a device, click on the corresponding button.

Step 5 To search for a specific device or range of devices, select Search>Find.

Step 6 Select File>Exit to exit the Devices window and the database.

Displaying the Path between Two Devices

The Path Tool application enables you to display the routing path between a source device and a destination device.

To graphically display the path between two devices, perform the following steps:

Step 1 In the SNM Console window, click on the SNMP device to display the Glyph menu.

Step 2 Select Tools>Path Tool from the Glyph menu.

A window similar to that in Figure 2-6 appears. The information about the source device is filled in.



Figure 2-6: Path Tool Window

Step 3 To select the destination device, click on the Select button beside the Path Destination field or enter the complete device name.

If you click on the button, the Device Selection window appears listing the devices in the SNM database. It is similar to the window shown in Figure 2-7.






Figure 2-7: Device Selection Window

Step 4 Click on the device that you want to specify as the destination and click on OK.

After the connection has been established, the device name appears in the Path Destination field in the Path Tool window.


Step 5 Click on OK to launch the Path Tool.

When the Path Tool is launched, a browser window (similar to the window shown in
Figure 2-8) appears, displaying the progress of the Path Tool as it makes each network hop from the source to the destination device.






Figure 2-8: Path Tool Window with Text

After the connection is established, the Path Tool window appears (similar to the window shown in Figure 2-9), displaying the path between the source and the destination device you specified.



Figure 2-9: Path Tool Window with a Graphic Display

Step 6 Select File>Exit to close the window.

Using Show Commands

The Show Commands application provides a unique interface to the Cisco devices on your network. It enables you to display device data, such as the status of a device or traffic information.

To use the Show Commands application to obtain data from a device, perform the following steps:

Step 1 In the SNM Console window, select a Cisco device.

Step 2 Select Tools>Show Commands from the Glyph menu.

The Show Commands window (similar to that shown in Figure 2-10) appears.



Figure 2-10: Show Commands Window

Step 3 Click on Interface to display the interfaces for the device.

The Show Interface window (similar to the window shown in Figure 2-11) appears.






Figure 2-11: Show Interface Window

Step 4 Select File>Close to exit from the Show Interface window.

The Show Commands window redisplays.


Step 5 Select File>Exit to exit from the Show Commands application.

Graphing MIB Objects

You can use SNM real-time graphs to observe real-time information by means of a two- or three-dimensional graph. CiscoWorks enables you to graph data about the health of your device and interface, and traffic information.

To display a real-time graph with information on the buffer characteristics for a device, perform the follow the steps:

Step 1 In the SNM Console window, select the SNMP device to display the Glyph menu.

Step 2 Select Tools>Real-Time Graphs from the Glyph menu.

The Real-Time Graphs window appears as shown in Figure 2-12.





Figure 2-12: Real-Time Graphs Window

Step 3 In the Router Health section, click on Buffer Space to display the buffer characteristics for the device.

The Results Grapher window appears briefly (see Figure 2-13) followed by the Real-Time Graphs Free Memory window, which displays the buffer space information in the form of a graph (see Figure 2-14).






Figure 2-13: Results Grapher Window




Figure 2-14: Real-Time Graphs Free Memory Window

Step 4 Click on the close box at the top left corner of the window to display a drop-down menu; then select Close to exit the window.

or


Select the item in the Results Grapher and click on Remove.


Step 5 Select File>Exit to exit from the Real-Time Graphs window.

CiscoWorks is integrated with the SunNet Manager (SNM) network management platform.


Note To understand the relationship between SNM and CiscoWorks, you should be familiar with SNM features such as the Create, Discover, and Change Type commands. For all SNM questions, refer to your SNM documentation.

During installation and configuration, CiscoWorks adds customized schema files with Cisco-specific device types, such as the Cisco AGS+, to the SNM schema files directory. CiscoWorks also adds its applications to the SNM Tools and Glyph menus.


Note Familiarize yourself with the standards and conventions used by OPEN LOOK. To familiarize yourself with OPEN LOOK standards, read the appendix on the OPEN LOOK interface in the SunNet Manager 2.0 Reference Guide. CiscoWorks supports these standards for all its graphical-user-interface components, such as using the mouse, opening windows and menus, and manipulating windows and icons.

It is important that you understand the SNM environment and how you can use SNM in conjunction with CiscoWorks. To answer your SNM network management questions, refer to the SNM documentation.

SNM Processes That Affect CiscoWorks

Some processes in SNM affect how CiscoWorks runs, depending on their configuration in SNM. As you continue to work with SNM processes and CiscoWorks, consider the following conditions in which the two environments coexist:

One important option you may want to consider is to customize your system to automatically receive information about device status. To set this option, you must open the Console Properties window and enable the SNM Automatic Management feature, as described in the SunNet Manager 2.0 Reference Guide.
Especially important is the SNM Change Type command on the SNM Glyph menu. The Change Type command enables you to change the device type. You might need to use this command if you used the SNM Discover tool, and SNM incorrectly classifies the element type of a device. You must classify device types accurately to their specific product names or product types because availability and correct operation of many CiscoWorks applications depends on the correct classification of the device type.

Setting Environment Variables on SNM

To use SNM and CiscoWorks, you must set the following environment variables:

Normally, you should set these variables before installing CiscoWorks. For information on setting environment variables, refer to the CiscoWorks administration and installation guide.

Getting Started with CiscoWorks on HP OpenView

The following sections provide detailed information on the HP OpenView post-installation tasks and contain an overview of how CiscoWorks functions on the HP OpenView network management platform.

The following topics are discussed:

Starting CiscoWorks on HP OpenView

This section briefly discusses how to start the HP OpenView Console in order to access CiscoWorks. You can use several different commands to start the HP OpenView Console. However, you must be running an X window manager, such as Motif.


Note Do not use the following commands until you install HP OpenView in the default installation directory.

Step 1 To start the HP OpenView Console initially (when there is no database present) or when you want to bring up the last map file, enter the following:

If problems occur, your PATH environment variable might not include a path to HP OpenView executables. You can enter a fully qualified path. In the following example, /usr/OV/bin is the path to the executables:


Step 2 To load a database map file into the HP OpenView Console, select File>Open/List Maps.

Step 3 To start the HP OpenView Console enter one of the the following:

% ovw -i
If you have not saved your map, this command will delete it.
% ovw - map <map_name>

For more information on starting the HP OpenView Console or troubleshooting problems with startup, refer to the HP OpenView 2.0 User's Guide.

Learning about Other CiscoWorks Applications on HP OpenView

This section briefly outlines the steps you must complete in HP OpenView before continuing with CiscoWorks tasks. For instructions on using specific CiscoWorks applications, refer to the appropriate sections in this guide.

Follow these steps to learn about CiscoWorks applications that use the Sybase database:

Step 1 Start HP OpenView (if not started already).

Refer to the section "GUI and Menu Structure of CiscoWorks" later in this chapter to learn how to start HP OpenView.


Step 2 Access the Security Manager application to turn on authentication checking and provide users and groups access privileges to CiscoWorks applications.

For more information, refer to Chapter 7, "Setting Up Domains and Securing Applications."


Step 3 Set up your HP OpenView run-time database using the HP OpenView Manage Objects command.

For information on the HP OpenView Manage Objects command, refer to the section "Getting Started with CiscoWorks on HP OpenView" or to the HP OpenView documentation.


Step 4 Use Sync w/Sybase to synchronize HP OpenView database devices with the CiscoWorks Sybase database.

If you are adding individual devices, use the CiscoWorks Device Management application, the AutoInstall Manager, the Change Symbol Type menu, or Sync w/Sybase application to add device data to the database. For information on the AutoInstall Manager, refer to Chapter 5, "Managing Cisco Device Configurations." For Sync w/Sybase and Device Management application information, refer to Chapter 6, "Device Management."



Note The Sync w/Sybase application synchronizes, or adds, devices that exist in the HP OpenView database to the CiscoWorks database. The Sync w/NMS command, located within Sync w/Sybase, allows you to add devices from the CiscoWorks database to the HP OpenView database. Alternatively, you can add devices created in CiscoWorks by manually adding them using the Create command in HP OpenView or the Initialize command in Device Management.

Step 5 Use the CiscoWorks applications and HP OpenView tools to help you monitor and manage your network activity.

Table 2-2 lists some general network management tasks and associates the task with its responsible software application. Use this table to determine which documentation set (CiscoWorks or HP OpenView) to use if you have questions or need information. The X indicates that this information is located in the HP OpenView manual set for the tool or application.



CiscoWorks Versus HP OpenView Task Descriptions
Task HP OpenView CiscoWorks
Starting HP OpenView Console X
Using Manage Objects command X
Traversing your network map (run-time database) X
Creating or finding elements or element properties X Device Mgmt
Modifying or changing elements or element properties X Device Mgmt
Moving or connecting elements (devices) X
Copying or deleting elements (devices) X Device Mgmt
Saving your network map (run-time database) X
Using HP OpenView applications (such as Graph Collected Data: SNMP) X
Modifying a graph display X
Printing graphs, windows, or text files X
Changing the symbol type X
Specifying an event (condition of notification) X Device Monitor (SNM only)
Checking the cause of an event X Log Manager
Changing how symbol type changes propagate X
Viewing or changing the status of requests X
Viewing error and traps X Log Manager
Managing HP OpenView devices X All CiscoWorks applications

Overview of CiscoWorks on HP OpenView

CiscoWorks is integrated with the HP OpenView network management platform.


Note To understand the relationship between HP OpenView and CiscoWorks, you should be familiar with HP OpenView features such as the Open/List Maps, Manage Objects, and Change Symbol Type commands. For all HP OpenView questions, refer to your HP OpenView documentation.

During installation and configuration, CiscoWorks adds customized schema files with Cisco-specific device types, such as the Cisco AGS+, to the HP OpenView schema files directory. CiscoWorks also adds its applications to the HP OpenView Tools and Glyph menus.


Note Familiarize yourself with the standards and conventions used by Motif. CiscoWorks supports these standards for all its graphical-user-interface components, such as using the mouse, opening windows and menus, and manipulating windows and icons.

It is important that you understand the HP OpenView environment and how you can use HP OpenView in conjunction with CiscoWorks. To answer your HP OpenView network management questions, refer to the HP OpenView documentation.

CiscoWorks Use of HP OpenView Tools

CiscoWorks uses one HP OpenView application, xnmgraph.The HP OpenView xnmgraph presents real-time or logged network data in graphical format. The xnmgraph application is used in the CiscoWorks Health Monitor and Real-Time Graphs applications to display data in graphical format. you can change the graph properties either with the pull-down menu on the graph window or by means of X resources in /usr/OV/appdefaults/xnm.

For more detailed information on the xnmgraph, refer to your HP OpenView documentation.

Running the Manage Objects Command on HP OpenView

Most CiscoWorks applications require a database of network devices. They also require a network map that contains these network devices.

HP OpenView automatically displays a default map, called IP Map, which displays all the IP devices connected to the HP OpenView workstation. The Manage Objects command enables you to find the devices in the primary network to which your system is attached. Use the Manage Objects command to view your network and a run-time database for HP OpenView.


Note The amount of time taken by the Manage Objects command to find devices on your network depends on the size of your subnet and the number of devices attached to it.

To run the Manage Objects command, perform the following steps:

Step 1 At the UNIX prompt, display the HP OpenView Console by entering the following command:

The HP OpenView Console window appears.


Step 2 Open the IP Internet default map.

Step 3 Click on a device symbol to select it.

Step 4 Select Options>Manage Objects.

The Manage Objects command begins to construct views of the network. When the Manage Objects command completes the process, you see a representation of the subnetwork that is joined to the selected device. The subnetworks appear in the form of lines connecting the selected device symbol to other device symbols.


Step 5 To save the database of devices that you created, select File>Save Map As.

For detailed information on how to run the Manage Objects command, refer to the HP OpenView User's Guide. To add devices to a network map after CiscoWorks installation, you can use any of the following applications: Device Management, AutoInstall Manager, or Sync w/Sybase. For more information adding devices after a CiscoWorks installation, refer to the appropriate sections within this guide.


Identifying Cisco Devices for CiscoWorks on HP OpenView

Network devices that are discovered by the Manage Objects command may exist as generic devices. You must identify them as Cisco devices to take advantage of CiscoWorks functionality.

To use the Change Symbol Type command to change a device from its generic status to the status of a Cisco device, perform the following steps:

Step 1 In the HP OpenView Console window, use the mouse to point to a Cisco device.

Step 2 then press the right mouse button or equivalent.

The symbol popup menu for the device appears. It is similar to the window in Figure 2-15.






Figure 2-15: Symbol Popup Menu

Step 3 From the Symbol Popup menu, select Change Symbol Type.

The Change Symbol Type window appears, as shown in Figure 2-16.



Figure 2-16: Change Symbol Type

Step 4 Select a symbol class that corresponds to the device you selected in the map. For example, if the selected device in your network map is a Cisco 7000, select Cisco Router because Cisco 7000 is a class of Cisco Router.

The Change Symbol Type window expands to show you the Symbol Subclasses for Class Cisco Router.


Step 5 Select a symbol subclass for the specified symbol. For example, if the selected device in your network map is a Cisco 7000, select the 7000 symbol.

Step 6 Repeat steps 1 through 4 to identify other devices in the network map.

Step 7 Confirm that the selected devices have the correct SNMP Community Strings by viewing the SNMP Configuration window. (From the HP OpenView menu bar, select Options>SNMP Configuration.)

Synchronizing the HP OpenView Database with Sybase

Two distinct databases are used in your work with CiscoWorks. The first is the Sybase relational database that is used by CiscoWorks applications to contain information about network devices, polling data, configuration details, and other data needed by each application. The second is the HP OpenView run-time database that is used by HP OpenView to store information about the network. By synchronizing the Sybase database of CiscoWorks with the HP OpenView database of the network platform, you build a complete resource of information.

HP OpenView maintains a run-time database of devices that you discover by using the Manage Objects command. In order to use CiscoWorks applications, you must list devices in the Sybase database. The Sync w/Sybase application performs the following functions to enable you to use CiscoWorks applications:

Use the Sync w/Sybase application to synchronize the database information. The Sync w/Sybase application appears in the CiscoWorks menu and HP OpenView symbol popup menus. Run Sync w/Sybase from the Misc. menu if you just initialized HP OpenView and want to fully synchronize both databases. Run Sync w/Sybase from the symbol popup menu if you want to synchronize one or more specific devices. In both cases, the Sync w/Sybase window from which you can select other options displays. (See Figure 2-17.)




Figure 2-17: Sync w/Sybase

Depending on the number of database records and the information contained in each, database synchronization can be timely. To adjust for synchronization time and to meet special needs, select one of the following commands from the Options menu of the Sync w/Sybase window:

Copies the complete number and contents of database records from HP OpenView to Sybase. These records might include information about the hardware platforms, community strings, and so forth. Allows you to choose the HP OpenView device records that you want to add to Sybase. With the device name selected, click on Sync. To select contiguous items, hold down the Shift key and click additional device names or drag your mouse through a range of device names. To select discontiguous items, hold down the Control key and select individual device names.
Updates device records for the selected domain in the Sybase database. With the domain name selected, click on Sync.
Creates only entries in the Sybase table for devices listed in HP OpenView--but excludes any specific information, such as inventory details or hardware platforms. Use this command if you need the databases to quickly recognize the devices contained in each. Later, if you decide that you want the complete device information available from HP OpenView, you can copy it using another command from the Options menu of Sync w/Sybase, or the CiscoWorks Device Management application.
Copies only the device records from Sybase that did not yet exist in HP OpenView into the HP OpenView database. This is the inverse process of Devices (Network-->Sybase). When you use Device Management or the AutoInstall Manager application to add a device directly to Sybase, the device name will not be recognized by HP OpenView until you use the Sybase-->NMS command. Nor will the device name be recognized if you added it directly to Sybase but not yet have added the symbol to HP OpenView. If you delete a device from HP OpenView, however, it remains as a record in Sybase until you manually delete it from Sybase. A network symbol (circle) appears in your network map that lists the device records that were added from this process.
Displays a dialog box in which you can specify how much time can elapse before synchronization terminates and declares the device unreachable. You can also specify the default timeout using X Resource timeout Interval in your .Xdefaults file. The resource name is synchTimeout.

Figure 2-18 illustrates the relationship between the HP OpenView database and the CiscoWorks database. Although you can directly add device names to either database, you must run the Sync w/Sybase application to confirm that the information about a particular device is correct in both places.


Figure 2-18: Database Creation for HP OpenView and CiscoWorks

For more detailed information about the database and the Sync w/Sybase and Sync with NMS applications, refer to Chapter 6, "Device Management.." For more information about the AutoInstall Manager application, refer to Chapter 5, "Managing Cisco Device Configurations."

After you finish creating a run-time database with network devices, follow these steps to run the Sync w/Sybase application:

Step 1 Select Misc>Sync w/Sybase.

The Sync w/Sybase window appears. (See Figure 2-19.)



Figure 2-19: Sync w/Sybase Window

The synchronization process takes from 3 minutes to over an hour, depending on the size of your network and the number of devices you are synchronizing.


You can stop the synchronization process at any time by selecting File>Exit. The devices that have been synchronized up to this time will be saved in the Sybase database.


Step 2 Select File>Exit to exit this window.

Quick Tutorial on Using CiscoWorks on HP OpenView

This section provides steps for viewing or using four different CiscoWorks applications:

In order to use these applications, you must have at least two network devices in the Sybase database. Use the Sync w/Sybase application to add network devices to the Sybase database. After completing the exercises in this chapter, you will have a general idea of how to use CiscoWorks applications. For a detailed explanation of all the CiscoWorks applications, refer to the appropriate sections in this guide.

Displaying Devices in the Devices Window

When the HP OpenView database is synchronized with the Sybase database, the device information in the Sybase database can be displayed with the Device Management application by accessing the Devices window.

After you synchronized the NMS database with Sybase, perform the following steps to display the names of devices present in the Sybase database:

Step 1 Select the Administer>Cisco Devices>Device Mgmt application.

The Device Management window appears, as shown in Figure 2-20.



Figure 2-20: Device Management Window

The Device Management window uses information stored in the database to display all the devices on the network, the interfaces of the device, and the names of contacts--people who are likely to have more information about a selected device.


Step 2 Select a device name to display the interfaces and contacts associated with that device.

Step 3 To add, modify, or delete interfaces or contacts for a specified device, select a corresponding item from the Edit menu.

Step 4 To modify, add, or delete a device, click on the corresponding button.

Step 5 To search for a specific device or range of devices, select Search>Find.

Step 6 Select File>Exit to exit the Devices window and the database.

Displaying the Path between Two Devices

The Path Tool application enables you to display the routing path between a source device and a destination device.

To graphically display the path between two devices, perform the following steps:

Step 1 From the HP OpenView menu bar, select Diagnose>Network Connectivity>Path Tool.

A window similar to that in Figure 2-21 appears. The information about the source device is filled in.



Figure 2-21: Path Tool Window

Step 2 To select the destination device, click on Select beside the Path Destination field or enter the complete device name.

If you click on the button, the Device Selection window appears listing the devices in the HP OpenView database. It is similar to the window shown in Figure 2-22.






Figure 2-22: Device Selection Window

Step 3 Click on the device that you want to specify as the destination and click on OK.

After the connection has been established, the device name appears in the Path Destination field in the Path Tool window.


Step 4 Click on OK to launch the Path Tool.

When the Path Tool is launched, a browser window (similar to the window shown in
Figure 2-23) appears, displaying the progress of the Path Tool as it makes each network hop from the source to the destination device.






Figure 2-23: Path Tool Window with Text

After the connection is established, the Path Tool window appears (similar to the window shown in Figure 2-24), displaying the path between the source and the destination device you specified.



Figure 2-24: Path Tool Window with a Graphic Display

Step 5 Select File>Exit to close the window.

Using Show Commands

The Show Commands application provides a unique interface to the Cisco devices on your network. It enables you to display device data, such as the status of a device or traffic information.

To use the Show Commands application to obtain data from a device, perform the following steps:

Step 1 In the HP OpenView Console window, select a Cisco device.

Step 2 Click the right mouse button or equivalent to select Diagnose>Show Commands.

The Show Commands window (similar to that shown in Figure 2-25) appears.



Figure 2-25: Show Commands Window

Step 3 Click on Interface to display the interfaces for the device.

The Show Interface window (similar to the window shown in Figure 2-26) appears.






Figure 2-26: Show Interface Window

Step 4 Select File>Close to exit from the Show Interface window.

The Show Commands window redisplays.


Step 5 Select File>Exit to exit from the Show Commands application.

Graphing MIB Objects

You can use CiscoWorks real-time graphs to observe real-time information by means of a two- or three-dimensional graph. CiscoWorks enables you to graph data about the health of your device and interface, and traffic information.

To display a real-time graph with information on the buffer characteristics for a device, perform the follow the steps:

Step 1 In the HP OpenView Console window, select a device.

Step 2 From the HP OpenView menu bar, select Plan>Real-Time Graphs.

The Real-Time Graphs window appears as shown in Figure 2-27.





Figure 2-27: Real-Time Graphs Window

Step 3 In the Router Health section, click on Buffer Space to display the buffer characteristics for the device.

The Real-Time Graphs Free Memory window displays containing the buffer space information in the form of a graph (see Figure 2-28).





Figure 2-28: Real-Time Graphs Free Memory Window

Step 4 Click on the close box at the top left corner of the window to display a drop-down menu; then select Close to exit the window.

Step 5 Select File>Exit to exit from the Real-Time Graphs window.

HP OpenView Processes That Affect CiscoWorks

Some processes in OpenView affect how CiscoWorks runs, depending on their configuration in OpenView. As you continue to work with OpenView processes and CiscoWorks, consider the following conditions in which the two environments coexist:

Especially important is the HP OpenView Change Symbol Type command on the HP OpenView symbol popup menu. The Change Symbol Type command enables you to change the device symbol type. You might need to use this command if you used the Manage Objects command, and HP OpenView assigned an incorrect symbol to the device. You must classify device types accurately to their specific product names or product types because availability and correct operation of many CiscoWorks applications depends on the correct classification of the device type.

Setting Environment Variables on HP OpenView

To use HP OpenView and CiscoWorks, you must set the following environment variables:

Normally, you should set these variables before installing CiscoWorks. For information on setting environment variables, refer to the CiscoWorks administration and installation guide.

Getting Started with CiscoWorks on NetView for AIX

The following sections provide detailed information on some post-installation tasks. It also contains an overview of how CiscoWorks functions on the NetView for AIX network management platform.

The following topics are discussed:

Starting CiscoWorks on NetView for AIX

This section briefly discusses how to start NetView for AIX in order to access CiscoWorks. You can use several different commands to start NetView for AIX. You must be running an X window manager, such as Motif to start NetView for AIX.


Note Do not use the following commands until you install NetView for AIX in the default installation directory.

There are three ways to start NetView for AIX:

If problems occur, your PATH environment variable might not include a path to NetView for AIX executables. To resolve this problem, try entering a fully qualified path, such as /usr/OV/bin/nv6000.

To load a network map file into the NetView for AIX main window, select File>Open/List Maps.

For more information on starting NetView for AIX or troubleshooting problems with startup, refer to the NetView for AIX User's Guide.

Learning about Other CiscoWorks Applications on NetView for AIX

This section briefly outlines the steps you must complete in NetView for AIX before continuing with CiscoWorks tasks. For instructions on using specific CiscoWorks applications, refer to the appropriate sections in this guide.

In order to use the CiscoWorks applications that use the Sybase database, follow these steps:

Step 1 Start NetView for AIX (if not started already).

Refer to the section "Starting CiscoWorks on NetView for AIX" to learn how to start NetView for AIX.


Step 2 Access the Security Manager application to turn on authentication checking and provide user and group access privileges to CiscoWorks applications.

For more information, refer to Chapter 7, "Setting Up Domains and Securing Applications," in your CiscoWorks User Guide.


Step 3 Set up your NetView for AIX run-time database using the NetView for AIX Manage Objects command.

For information on the NetView for AIX Manage Objects command, refer to the section "Getting Started with CiscoWorks on NetView for AIX" or to the NetView for AIX documentation.


Step 4 Use Sync w/Sybase to synchronize devices in NetView for AIX with the CiscoWorks Sybase database.

If you are adding individual devices, use the CiscoWorks Device Management application, the AutoInstall Manager, the Change Symbol Type command, or the Sync w/Sybase application to add device data to the database. For information on the AutoInstall Manager, refer to Chapter 5, "Managing Cisco Device Configurations." For Sync w/Sybase and Device Management application information, refer to Chapter 6, "Device Management."



Note The Devices (Network-->Sybase) command synchronizes, or adds, devices that exist in the NetView for AIX database to the CiscoWorks database. The Sybase-->Platform command, located within Sync w/Sybase, allows you to add devices from the CiscoWorks database to the NetView for AIX database. Alternatively, you can add devices created in CiscoWorks by manually adding them using the Create command in NetView for AIX or the Initialize command in Device Management.

Step 5 Use the CiscoWorks applications to help you manage your network activity.

Table 2-3 lists some general network management tasks and associates the task with its responsible CiscoWorks software application. Use this table to determine which documentation set (CiscoWorks or NetView for AIX) to use if you have questions or need information. The NA indicates that this information is not applicable to the CiscoWorks software or manuals and to refer to the NetView for AIX manual set. The X indicates that this information may be covered briefly in the CiscoWorks manual set, but may be a platform-specific task so should be referenced in your platform documentation.



CiscoWorks Task Descriptions
Task CiscoWorks
Starting NetView for AIX X
Using Manage Objects command X
Traversing your network map (run-time database) NA
Creating or finding elements or element properties Device Mgmt, Sync w/Sybase
Modifying or changing elements or element properties Device Mgmt
Moving or connecting elements (devices) NA
Copying or deleting elements (devices) Device Mgmt
Saving your network map (run-time database) NA
Using platform applications (such as Graph Collected Data: SNMP) NA
Modifying a graph display NA
Printing graphs, windows, or text files X
Changing the symbol type NA
Specifying an event (condition of notification) NA
Checking the cause of an event Log Manager
Changing how symbol type propagates NA
Viewing or changing the status of requests NA
Viewing errors and traps Log Manager
Managing NetView for AIX devices All CiscoWorks applications

Overview of CiscoWorks on NetView for AIX

CiscoWorks is integrated with the NetView for AIX network management platform.


Note To understand the relationship between NetView for AIX and CiscoWorks, you should be familiar with NetView for AIX features such as the Open/List Maps, Manage Objects, and Change Symbol Type commands. For all NetView for AIX questions, refer to your NetView for AIX documentation.

During installation and configuration, CiscoWorks adds customized router files with Cisco-specific device types, such as the Cisco AGS+, to the NetView for AIX /usr/OV/symbols directory. CiscoWorks also adds its applications to the NetView for AIX menu bar.


Note Familiarize yourself with the standards and conventions used by Motif. CiscoWorks supports these standards for all its graphical-user-interface components, such as using the mouse, opening windows and menus, and manipulating windows and icons.

CiscoWorks Use of NetView for AIX Tools

CiscoWorks uses the NetView for AIX grapher, xnmgraph, to present real-time or logged network data in graphical format. The xnmgraph application is used in the CiscoWorks Health Monitor and Real-Time Graphs applications to display data in graphical format. You can change the graph properties either with the pull-down menu on the graph window or using the X resources in
/usr/OV/appdefaults/xnm.

For more detailed information on xnmgraph, refer to your NetView for AIX documentation.

Running the Manage Objects Command on NetView for AIX

Most CiscoWorks applications require a database of network devices. They also require a network map that contains these network devices.

NetView for AIX automatically displays a default map, called IP Map, which displays all the IP devices connected to the NetView for AIX workstation. The Manage Objects command enables you to find the devices in the primary network to which your system is attached. Use the Manage Objects command to view your network and run-time database for NetView for AIX.


Note The time taken by the Manage Objects command to find devices on your network depends on the size of your subnetwork and the number of devices attached to it.

To run the Manage Objects command, perform the following steps:

Step 1 At the UNIX prompt, display NetView for AIX by entering the following command:

The NetView for AIX main window appears. (See Figure 1-5.)


Step 2 Open the IP Internet default map.

Step 3 Click on a device symbol to select it.

Step 4 Select Options>Manage Objects.

The Manage Objects command begins to construct views of the network. When the Manage Objects command completes the process, you see a representation of the subnetwork that is connected to the selected device. The subnetworks appear in the form of lines connecting the selected device symbol to other device symbols.


Step 5 To save the database of devices that you created, select File>Save Map As.

To add devices to a network map after CiscoWorks installation, you can use any of the following applications: Device Management, AutoInstall Manager, or Sync w/Sybase. For more information on adding devices after a CiscoWorks installation, refer to the appropriate sections within the CiscoWorks User Guide.


For detailed information on how to run the Manage Objects command, refer to the NetView for AIX User's Guide.


Identifying Cisco Devices for CiscoWorks

Network devices that are discovered by the Manage Objects command may exist as generic devices. You must identify them as Cisco devices to take advantage of CiscoWorks functionality.

To use the Change Symbol Type command to change a device from its generic status to the status of a Cisco device, perform the following steps:

Step 1 In the NetView for AIX main window, use the mouse to point to the device then press the right mouse button or equivalent.

Step 2 Select Edit>Change Symbol Type.

The Change Symbol Type window appears, as shown in Figure 2-29.






Figure 2-29: Change Symbol Type

Step 3 Select a symbol class that corresponds to the device you selected in the map. For example, if the selected device in your network map is a Cisco 7000, select Cisco Router because Cisco 7000 is a class of Cisco Router.

The Change Symbol Type window expands to show you the Symbol Subclasses for Class Cisco Router. All supported Cisco router classes appear in this panel in the Change Symbol Type window.


Step 4 Select a symbol subclass for the specified symbol. For example, if the selected device in your network map is a Cisco 7000, select the 7000 symbol.

Step 5 Repeat steps 1 through 4 to identify other devices in the network map.

Step 6 Confirm that the selected devices have the correct SNMP Community Strings by viewing the SNMP Configuration window. (From the NetView for AIX menu bar, select Options>SNMP Configuration.)

Synchronizing the NetView for AIX Database with Sybase

Two distinct databases are used in your work with CiscoWorks. The first is the Sybase relational database that is used by CiscoWorks applications to contain information about network devices, polling data, configuration details, and other data needed by each application. The second is the NetView for AIX run-time database that is used by NetView for AIX to store information about the network. By synchronizing the CiscoWorks Sybase database with the NetView for AIX database, you build a complete resource of information.

NetView for AIX maintains a run-time database of devices that you discover by using the Manage Objects command. In order to use CiscoWorks applications, you must include devices in the Sybase database. The Sync w/Sybase application performs the following functions to enable you to use CiscoWorks applications:

Use the Sync w/Sybase or Sync Selected applications to synchronize the database information. Both the Sync w/Sybase and Sync Selected applications appear in the Misc menu. Use Sync w/Sybase if you just initialized NetView for AIX and want to fully synchronize both databases. Use Sync Selected if you want to synchronize a specific device.




Figure 2-30: Sync w/Sybase

Depending on the number of database records and the information contained in each, database synchronization can be time-consuming. To adjust for synchronization time and to meet special needs, select one of the following commands from the Options menu of the Sync w/Sybase window: (See Figure 2-30.)

Copies the complete number and contents of database records from NetView for AIX to Sybase. These records might include information about the hardware platforms, community strings, and so forth. Allows you to choose the NetView for AIX device records that you want to add to Sybase. With the device name selected, click on the Sync button. To select contiguous items, hold down the Shift key and click additional device names or drag your mouse through a range of device names. To select discontiguous items, hold down the Control key and select individual device names.
Updates device records for the selected domain in the Sybase database. With the domain name selected, click on the Sync button.
Creates only entries in the Sybase table for devices listed in NetView for AIX--but excludes any specific information, such as inventory details or hardware platforms. Use this command if you need the databases to quickly recognize the devices contained in each. Later, if you decide that you want the complete device information available from NetView for AIX, you can copy it using another command from the Options menu of Sync w/Sybase, or the CiscoWorks Device Management application.
Copies only the device records from Sybase that did not yet exist in NetView for AIX into the NetView for AIX database. This is the inverse process of Devices (Network-->Sybase). When you use Device Management or the AutoInstall Manager application to add a device directly to Sybase, the device name will not be recognized by NetView for AIX until you use the
Sybase-->Platform command. Nor will the device name be recognized if you added it directly to Sybase but have not yet added the symbol to NetView for AIX. If you delete a device from NetView for AIX, however, it remains as a record in Sybase until you manually delete it from Sybase. A network symbol (circle) appears in your network map that lists the device records that were added from this process.
Displays a dialog box in which you can specify how much time can elapse before synchronization terminates and declares the device unreachable. You can also specify the default timeout using X Resource timeout Interval in your .Xdefaults file.

Use the Misc>Sync Selected option in the NetView for AIX menu to synchronize a specific device.

Figure 2-31 illustrates the relationship between the NetView for AIX database and the CiscoWorks database. Although you can directly add device names to either database, you must run the
Sync w/Sybase application to confirm that the information about a particular device is correct in both places.




Figure 2-31: Database Creation for NetView for AIX and CiscoWorks

For more detailed information about the database and the Sync w/Sybase and Sync Selected applications, refer to Chapter 6, "Device Management." For more information about the AutoInstall Manager application, refer to Chapter 5, "Managing Cisco Device Configurations."

After you finish creating a run-time database with network devices, follow these steps to run the Sync w/Sybase application:

Step 1 Select Misc>Sync w/Sybase.

The Sync w/Sybase window appears. (See Figure 2-30.)






Figure 2-32: Sync w/Sybase Window

The synchronization process takes from 3 minutes to over an hour, depending on the size of your network and the number of devices you are synchronizing.


You can stop the synchronization process at any time by selecting File>Exit. The devices that have been synchronized up to this time will be saved in the Sybase database.


Step 2 Select File>Exit to exit this window.

Quick Tutorial on Using CiscoWorks on NetView for AIX

This section provides steps for viewing or using four key CiscoWorks applications:

In order to use these applications, you must have at least two network devices in the Sybase database. Use the Sync w/Sybase application to add network devices to the Sybase database. After completing the exercises in this chapter, you will have a general idea of how to use CiscoWorks applications. For a detailed explanation of all the CiscoWorks applications, refer to the appropriate sections in this guide.

Displaying Devices in the Devices Window

When the Sybase database is synchronized with the NetView for AIX database, the device information in the Sybase database can be displayed with the Device Management application by accessing the Devices window.

After you synchronized the NetView for AIX database with Sybase, perform the following steps to display the names of devices present in the Sybase database:

Step 1 Select the Administer>CiscoWorks Devices>Device Mgmt application.

The Device Management window appears, as shown in Figure 2-33.


The Device Management window uses information stored in the database to display all the devices on the network, the interfaces of the device, and the names of contacts--people who are likely to have more information about a selected device.


You may use the Forms menu in the Device Management window to store administrative information such as contact personnel, location, vendor, and other information.






Figure 2-33: Device Management Window

Step 2 Select a device name to display the interfaces and contacts associated with that device.

Step 3 To add, modify, or delete interfaces or contacts for a specified device, select a corresponding item from the Edit menu.

Step 4 To modify, add, or delete a device, click on the corresponding button.

Step 5 To search for a specific device or range of devices, select Search>Find.

Step 6 Select File>Exit to exit the Devices window and the database.

Displaying the Path between Two Devices

The Path Tool application enables you to display the routing path between a source device and a destination device.

To graphically display the path between two devices, perform the following steps:

Step 1 In the NetView for AIX main window, click on a source device and select Diagnose>Network Connectivity>Path Tool.

A window similar to that in Figure 2-34 appears. If you did not select a device on the network map before selecting the menu item, the information about the source device is not filled in.






Figure 2-34: Path Tool Window

Step 2 To select the destination device, click on Select beside the Path Destination field or enter the complete device name.

If you click on the button, the Device Selection window appears listing the devices in the NetView for AIX database. It is similar to the window shown in Figure 2-35.






Figure 2-35: Device Selection Window

Step 3 Click on the device that you want to specify as the destination and click on the OK button.

After the connection has been established, the device name appears in the Path Destination field in the Path Tool window.


Step 4 Click on OK to launch the Path Tool.

When the Path Tool is launched, a browser window (similar to the window shown in
Figure 2-36) appears, displaying the progress of the Path Tool as it traces each network hop from the source to the destination device.






Figure 2-36: Path Tool Window with Text

After the connection is established, the Path Tool window appears (similar to the window shown in Figure 2-37), displaying the path between the source and the destination device you specified.






Figure 2-37: Path Tool Window with a Graphic Display

Step 5 Select File>Exit to close the window.

Using Show Commands

The Show Commands application provides a unique interface to the Cisco devices on your network. It enables you to display device data, such as the status of a device or traffic information.

To use the Show Commands application to obtain data from a device, perform the following steps:

Step 1 In the NetView for AIX main window, select a Cisco device.

Step 2 Click the right mouse button or equivalent to select Diagnose>Show Commands.

The Show Commands window (similar to that shown in Figure 2-38) appears.






Figure 2-38: Show Commands Window

Step 3 Click on Interface to display the interfaces for the device.

The Show Interface window (similar to the window shown in Figure 2-39) appears.






Figure 2-39: Show Interface Window

Step 4 Select File>Close to exit from the Show Interface window.

The Show Commands window redisplays.


Step 5 Select File>Exit to exit from the Show Commands application.

Graphing MIB Objects

You can use CiscoWorks real-time graphs to observe real-time information by means of a two-dimensional graph. CiscoWorks enables you to graph data about the health of your device and interface, and traffic information.

To display a real-time graph with information on the buffer characteristics for a device, perform the following the steps:

Step 1 In the NetView for AIX main window, select a device.

Step 2 From the NetView for AIX menu bar, select Monitor>Real-Time Graphs.

The Real-Time Graphs window appears as shown in Figure 2-40.





Figure 2-40: Real-Time Graphs Window

Step 3 In the Router Health section, click on Buffer Space to display the buffer characteristics for the device.

The Real-Time Graphs Free Memory window displays containing the buffer space information in the form of a graph. (See Figure 2-41.)





Figure 2-41: Real-Time Graphs Free Memory Window

Step 4 Click on the box at the top left corner of the window to display a drop-down menu; then select Close to exit the window.

Step 5 Select File>Exit to exit from the Real-Time Graphs window.

NetView for AIX Processes That Affect CiscoWorks

Some processes in NetView for AIX affect how CiscoWorks runs, depending on the processes configuration in NetView for AIX. As you continue to work with NetView for AIX processes and CiscoWorks, consider the following conditions in which the two environments coexist:

Especially important is the NetView for AIX Change Symbol Type command on the NetView for AIX Edit menu. The Change Symbol Type command enables you to change the device symbol type. You might need to use this command if you used the Manage Objects command, and NetView for AIX assigned an incorrect symbol to the device. You must classify device types accurately to their specific product names or product types because availability and correct operation of many CiscoWorks applications depends on the correct classification of the device type.
For a brief overview on how the NetView for AIX Manage Objects command is used, refer to the section "Running the Manage Objects Command on NetView for AIX," earlier in this chapter. For a detailed description of the NetView for AIX Manage Objects command, refer to your NetView for AIX User's Guide.

Setting Environment Variables on NetView for AIX

To use NetView for AIX and CiscoWorks, you must set the following environment variables:

Normally, you should set these variables before invoking NetView for AIX. For information on setting environment variables, refer to the CiscoWorks Administration and Installation Guide on NetView for AIX.

GUI and Menu Structure of CiscoWorks

CiscoWorks supports the Motif graphical user interface (GUI).


Note If a window component is grayed out, the option or feature is either inactive or unavailable. For example, on the Health Monitor window, if a protocol button is gray, that protocol is not activated on the selected device or the environmental interface card may not be present on the selected device.

When accessing the network management windows, keep the following in mind:

Menu Structure of CiscoWorks Windows

Most primary windows contain the following common menu options:

Some application windows contain other menu options. For information on these options, along with full-menu descriptions of each application, refer to the specific application for window descriptions.

File Menu

All primary windows contain a File menu. Figure 2-42 shows the opened File menu.




Figure 2-42: File Menu
Print Command

Each CiscoWorks primary window contains a Print command. There are two types of print options available in CiscoWorks applications. One option prints text displayed in a window using the lpr command. The other option prints a screen or window image using the NMS print utility. The CiscoWorks application you are in will determine the popup window that appears after you select the Print command.

When you use the network management platform print utility, you print the window on which the mouse pointer is resting. For example, when pointing to a menu bar (near the top of the window), your NMS print utility prints whatever is displayed on your monitor. When pointing to a browser, or text-displaying window inside a window, the print utility prints only the Browser window.

When you select Print on a window that accesses the lpr command, the Print Command window appears. (See Figure 2-43.) In NetView for AIX, a -d will appear in the Printer Name field.




Figure 2-43: Print Command Window

To print, enter the name of your printer, including any path designations, and click on OK. To close the window without printing, click on Cancel.

You can set up a default printer selection by setting the PRINTER environment variable before you start the NetView for AIX session. For example, in a C shell enter the following:

# setenv PRINTER printername

For the Korn Shell, enter the following:

# PRINTER=printername
# export PRINTER

Note When you print a color image on a black and white printer, the colors are printed in various shades of gray.
Exit Command

To exit from a primary application window, select File>Exit.

Exit closes the active window. If you exit from a primary window, you return to the NetView for AIX main window. If you exit from a secondary window, the primary window remains displayed. If multiple primary windows are opened, only the one where you selected Exit is closed; all other windows remain open and active until you select Exit on each of those primary windows.

Security Menu

The Security menu, shown in Figure 2-44, appears in the windows of CiscoWorks applications that use authentication-checking, a feature that allows an administrator to grant different levels of access privileges to CiscoWorks applications. Depending on whether the application governs a process or database function, you can use the menu commands to access another domain, to log in as another user, or learn what user privileges you have for a given CiscoWorks application.




Figure 2-44: Security Menu
Change Domain Command

The Change Domain command allows you to display, change to, and operate in another domain. A domain represents a logical group of devices. A device is any network entity that contains an SNMP agent. (Devices generally include routers, bridges, and communication servers.)

The Change Domain command is used by applications that work with devices listed in the Sybase database. Applications that support the Change Domain command include Path Tool and Device Polling. Changing domains may alter your privileges to an application because privileges are granted according to your group/domain association. In most cases however, when you access another domain, you can expect changes in privileges to the applications that manage the devices in that domain.

Change User Command

The Change User command allows you to log in under another user name. Use this command when you need the privileges of another user in order to access applications (like Configuration Management) that would otherwise be unavailable to you.

Privileges Command

The Privileges command allows you to display your current privileges for the specified CiscoWorks application. When you select the Privileges command, the User Privilege window appears, listing your application-specific privileges. (See Figure 2-45.)


Note An item in any CiscoWorks application that is grayed out represents an inactive or unavailable option or feature. If you need privileges beyond those defined by your user ID account, see your CiscoWorks administrator.




Figure 2-45: User Privilege Window

Help Menu

The Help menu provides options for viewing online help for the current application and its current version number. (See Figure 2-46.)


Figure 2-46: Help Menu
Help on Version

Use the Help on Version command from the Help menu to display the current version of the active CiscoWorks application. (See Figure 2-47.)


Figure 2-47: Version Window
Help on the Application

When you select On <application name>, a window similar to Figure 2-48 appears.




Figure 2-48: Help Window

Enter characters in the search string field. Then use the Search Forward and Search Reverse buttons to find your search string in the displayed text.

Using Command Buttons

The command buttons used in the Device Management application are described in this section. For more information on Device Management, refer to Chapter 6, "Device Management" in the CiscoWorks User Guide.

To view the command buttons, perform the following steps:

Step 1 Select Administer>CiscoWorks Devices>Device Mgmt.

The Device Management window appears. (See Figure 2-58.)






Figure 2-49: Device Management Window

The following command buttons appear along the bottom of the window:


Step 2 Click on New to open the Device Information Window. (See Figure 2-59.) When you click on the New button, you see panes for Device Details and Inventory Details and Administrative Details.


Note When you display information about a device that already exists, only the Device Details and Inventory Details panes are displayed. The Device Information Window still contains a pane for Administrative Details, but is displayed only when you select Options>Admin Details.




Figure 2-50: Device Information Window
Note Use care because adding data records to a related table may also result in the creation of a duplicate unwanted record in the primary or other window table. If this occurs, delete the duplicate record by selecting its name in the Device Management window and clicking on Delete.

Step 3 When you finish entering data in the Device Information window, click on OK. The data is saved to the database and displayed in the Device Management window.

With the Device Information window open, you can change the data in any field you wish. If you like, you can copy and paste data directly among windows or the fields within windows.


Step 4 When you finish modifying data about a particular device, click on Apply to save the changes.

Step 5 Select Options>Initialize to get the device information.


Note When you click on a device name in the Device Management window, the Interfaces and Contacts associated with that device appear in the remaining windows. Clicking on Modify always displays database fields belonging to the selected device name, even though a particular interface or contact name may also be selected.

GUI and Menu Structure of CiscoWorks

CiscoWorks supports the Motif graphical user interface (GUI).


Note If a window component is grayed out, the option or feature is either inactive or unavailable. For example, on the Health Monitor window, if a protocol button is gray, that protocol is not activated on the selected device.

When accessing the network management windows, keep the following in mind:

Menu Structure of CiscoWorks Windows

Most primary windows contain the following common menu options:

Some application windows contain other menu options. For information on these options, along with full-menu descriptions of each application, refer to the specific application for window descriptions.

File Menu

All primary windows contain a File menu. Figure 2-51 shows the opened File menu.


Figure 2-51: File Menu
Print Command

Each CiscoWorks primary window contains a Print command. There are two types of print options available in CiscoWorks applications. One option prints text displayed in a window using the lpr command. The other option prints a screen or window image using the NMS print utility. The CiscoWorks application you are in will determine the popup window that appears after you select the Print command.

When you use the NMS print utility, you print the window on which the mouse pointer is resting. For example, when pointing to a menu bar (near the top of the window), SNM Snapshot prints whatever is displayed on your monitor. When pointing to a browser, or text-displaying window inside a window, Snapshot prints only the Browser window. On HP OpenView, print capabilities may differ slightly.

For more information on the Snapshot utility, refer to the SunNet Manager 2.0 User's Guide.

Table 2-4 lists CiscoWorks applications that use the print utility and those that use the lpr print command. In general, all windows that display text use the lpr command.


Print Command Options in CiscoWorks Applications
CiscoWorks Application Snapshot Utility lpr Command
AutoInstall Manager X
Configuration Manager X
Contacts X
Device Inventory Manager X
Device Management X
Device Software Manager X
Device Monitor X
Device Polling X
Environment Monitor X
Domain Manager X
Global Command Manager
Health Monitor X
Log Manager X X
Configuration Snap-In Manager
Path Tool1 X X
Polling Summary X
Process Manager X
Real-Time Graphs X
Scheduler X
Security Manager X
Show Commands X
Software Library Manager X
Sybase DWB Not Applicable Not Applicable
Sync w/Sybase X

1 The Print command used depends on which Path Tool window you are currently in: Tools menu or Glyph menu.

When you select Print on a window that accesses the lpr command, the Print Command window appears. (See Figure 2-52.)


Figure 2-52: Print Command Window

To print, enter the name of your printer, including any path designations, and click on OK. To close the window without printing, click on Cancel.

You can set up a default printer selection by setting an environmental variable PRINTER before you start SunNet Manager session. For example enter the following:

# setenv PRINTER <printername> 

On HP OpenView, you can set up a default printer selection by setting an environmental variable LPDEST before you start HP OpenView. For example enter the following:

# setenv LPDEST <printername> 

Note When you print a color image on a black and white printer, the colors are printed in various shades of gray.
Exit Command

To exit from a primary application window, select File>Exit.

Exit closes the active window. If you exit from a primary window, the SNM Console displays. If you exit from a secondary window, the primary window displays. If multiple primary windows are opened, only the one from which Exit was invoked is closed; other windows remain open and active.

Security Menu

The Security menu, shown in Figure 2-53 appears in the windows of CiscoWorks applications that use authentication-checking, a feature that allows an administrator to grant different levels of access privileges to CiscoWorks applications. Depending on whether the application governs a process or database function, you can use the menu commands to access another domain, to log in as another user, or to learn what user privileges you have to a given CiscoWorks application.




Figure 2-53: Security Menu
Change Domain Command

The Change Domain command allows you to display another domain. A domain represents a logical group of devices. A device is any network entity that contains an SNMP agent. (Devices generally include routers, bridges, and communication servers.)

The Change Domain command is used by applications that work with devices listed in the Sybase database. Applications that support the Change Domain command include Device Monitor and Device Polling. Changing domains may alter your privileges to an application because privileges are granted according to your group/domain association. In most cases however, when you access another domain, you can expect reduced privileges to the applications that manage its devices.

Change User Command

The Change User command allows you to log in under another user name. Use this command when you need the privileges of another user in order to access applications that would otherwise be unavailable to you.

Privileges Command

The Privileges command allows you to display your current privileges for the specified CiscoWorks application. When you select the Privileges command, the User Privilege window appears, listing your application-specific privileges. (See Figure 2-54.)


Note An item in any CiscoWorks application that is grayed out represents an inactive or unavailable option or feature. If you need privileges beyond those defined by your User ID account, see your CiscoWorks administrator.




Figure 2-54: User Privilege Window

Help Menu

The Help menu provides options for viewing online help for the current application and its current version number. (See Figure 2-55.)


Figure 2-55: Help Menu
Help on the Application

When you select On <application name>, a window similar to Figure 2-56 appears.




Figure 2-56: Help Window

Enter characters in the search string field. Then use the Search Forward and Search Reverse buttons to find your search string in the displayed text.

Version Command

Use the Version command from the Help menu to display the current version of the active CiscoWorks application. (See Figure 2-57.)


Figure 2-57: Version Command

Using Command Buttons

The command buttons used in the Device Management application are described in this section. For more information on Device Management, refer Chapter 6, "Device Management."

To view the command buttons, perform the following steps:

Step 1 Select Device Mgmt.

On SNM, select Tools>Device Mgmt.


On HP OpenView, select Administer>Cisco Devices>Device Mgmt.


The Device Management window appears. (See Figure 2-58.)



Figure 2-58: Device Management Window

The following command buttons appear along the bottom of the window:


Step 2 Click on New to open the Device Information Window. (See Figure 2-59.) When you click on the New button, you see panes for Device Details and Inventory Details and Administrative Details.


Note However, when you display information about a device that already exists, only the Device Details and Inventory Details panes are displayed. The Device Information Window still contains a pane for Administrative Details, but is displayed only when you select Options>Admin Details.




Figure 2-59: Device Information Window
Note Use care because adding data records to a related table may also result in the creation of a duplicate unwanted record in the primary or other window table. If this occurs, delete the duplicate record by selecting its name in the Device Management window and clicking on Delete.

Step 3 When you finish entering data in the Device Information window, click on OK. The data is saved to the database and displayed in the Device Management window.

With the Device Information window open, you can change the data in any field as your needs determine. If you like, you can copy and paste data directly among windows or the fields within windows.


Step 4 When you finish modifying data about a particular device, click on Apply to save the changes.


Note When you click on a device name in the Device Management window, the Interfaces and Contacts associated with that device appear in the remaining windows. Clicking on Modify always displays database fields belonging to the selected device name, even though a particular interface or contact name may also be selected.

Security Options

If you use the Security Manager application to protect specified applications, all users must enter a valid username and password to access the protected CiscoWorks applications. For a detailed description of which CiscoWorks applications you can protect, refer to Chapter 7, "Setting Up Domains and Securing Applications."

Each CiscoWorks application has varying levels of access privileges. Each user is granted inherent privileges to certain applications (such as the ability to display devices) based solely on the user's group-domain association of the user. The CiscoWorks administrator governing Security Manager can grant further levels of "application-specific" privileges (such as add or change database information) to selected groups.

Logging In and Out

With security enabled, if you previously used the Login function on the Tools menu to log into CiscoWorks, no user identification window appears. If you have not used the CiscoWorks Login function, each time you access any of the secured CiscoWorks applications, CiscoWorks prompts you for a username and password. This login controls access to the application.

If you used Security Manager to secure your CiscoWorks applications, you can use the Login and Logout function from the Tools menu. For more information on logging in and out, refer to Chapter 7, "Setting up Domains and Securing Applications."

Time Saver By using the Login function, you need to log in only once. If you do not use Login, CiscoWorks will require user identification information (username and password) each time you attempt to start a secured application.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.