HP OpenView for Windows User Guide

3Com Corporation5400 Bayfront PlazaP.O. Box 58145Santa Clara, CA95052-8145

http://www.3com.com

© 19973Com CorporationAll rights reserved.Printed in the U.S.A.

09-1114-001

3/4” SPINE

1/2” SPINE

1/4”

HP OpenView for Windows®

User Guidef o r T r a n s c e n d M a n a g e m e n t S o f t w a r e

V e r s i o n 6 . 1 f o r W i n d o w s ® a n d ‘ 9 7 f o r W i n d o w s N T ®

®

HP OpenView for Windows® User’s Guide

http://www.3com.com/

Transcend Enterprise Manager for Windows Version 6.1Transcend Workgroup Manager for Windows Version 6.1

Part No. 09-1114-001October 1997

Hewlett-Packard Co.10500 Ridgeview Court Cupertino, California 95015 U.S.A.

Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this document is subject to change without notice.

Netware® and Novell® are registered trademarks of Novell Corporation.

Microsoft®, Visual Basic, and MS-DOS®are registered trademarks of Microsoft Corporation.

Notify!® Connect for Windows is a registered trademark of Ex Machina Corporation.

Paradox is a trademark of Borland International.©Hewlett-Packard Company 1997 All Rights Reserved

UNITED STATES GOVERNMENT LEGENDS:If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following restricted rights:

For units of the Department of Defense:Restricted Rights Legend: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) for Restricted Rights in Technical Data and Computer Software Clause at 48 C.F.R. 52.227-7013. 3Com Corporation, 5400 Bayfront Plaza, Santa Clara, California 95052-8145.

For civilian agencies:Restricted Rights Legend: Use, reproduction, or disclosure is subject to restrictions set forth in subparagraph (a) through (d) of the Commercial Computer Software – Restricted Rights Clause at 48 C.F.R. 52.227-19 and the limitations set forth in 3Com Corporation’s standard commercial agreement for the software. Unpublished rights reserved under the copyright laws of the United States.

ii

CONTENTS

ABOUT THIS GUIDE

How to Use This Guide 1Conventions 2

1 OVERVIEW

HP OpenView Interface 1-1Maps 1-2Autodiscovery 1-2Alarms 1-3

Polling 1-4Trapping 1-5

Alarm System 1-6SNMP Manager 1-7

2 CREATING NETWORK MAPS AUTOMATICALLY

IP and IPX Discoveries 2-2Preparing for a Discovery 2-2

Configuring Autodiscovery 2-3Your Computer’s Settings 2-4Managing Autodiscovery 2-6Maintaining the Autodiscovery Database 2-13

Creating Submaps of Discovered Devices 2-14Configuring Preferred Names 2-14Setting Layout Options 2-15

Executing the Layout 2-16

3 CREATING NETWORK MAPS MANUALLY

Drawing A Simple Map 3-2Drawing a Network Map 3-3

iii

Map Example 3-3Creating a Map File and Home Submap 3-4Adding a Background 3-5Adding Submap Symbols 3-6Adding Lines 3-7Adding Text 3-8Add Remaining Submaps 3-8

Saving a Map 3-9Printing a Map 3-9Web Browser 3-9Disabling the Map Editing Feature 3-9Map Toolbar and Commands 3-10

Status Bar 3-10Toolbar 3-11

Add Toolbox 3-12Select Object 3-13Text 3-13Lines and Connections 3-13Symbol 3-13

Selection Lists 3-14Extended Locate 3-14

4 MONITORING DEVICES ON THE NETWORK

Customizing Device Access 4-2Ping 4-3

Polling Network Devices 4-4Creating a List of Devices to Poll 4-4Removing Devices to Poll 4-5

Selection Lists 4-6Loading a Selection List 4-6Saving a Selection List 4-6Editing a Selection List 4-6Configuring System Polling Parameters 4-7Configuring Device Types 4-7Configuring Parameters for Selected Devices 4-9Turning Polling On and Off 4-10AutoPolling 4-10

iv

Monitoring Traps from Network Devices 4-10Customizing Traps 4-11Selecting a Device Class 4-12Ignoring Traps 4-12Specifying Traps for a Device Class 4-13Choosing Trap Alarm Actions 4-14Description Field Variable Substitution Syntax 4-15Loading Traps 4-16Automatically Acknowledging Alarms Generated by Traps 4-16

Managing Alarms 4-17Selecting Map Status Options 4-17Status Propagation 4-18Configuring Alarms 4-21Viewing Alarms 4-22Selecting Alarms for Display 4-23Acknowledging and Deleting Alarms 4-24

Configuring Alarm Processing 4-25General Alarm Settings 4-26Alarm Sound Settings 4-27Alarm Sound Configuration 4-27Alarm Status Propagation 4-28Alarm Forwarding 4-28Running Programs 4-30DDE Commands 4-31Paging Program 4-32Alarm Database 4-32

DMI Manager 4-33HP Top Tools 4-33

5 MANAGING SNMP NETWORK DEVICES

Defining a Query 5-1Selecting Variables to Query 5-3Moving Around the Variable Tree 5-4Selecting a Variable to Use in the Query 5-5Removing a Variable From the Query List 5-5Variable Descriptions 5-6

Saving a Query 5-6

v

Selecting a Query 5-7 Removing a Query from the Menu 5-8

Displaying SNMP Query Results 5-9Displaying a Query as a Table 5-10Displaying a Query as a Graph 5-14Changing a Variable's Value 5-17

Managing the SNMP Manager Database 5-17Status Line 5-18Available MIB Files 5-18Files in MIB Database 5-19

MIB Structure 5-19MIBs Dependent Upon MIB-2 5-19Vendor-Specific Private MIBs 5-20Selecting MIB Files to Add to the Database 5-20

6 IN CASE OF DIFFICULTY

Things You Should Know 6-1What You Should Do 6-2

OVMDump Diagnostic Tool 6-3OpenView Backup 6-3

7 CUSTOM CONTROLS

Code Components 7-2Control Description 7-3Properties 7-5Summary of Control Properties 7-5

Events 7-8Basic Operation 7-9Data Properties 7-10Alarm and Threshold Properties 7-11Table Access Properties 7-13Advanced Properties 7-14

Creating an Application 7-15Debugging Visual Basic Applications 7-15

Registering Your Visual Basic Application 7-18Menus and Commands 7-21

Adding Features To Your Application 7-26

vi

A OPENVIEW COMMAND AND TOOL REFERENCE

Menu Commands A-1File Menu Commands A-1Edit Menu Command A-2View Menu Commands A-2Monitor Menu Commands A-3Control Menu Commands A-3Autodiscovery Menu Commands A-4Options Menu Commands A-5Window Menu Commands A-5Help Menu Commands A-5

Toolbar A-6Toolbar Functions A-6

B CONFIGURING NOTIFY! CONNECT

OVWIN.INI Configuration B-1Notify! Configuration B-2

INDEX

vii

viii

ABOUT THIS GUIDE

About This Guide provides an overview of this guide, describes guide conventions, tells you where to look for specific information and lists other publications that may be useful.

This user’s guide describes the features and functions of HP OpenView for Windows Workgroup Node Manager (referred to as OpenView). To access additional information that is not covered in this guide, click on any of the program Help buttons.

This guide is intended for network system administrators that are familiar with the Windows user interface and have a basic understand of networks and the Simple Network Management Protocol (SNMP).

If you installed applications to run under HP OpenView, you will find descriptions of application-specific functions in the application documentation.

If the information in the Release Notes shipped with your product differs from the information in this guide, follow the Release Notes.

Finding Specific Information in This Guide

This table shows where to find specific information in this guide.

If you are looking for Turn to

An overview of HP OpenView features and how it manages networks

Chapter 1

How to create a map using Autodiscovery Chapter 2

How to create and edit network maps using the map toolbar and commands

Chapter 3

A description of polling, trapping, and configuring alarms Chapter 4

(continued)

2

A

BOUT

T

HIS

G

UIDE

Conventions Table 1 and Table 2 list conventions that are used throughout this guide.

How to use the SNMP Manager to query SNMP devices and display query results

Chapter 5

What to do if you are having difficulty getting HP OpenView to work

Chapter 6

The HP OpenView Visual Basic custom controls that are provided for application development

Chapter 7

A list of all the HP OpenView commands and tools and their functions

Appendix A

How to configure Notify! Connect Appendix B

Table 1 Notice Icons

Icon Notice Type Alerts you to...

Information note Important features or instructions

Caution Risk of personal safety, system damage, or loss of data

Warning Risk of severe personal injury

Table 2 Text Conventions

Convention Description

Syntax The word “syntax” means you must evaluate the syntax provided and supply the appropriate values. Placeholders for values you must supply appear in angle brackets. Example:

Enable RIPIP by using the following syntax:

SETDefault !<port> -RIPIP CONTrol = Listen

In this example, you must supply a port number for <port>.

(continued)

Conventions

3

Commands The word “command” means you must enter the command exactly as shown in text and press the Return or Enter key. Example:

To remove the IP address, enter the following command:

SETDefault !0 -IP NETaddr = 0.0.0.0

This guide always gives the full form of a command in uppercase and lowercase letters. However, you can abbreviate commands by entering only the uppercase letters and the appropriate value. Commands are not case-sensitive.

Screen displays This typeface represents information as it appears on the screen.

The words “enter” and “type”

When you see the word “enter” in this guide, you must type something, and then press the Return or Enter key. Do not press the Return or Enter key when an instruction simply says “type.”

[Key] names Key names appear in text in one of two ways:

■ Referred to by their labels, such as “the Return key” or “the Escape key”

■ Written with brackets, such as [Return] or [Esc].

If you must press two or more keys simultaneously, the key names are linked with a plus sign (+). Example:

Press [Ctrl]+[Alt]+[Del].

Menu commands and buttons

Menu commands or button names appear in italics. Example:

From the Help menu, select Contents.

Words in italicized type

Italics emphasize a point or denote new terms at the place where they are defined in the text.

Words in bold-face type

Bold text denotes key features.

Table 2 Text Conventions (continued)

Convention Description

4 ABOUT THIS GUIDE

1
OVERVIEW
The HP OpenView Workgroup Node Manager is a "platform" for network management programs. It provides a standard graphic interface so that multiple network applications can share a common display and alarm system. In addition, it provides basic network management functions to interface with devices on the network. Workgroup Node Manager consists of:

■ Maps

■ Autodiscovery

■ Alarms

■ SNMP Manager

HP OpenView Interface

HP OpenView provides a user interface for managing network applications and devices; see Figure 1-1.

Figure 1-1 HP OpenView interface

Applications

HP OpenView

* Maps

* Autodiscovery

* Alarms

* SNMP ManagerDevicesUser

1-2 CHAPTER 1: OVERVIEW

Maps Devices in the network are displayed on maps. Devices and subnetworks can be organized into submaps to suit your needs. You can create separate submaps of devices grouped by device function, network organization, or corporate organization. You can use the maps to manage your network from a single display even when the network includes devices from different manufacturers.

Figure 1-2 Managing the network using maps

Programs that manage hubs, routers, servers, and other network devices can run in the background. Changes in network status are displayed on network maps with icons representing devices. Color is used to indicate device status. Submaps allow you to create several views of your network to simplify management. You can add meaningful graphics such as geographic maps and floor plans as backgrounds for your map to provide "real world" visual references for your network.

Autodiscovery Autodiscovery is a function that helps you to create maps of your network. It uses information such as the range of network addresses, community names, and the types of devices on your network to locate most of the devices present. You can then request OpenView to draw a network map based on the devices found.

Manufacturers who have designed their devices to be managed through OpenView can provide descriptions of their devices so that the correct icons and labels can be used by the layout operation. This

Applications

AutodiscoveryUser

Alarms 1-3

information is stored in a device definition file. In addition, manufac-turers can provide application programs that can locate their devices or provide additional information for use in creating maps.

Once you have entered information about the networks and devices that you want discovered you can perform a discovery. The discovery process creates a list of discovered devices. Application programs can provide supplemental information for the list. You can then control which devices in the list are used to create the map using the layout function.

Figure 1-3 Autodiscovery can be used to automatically create network maps

Alarms Changes in device status or "alarms" provide the notification to the OpenView map that a noteworthy event has happened on the network. Alarms are the main mechanism used to communicate device status. Alarms are displayed on the network map and are listed in the Alarm Log. The alarms are also recorded in a Paradox database. The Alarm database allows you to generate reports or archive network performance. In addition to visual cues, alarms can be set to trigger sounds, programs, or even activate a remote paging device based on the type of alarm received.

CH1-A3


Figure 1-4 Alarms are generated by third party applications and the OpenView Polling and Trap Manager functions

Polling Polling is a function that lets you check to see if a network device is up (running) or down (not running). A poll is a simple request sent to a device that asks the device to respond. If the device responds, it is functioning. You can have OpenView "poll" a list of devices periodically to check to see if they are running. When a response (or time out due to a lack of response) occurs, OpenView processes the information as an alarm; see Figure 1-5.

Figure 1-5 HP OpenView polling

CH1-A4

CH1-A5

Alarms 1-5

Trapping Some devices can send messages when certain conditions occur. The conditions may be startup, shutdown, data error, or a preset level of activity. The message resulting from a device condition is called a trap. Devices vary in their ability to send traps. Refer to your device manual to see if the device can send traps.

Figure 1-6 Trapping

In order for a device to send a trap, you must tell it where to send the trap. The address of the OpenView console to receive the traps is usually set when the device is installed. The device manual should indicate how to set this address on the device.

Once devices are configured to send traps to the OpenView console, they will be recorded in the alarm log by default. You can customize how OpenView responds to traps using the Customize Traps dialog. You can select which traps to respond to. The traps can be of particular types or from particular device classes. Trap types can be selected from a list of standard traps or you can define custom traps for specific device classes. When OpenView receives a trap message OpenView converts it into an alarm and processes it through the alarm system.

CH1-A6


Applications and Alarms

Equipment manufacturers create application programs to provide information on the status of their devices. Application programs can request status information from the device, make device settings, or run device diagnostics. The application program then sends the appropriate information to OpenView as alarms.

Alarm System OpenView allows you to configure how alarms will be processed or displayed on maps, clear alarm conditions, and create reports from the alarm log. In addition, you can configure alarms of a particular level to start programs, send pages, or be forwarded to other workstations.

Figure 1-7 HP OpenView Alarm system

CH1-A7

SNMP Manager 1-7

SNMP Manager The Simple Network Management Protocol (SNMP) Version 1 is a standard that defines a method of communicating with and controlling network devices. Devices that support the SNMP V.1 standard can be queried for their status and other device information. Some devices allow you to change device settings or configuration using SNMP commands. SNMP commands request that the values of device settings be returned ("Gets") or changed ("Sets"). OpenView provides an SNMP Management function that can be used to communicate with SNMP devices.

The device settings and other device information are available as variables and are defined either in a standard Management Information Base (MIB) file or in a custom MIB file provided by the device manufacturer. The SNMP Manager uses a database to hold lists of the variables that can be accessed for each device on your network. Before you can use the SNMP Manager you must make sure that the list of variables needed for your device have been added to the database used by the SNMP Manager. The process of adding the device information to the database used by the SNMP Manager is called "compiling".

The information returned by the device can be displayed in tabular form, graphic form, or saved in a file. The device requests (queries) that you use with the SNMP manager consist of a device address, variable list, and instructions for processing the results returned by the device. You can store these queries in a file for use again.


Figure 1-8 SNMP Manager can be used to obtain information from devices or change device settings

CH1-A8

2
CREATING NETWORK MAPS AUTOMATICALLY
You can create network maps automatically using Autodiscovery to locate and identify devices in your network. Autodiscovery and Layout execute automatically. Autodiscovery starts when OpenView is started. When Autodiscovery completes, a map will automatically be drawn. Polling will automatically start as soon as the discovery process is complete.

You can also manually create network maps using the map tools. In most instances, creating maps with Autodiscovery is the fastest and easiest method. You can change a map created with Autodiscovery at any time using the map tools. This chapter provides information about how to create maps using Autodiscovery. It includes information about:

■ Entering information required to perform a discovery

■ Starting the process for a IP discovery and an Extended (IPX, other) discovery

■ Creating submaps of discovered devices

Figure 2-1 Autodiscovery

For information about manually creating new maps or editing existing maps, see Chapter 3, “Creating Network Maps Manually.”

Configure Discover Layout

Configure

Discovery

Networks

Discovery

Enter networkand devicespecifications

Configureand startAutodiscovery

Build databaseof discovereddevices

Select layoutoptions and draw map

2-2 CHAPTER 2: CREATING NETWORK MAPS AUTOMATICALLY

IP and IPX Discoveries

Autodiscovery searches IP, IPX, and VINES networks, identifies devices on the networks, and assigns the appropriate OpenView map symbol to each device. You can then use Autodiscovery's layout function to create an OpenView map of the devices.

IP Discovery uses routers to discover and identify all IP devices in your network. Autodiscovery reads each router's “next hop” and ARP tables, then discovers and identifies all the devices listed in the tables. Autodiscovery continues the IP discovery until it has searched all segments of the network.

Extended discovery is a combination of IPX and supplemental IP device discovery. It uses NetWare diagnostic services to locate all IPX devices, then uses SNMP to identify the devices. It can also run program modules created by equipment suppliers that provide additional discovery information. These supplemental modules may or may not be present depending on your OpenView system's configuration.

Once you start either an IP or Extended discovery, they run in the background and perform periodic discoveries to update a database of device information. You can configure Autodiscovery to schedule discoveries, limit the devices included in a search, and customize the layout of an OpenView map.

Preparing for a Discovery

To start a discovery, you need to know some information about your own network and the networks you want Autodiscovery to search.

To run an IP discovery, you must provide the following information:

■ Your IP subnet mask

■ The IP networks you want to discover

■ The IP address and community name for your default gateway or router if present.

You can run an Extended discovery of IPX and VINES devices without providing information about your network. However, if you want to limit the discovery to specific IPX or VINES networks, you need to

Preparing for a Discovery 2-3

provide the names of those networks. You can use Novell’s COMCHECK utility to see which IPX networks are currently in use.

You can use the form provided here to record the information.

ConfiguringAutodiscovery

Before you can run a discovery, you need to enter information about your network and the networks you want to search. You enter this information in the Configure Discovery Networks dialog box. To open the dialog box, choose Configure from the Autodiscovery menu and then choose Discovery Networks.

IP Network Addresses

IP Router/Gateway

IP Router/Gateway Community Name

IPX Network Names

IP Subnet Mask

Address

. . .

.

.

.

.

.

.

.

.

.

. .

.

CH3-05


You don’t need to have both IPX and IP devices on your network for Autodiscovery to run. If you have only one type of device, just enter the IP or IPX information in the appropriate fields.

Your Computer’sSettings

IP Subnet Mask – Enter your subnet mask. This mask should be specific to your local network and also the same as the mask you specified when you installed your TCP/IP protocol stack. The Subnet Mask is used to calculate the node address range for your network. If you are using the FTP stack, this value will be entered for you.

IP Router/Gateway – Enter the address for your IP default gateway or router. Autodiscovery uses this address to begin a discovery. If you do not enter an address for a router, OpenView will use the subnet mask to test each of the possible addresses in your network. This process takes much longer and uses more network resources than obtaining valid addresses from the router. If you are using the FTP stack, this value will be entered for you. The IP Router/Gateway applies to the current map only.

IP Router/Gateway Community – Enter the community name. OpenView uses this name as a password to gain access to your gateway or router, and by using SNMP as the means of communication.

The default community name in the router community field is stored in the central database (accessed through Customize Device Access) for the IP address for the router. If no name is entered, the system default is used. By default, the system default is “public.”

Networks

Net Address – Enter the address of a network you want to search in the Networks text field, then click the Add Net/Set Mask button. Autodiscovery adds the network to the list of networks to be searched. To delete a network from the list, select the network address in the list, then click the Delete button. If you don’t know the address of a network, you can enter the address of one device on the network and click the Add Net/Set Mask button. Autodiscovery will calculate the network’s address using the IP subnet mask (below) and add it to the list. The range of networks calculated is displayed.

Subnet Mask – This field is only relevant for IP networks. If the Subnet Mask field is empty, the default mask will be used when you press Add Net/Set Mask. You can also edit the Subnet Mask to other values if


your system connects to IP networks with different subnet masks. The subnet masks are used initially to determine how you have grouped IP addresses into networks. OpenView discovery may correct these values during Router Discovery as it reads the subnet masks configured within routers.

Discover All IP Networks – Select this option if you don’t want to limit the IP discovery to only those IP networks listed in the Networks section, but prefer Autodiscovery to Locate and identify all IP Networks within the number of hops specified in “IP Maximum Hops.”

Discover All IPX Networks – Select this option if you don't want to limit the IPX discovery to only those IPX networks listed in the Networks section, but prefer Autodiscovery to locate and identify all IPX Networks within the number of hops specified in “IPX Maximum Hops.”

When you have entered all the information, click OK to save the information. All of the information that you enter in the “Configure Discovery Networks” dialog is saved with the map. When you load a different map, you will load the values saved with the newly loaded map.

To add information for additional router or other devices in your network use the Customize Device Access command.

Choose Customize Device Access from the Options menu. Choose Add, this will display the Add Device Access Information dialog box.

CH3-04


Type the addresses of the network routers and their respective community names in the Address and Community Name text boxes. Click OK.

For more information about how to use the Customize Device Access dialog box, see Chapter 4.

ManagingAutodiscovery

The discovery processes can be scheduled to run automatically or can start Discovery on demand using the Discovery Manager dialog box. You can specify devices to be added to or deleted from Autodiscovery. You can also monitor the progress of both the IP and discoveries in the Discovery Manager dialog box. Note that the Discovery Manager dialog box is iconized and the Discovery Manager command disabled while Discovery is running. To view the Discovery Manager double click the icon.

Scheduling Discovery

You can set a schedule for Autodiscovery to run both the IP and Extended (IPX, other) discoveries. You set these schedules in the Configure Discovery Schedule dialog box. To open the dialog box, go to the Autodiscovery menu and choose Configure, then choose Discovery Schedule.

IP Discovery – Enter the number of minutes you want as the interval between discovery processes.

CH3N-04


Choose the Enable ARP Cache Reader option if you want Autodiscovery to search all ARP Caches each time IP Discovery is run.

Choose the Enable IP Router Discovery option if you want Autodiscovery, to search for routers each time IP Discovery is run.

If you want to completely disable IP discovery, deselect both the Enable ARP Cache Reader option and the Enable IP Router Discovery option.

Router Discovery – If you have enabled Router Discovery, it will run whenever:

■ Basic IP Discovery is first run

■ After you have selected Clear Database

■ If you select Discover from the AutoDiscovery menu and then Discover Routers

Before running Router Discovery, to correctly determine the connectivity of all IP networks you should specify the Community names (see Customize Device Access) of all routers connecting discovery networks (see Configuring Discovery Networks). Without correct community names, the router discovery will not be completely successful.

Router Discovery can dynamically prompt the user for the community name of any router for which it needs a community name. To enable this feature, the OVWIN.INI file should have the following specified in the [Discovery] section:

IPRouterAskForCommunity=yes

A prompt appears to the user when the community name of a router is needed. Router discovery will be suspended until the user has made a selection. The user should correct the Community Name, click Save Community, and then click Done to allow router discovery to resume. This prompt appears as each Router with an incorrect community name is detected. To have no further requests for Community Name during router discovery, click Ask No More.


Topology Discovery – You can have OpenView automatically determine how segments in a network are connected. If Discover Topology is enabled, at the end of the normal discovery process OpenView will attempt to determine the segmentation of the network based on how the discovered devices are connected to bridges. You can also start a topology discovery at any time using the Discovery Topology command in the Discover Menu under autodiscovery. The status of the topology discovery will be displayed in the Extended Discovery status field in the Discovery Manager Dialog. When you perform a layout the topology information will be used to show how the subnets in your network are connected. See Help for more information on Topology Discovery.

Extended (IPX, other) Discovery – If you want Autodiscovery to start the extended (IPX, other) Discovery at regular intervals, choose the Timed Intervals option button and enter the number of minutes you want for the interval.

If you want Autodiscovery to start the Extended (IPX, other) Discovery at specific times, choose the Specified Times option button and place a marker at each hour you want to run a discovery. To place a marker, choose the Move option button, then click the New Marker button and drag the marker to the time you want. As you drag the marker, the corresponding time appears over the bar. If you want to delete a marker, choose the Delete option button, then click the marker you want to delete.

Configuring Device Classes

If you want to narrow the search for a discovery or limit the devices drawn by layout, you can configure Autodiscovery to ignore certain device types in its search. For example, if your network has a large number of personal computers, you may want to reduce the discovery process time by excluding the computers from the discovery or you may want to layout a map that contains only certain types of devices. You specify the device types you want Autodiscovery to ignore in the Configure Device Classes dialog box. To open the dialog box, choose Configure from the Autodiscovery menu, then choose Device Classes.


The Configure Device Classes dialog box lists all registered device classes. Any device that doesn’t respond to an SNMP identification request (such as most personal computers) is listed as a Generic IP or Generic IPX device.

Ignore – Choose the device type that you want Autodiscovery to ignore and then click the Ignore button or double-click on the entry to toggle the “ignore” flag.

If you want to include the device type in the search or layout again, choose the device type in the list, then click the Include button.

Configuring Ignored Devices

If you want to prevent specific devices from being added to the Autodiscovery database by discovery, you can configure Autodiscovery to ignore those devices. You specify these devices in the Configure Ignored Devices dialog box. To open the dialog box, choose Configure from the Autodiscovery menu, then choose Ignored Devices.

CH3A-07

CH3A-06


Ignored Devices – Enter the network address of the device you want to ignore, then click the Add button to add the device to the list of ignored devices. The device will not be removed from the Autodiscovery database but will not be included in any maps you create from the database.

If you want an ignored device to be included during layout, remove it from the list of ignored devices. Click the device’s address in the list box, then click the Delete button to remove it from the list. If the device is contained in the database, Autodiscovery will include it in any maps you create from the database. Press OK to save the changes to the database. The list of ignored devices is stored with the current map.

User-Specified Devices

You can maintain a separate list of devices to be added, without running an entire discovery. When you add a device manually, Autodiscovery includes it in the database and in any maps you create from the database. You add these devices using the Configure User-Specified Devices dialog box. To open the dialog box, choose Configure from the Autodiscovery menu, then choose User-Specified Devices.

User-Specified Devices – Enter the network address of the device you want to add to the supplemental list, then click the Add button to add the address to the list box. If you want to delete a device from the list, select the device’s address in the list box and click the Delete button. Press OK to save the changes to the database.

If a device you entered is in a network that you did not specify as a discovery network, a message box will ask if you want the network added to the list of discovery networks. If you answer “Yes”, all devices in the added network will be discovered and added to your database. If

CH3A-05


you say “No”, the device that you specified will be added as a user-specified device. The list of user-specified devices is stored with the current map.

Viewing Autodiscovery Results

To view the Autodiscovery process, choose Discover from the Autodiscovery menu, then choose Discovery Manager. If the Discovery Manager command is grayed, this means that the Discovery Manager is already being displayed, though it may be hidden behind another window or possibly be iconized.

The list box in the Discovery Manager displays the address, device name, and System Description MIB variable of each discovered SNMP device.

If Autodiscovery cannot identify a device, the list displays the device name as a Generic IP or Generic IPX device.

Networks – This field lists the address of each network that contains a discovered device. If a network that you entered in the discovery Networks dialog is not listed no devices were discovered in this network. Verify that you have entered the correct network address and community name.

CH3-06


Display – You can control the contents of the device list by choosing one or more of the display options.

■ Choose Database Contents to show all discovered devices.

■ Choose IP Discovery to show all devices discovered by IP Discovery since the last time you reset the display.

■ Choose Extended (IPX, other) Discovery to show all devices discovered by Extended (IPX, other) Discovery since the last time you reset the display.

■ Choose New Since Last Layout to show all devices added to the database since the last layout. (This choice deselects the other options.)

Database Contents – This option overrides the other three options. For example, if you choose Database Contents, but don't choose Extended (IPX, other) Discovery, Autodiscovery still displays all discovered devices, including those located by an Extended discovery. However, newly discovered devices will not appear. This list is not updated with new data.

Totals – This box displays current totals of devices and networks for the display list and for the Autodiscovery database.

Start Discovery – Click this button to start.

Stop Discovery – Click this button to stop.

Reset Display – Click this button to clear the list box. When you click Reset Display, Autodiscovery clears only the display list, not the Autodiscovery database. The date and time when you last reset the display is shown at the top of the Discovery Manager.

Discovery Status – This box shows the current status of the IP and Extended (IPX, other) discoveries.

IP – This field shows the amount of time until the next discovery. When Autodiscovery is running this field also displays next hop routers and SNMP requests to specific IP addresses.

Extended – This field tells you whether or not Autodiscovery is currently running an Extended discovery.


Maintaining theAutodiscovery

Database

You can save the contents of the Autodiscovery database. If the Autodiscovery database has more information than you want, you can clear it. The database is a part of the map. Saving the map will also save the autodiscovery database for the map. (Note that the New command in the file menu does not clear the database.)

Saving the Database

To save a readable description of the database, choose Discover from the Autodiscovery menu, then choose Dump Discovery Database. Autodiscovery lists the database contents in the OVDUMPIT file. This file is stored in the OpenView for Windows directory. Each “dump” appends to end of the OVDUMPIT file, so you may want to delete or remove the current file before dumping the database to it.

Clearing the Database

To clear the database, choose Discover from the Autodiscovery menu, then choose Clear Discovery Database. Autodiscovery displays a message asking if you want to reset all the discovery information.

To clear the database, click on Yes. If you don't want to clear the database, click on No. Note that this does not clear the user-specified configuration information such as discovery networks, user-specified devices, ignored devices, or scheduling information. It only affects the Discovery database for the currently loaded map.

Running a Router Discovery

After completing an initial discovery, Autodiscovery can run periodic discoveries, updating its database with new information from routers and ARP caches. But you may want to start a router

CH3-08


discovery without waiting for a scheduled discovery process. This may occur if for example, you have installed a new router, or added a new network to discover.

To run a router discovery, choose Discover from the Autodiscovery menu, then choose Discover Routers.

Autodiscovery displays a message to confirm that a router discovery should be performed.

Click OK to clear the message from the screen.

Creating Submaps of Discovered Devices

Once you have used Autodiscovery to identify network devices, you can create submaps containing the discovered devices. To create submaps using information obtained from Autodiscovery you:

■ Configure preferred names (optional)

■ Set layout options (optional)

■ Perform the layout

ConfiguringPreferred Names

You can associate a more meaningful name (for example, Denver Office #2) with the device address. This preferred name is saved into the central database and is used for all maps drawn by layout on this OpenView console.

To associate a name with a device address, choose Configure Preferred Name from Layout in the Autodiscovery menu. Type the address in the Network Address text box and then type the name you want to associate with the device in the Preferred Name text box. Click on the Save button.

CH3A-04

Creating Submaps of Discovered Devices 2-15

Setting LayoutOptions

You can change the general appearance of your layout map by setting layout options in the Basic Layout Options dialog box. To open the Basic Layout Options dialog box, choose Layout from the Autodiscovery menu, then choose Basic Layout Options.

Internetwork View Symbol Spacing – Drag the scroll box to decrease or increase the distance between symbols on the “Internetwork” submap (called “ALL NETS”) of the current map. The spacing number decreases or increases according to the position of the scroll box on the scroll bar.

Network View Symbol Spacing – Drag the scroll box to decrease or increase the distance between symbols on each of the Network View submaps created by layout. The spacing number decreases or increases according to the position of the scroll box on the scroll bar.

CH3-11

CH3-13


Segmented View Symbol Spacing – Drag this scroll bar to specify the horizontal spacing between symbols representing each device in the Segmented View submaps. This will take effect the next time you do a Basic Layout and Topology Discovery has been enabled.

Network View Submap Width – Drag the scroll box to decrease or increase the width of all submaps in your layout. The width number decreases or increases according to the position of the scroll box on the scroll bar. A greater width allows more symbols to fit on a submap.

Label Devices with MAC Addresses – A MAC (Media Access Control) address is the hard coded address of the device's network interface.These addresses are assigned by hardware manufacturers and should be present on the network device or with the documentation shipped with the device. Choose this option if you want to display the MAC address for each device in the device labels of your layout map.

AutoArrange Redrawn Maps – This checkbox allows you to have OpenView layout all discovered devices. If this checkbox is not checked, OpenView will not change the position of devices already on the map. Devices that are new since the last layout will be added at the bottom of the map.

When you have made all the changes you want to the layout options, click OK to save the changes. Autodiscovery will implement the changes in the next map you create with the Do Basic Layout command.

Executing the Layout

The Do Basic Layout command creates a new submap named “ALLNETS” with the notation “Internetwork View” and a set of “Network View” submaps consisting of one submap for each network containing discovered devices.

If you have enabled a Topology Discovery and Topologic information was found for any of the subnets, a “Segmented View” submap will be created showing the network segments found. The nodes found in each segment will be shown in a “Nodes in Segment” submap.

Each time you perform a layout in a given map file, any previous submaps drawn by OpenView will not be effected unless there is a change in the devices discovered. (New devices will be added at the bottom of the submap.) You can control the redrawing of the Layout

Executing the Layout 2-17

submaps using the AutoArrange setting in the Basic Layout Options dialog.

In the following example, a map named MAP100 has been created following an Autodiscovery with Topologic Discovery enabled. OpenView has identified three major subnets, 0000BEEF, BABABABA, and 0000000A. The 0000000A subnet was found to have three identifiable segments, S1, S2, and S3 as well as some nodes that OpenView could not place with a particular segment.

MAP:ALL NETS

Network B

Network A Network C

Network View

Network View

MAP:C

MAP:A

MAP:BMAP:C.S2

Internetwork View

Segmented View

Network C.S2

Network C.S1 Network C.S3

Nodes in Segment View

MAP:C.S1 MAP:C.S3




To determine whether to perform another layout, click the New Since Last Layout check box in the Discovery Manager dialog box. It displays nodes not drawn on your map that have been discovered since the last time you ran layout.

Internetwork ViewAll Nets

Network View0000BEEF Segmented View

0000000A

Network ViewBABABABA

Segment View S1 Segment View S2

Segment View S3

CHN-24

CH3N-18

CH3N-19

CH3N-20

CH3N-23 CH3N-21

CH3N-24

3
CREATING NETWORK MAPS MANUALLY
This chapter describes how to create, edit, save and print maps using the map Toolbar and map commands. The first part provides instructions on how to create a map. The last part of the chapter provides a summary of the map tools and commands.

For information about how to create maps using the Autodiscovery feature, see Chapter 2, Creating Network Maps Automatically.

OpenView maps use symbols or icons to represent network devices and references to submaps. Lines show communication links between devices. Connections within your submaps “attach” device symbols to each other so that the devices remain connected when moved on the map.

You can assign a background image for a map that shows the physical location of the network devices.

Figure 3-1 Network map with background

CH4-01

3-2 CHAPTER 3: CREATING NETWORK MAPS MANUALLY

Drawing A Simple Map

Before you create a network map, you need to know the physical layout of your network. It may be a single LAN, several LANs, or a very complex enterprise-wide network. Whenever possible you should break your map into submaps that help you visualize the network organization. You can create submaps for a workgroup, building site, device type, or any other convenient grouping. The same device can be placed on several submaps to provide alternate “views” of the network.

The home submap should contain a symbol for each submap on the next lower level in your map. Some home submaps include a submap symbol for every submap in the entire map. From the home submap you can “walk” through your entire network by clicking on submap symbols to display the associated submap.

If your home submap does not contain a symbol for every submap, it should contain a “path” to every device in the network via the submap symbol. The submap symbol displays the most severe status color for all of the nodes or devices within it. This allows the most severe status information for any device in the network to be propagated up to the home submap. The home submap can then give you an overview of status for the entire network.

Home Home

Submap A Submap B Submap A

Submap B

Home submap with a submapsymbol for each submap

Home submap with apath to all submaps

Drawing a Network Map 3-3

Drawing a Network Map

A typical procedure for drawing a network map is as follows:

1 List all of the devices that you want represented in your map.

Note the network address of each device (if available) and its relation to the other devices.

2 Organize the devices hierarchically into levels based on their network position, device type, or function.

3 Create a “home” submap.

If possible, add an appropriate background bitmap. Add a submap symbol on the home submap for each submap in the next level of your network hierarchy.

If you have selected the “Create Submaps Automatically” option in the Customize OpenView dialog, a submap will be created automatically for each submap symbol that you add to the map.

4 Create a submap for each of the second level submaps shown on the home submap.

If possible, add an appropriate bitmap to aid in symbol placement. Add device symbols to each submap along with lines, connections, and annotations.

5 Repeat the process for each level of the hierarchy until all devices are represented.

6 Add additional submaps as desired for alternate views of your network.

For example, it might be useful to have a submap that shows all of the hubs or routers in a network.

Map Example The following example uses OpenView to create a simple network map. The map file containing the submaps is NORTHNET.OVM. NorthNet consists of a home map, three regional submaps, and three local submaps for each regional submap.


Table 3-1 Table of NorthNet Submaps

Background bitmaps are used to make submap layouts more meaningful. The bitmaps used in NorthNet are WORLDMAP.BMP, USA.BMP, EUROPE2.BMP, FAREAST2.BMP, and OFFICE.BMP.

Creating a Map Fileand Home Submap

To create a map file and home submap, follow these steps:

1 Choose New from the File menu to create a new map.

OpenView will display an empty submap with a name of the form:

<map>:<submap>

where <map> and <submap> are initially “UNTITLED”

2 Choose Save As from the File menu to name the map file PRACTICE.

3 Choose Rename Submap from the Edit menu to name the current submap WORLD.

Home Submap

Regional Submaps

Local Submaps Devices

World

Europe Edinburgh Support PC #11, 12, 13

Frankfurt Support PC# 31, 32, 33

Lyon Support PC # 21, 22, 23

Japan Nagoya Lab PC# 31, 32, 33

Osaka Support PC# 41, 42, 43

Tokyo PC, Hedeki, John, Yoshi Hub #3

USA Dallas Lab PC# 11, 12, 13

New York Marketing PC# 11, 12,

Sales Manager PC

San Jose Lab PC# 21, 22, 23


4 Choose Set Home Submap from the Edit menu and select WORLD as the home submap.

Adding a Background It's not necessary to use a background for a submap. They are independent of your network map data and can be added at any time. However, if you have access to suitable .BMP or .TIF images, they can actually make it easier to position icons. The bitmaps for NorthNet are provided in the OV\BKGROUND directory. If you do not use a background image, the grid commands in the View menu can be used to aid in positioning icons.

To add a background, follow these steps:

1 Choose Set Background Image from the Edit menu.

2 Find and select worldmap.bmp as the background for the WORLD submap.

3 Click OK.

CH4-02

CH4-03


Adding SubmapSymbols

To add submap symbols to your map, follow these steps:

1 Choose Add from the Edit menu to display the Add Toolbox.

2 Select Compound Object symbols from the SubmapClass list (the symbol class button should be down).

3 Select the Submap symbol from the icon list.

4 Position the cursor in the center of North America on the WORLD submap and click to drop the icon.

CH4-04

CH4-05


5 Enter the name for the submap symbol icon.

If desired you can enter Net or MAC addresses. Click OK.

6 Repeat steps 4 through 6 for Europe and again for Japan.

7 If necessary you can click on an icon and drag it to adjust its position on the submap.

You can determine whether or not to enter a description at the time you add an icon. Choose Customize HP OpenView from the Options menu. This will display the Customize HP OpenView dialog box. If you check the Describe objects as added check box, the Describe box appears each time you add an object. If you don’t check the Describe objects as added check box, the object is added without a name or label. You can add descriptions later on by selecting a map icon and using the Describe command in either the Edit or Monitor menus.

If the Describe function has not been deferred, you can press OK in the Describe dialog box and continue adding objects.

Adding Lines Lines are used to show relationships between network elements and to depict the physical wiring of a network. Use the line button in the Add Toolbox to select line drawing mode. Open the Line Type list box and select a line pattern or weight. Lines are drawn by clicking to set a start point and then dragging and releasing to set the end point.

CH4-07


To create a “connection” between two symbols, you can use the connection button to select connect mode. Connections differ from lines in that map objects can be moved and their connections will stretch or contract to maintain the connection. Connections are drawn from the center of one symbol to the center of another. Connections are displayed behind the symbols that they connect.

To connect the three submap symbols on the WORLD submap, follow these steps:

1 Select connections using the connection button in the Add Toolbox.

2 Select the second thinnest solid line type in the line type list box.

3 Click on the USA icon and then drag the connection to the EUROPE icon and release.

Repeat this so that all three regional submaps are connected.

4 To label a line, select the line and then choose Describe from the Edit or Monitor menus.

Once a description has been entered for a line or connection, it can be given status the same as other device icons.

Adding Text You can add text to a submap at any time using the text button in the Add Toolbox. Text is available in different sizes, bold, and underline. The font used is the Windows system default.

To add text to a submap, follow these steps:

1 Click the text button.

2 Select the size and style you want.

3 Click on the submap where text should start.

4 Type in the text.

5 Click again with the mouse or press the Enter key to end text entry.

6 After a text block has been entered, its position can be changed by selecting and dragging it with the mouse.

If you need to change the text, delete and reenter the text block.

Add RemainingSubmaps

If you have the “Create Submaps Automatically” option turned on in the Customize HP OpenView dialog box, a submap has been created for each submap symbol placed on your home submap. You can

Saving a Map 3-9

double-click on the submap symbols one at a time and add symbols as required to each of the submaps. If your map contains several levels of submaps, repeat the process for each level.

Saving a Map To save a map file with all of its submaps and symbol descriptions, choose Save from the File menu. This saves the map under its current name. To save the map to another name, choose Save As from the File menu.

Printing a Map You can print individual submaps. To print the displayed portion of the submap with all of its symbols, lines, connections, text notations, and background bitmaps, choose Print Submap from the File menu.

You can also print out a text list of all of the submaps in a map as well as the names and types of devices in the submaps. This list is useful to check your map. Choose Print Object List from the File menu.

A database file, openview.CSV is created in the OV directory everytime a layout is performed. This file can be read into database programs and used to generate reports of devices in the network submap.

Web Browser If a web page (HTML formatted data) is available for a selected device, the web browser commands will pass the URL locator for the page to a web browser. The web browser is normally configured at OpenView installation. The web browser can be selected or modified in the OVWIN.INI file. Information on the status of a device can be viewed, or its configuration settings can be modified using the browser. Refer to the online help for additional information.

Disabling the Map Editing Feature

You can disable OpenView's map editing to prevent accidental changes to maps.

Layout can still modify the map. The layout feature sets the map to protected mode while it is generating a new map. When the map is completed, it changes to unprotected mode. The map locking feature allows you to prevent accidental changes to maps. It does not provide data security.


To disable manual editing of a map, follow these steps:

1 Choose Protect Map from the Options menu.

A dialog box is displayed prompting you to enter a password. The password is case sensitive.

2 Enter a password.

3 Click OK.

The map editing feature is disabled and the editing status is displayed at the end of the Status Bar.

The locking feature is only meant to prevent accidental map changes by the supervisor. The operator and observer can never edit the map regardless of the Map Protect settings. It does not provide data security. If you forget the password, open the OVWIN.INI file and delete the Key= entry under [OpenView].

Map Toolbar and Commands

OpenView provides a toolbar and menu items for creating and modifying network maps. Each of these tools and commands are described below.

Applications can add new menus and commands to existing menus. Refer to your application documentation for specific functions.

Status Bar The status bar indicates the current selection and displays descriptive text for tool bar and menu selections. If you are not selecting a tool or menu command the field will display the last selected object's name

CH4-17

CH4-19

Map Toolbar and Commands 3-11

and type. It also shows the security level of the current user and whether the map is in protected (i.e., read-only) mode. See the section Disabling the Map Editing Feature in this chapter.

Toolbar OpenView displays a toolbar at the top of the main window.

The toolbar provides quick access to frequently used functions that allow you to create network maps.

The toolbar buttons are described in the following table.

Table 3-2 Toolbar Functions

CH4-21

CH4-22

Tool Description

Scissors Cut (same as in the Edit menu).

Camera Copy (same as in the Edit menu).

Paste Paste (same as in the Edit menu).

Eraser Delete (same as in the Edit menu).

Pencil Describe (same as in the Edit menu).

1:1 Zoom 1 (same as in the View menu).

1:2 Zoom 1/2 (same as in the View menu).



Home Submap Display the home submap (same as in the Window menu).

Previous Submap Display the previous submap (same as in the Window menu).

Alarm Bell Display the alarm log. Icon color reflects thehighest unacknowledged alarm.


Add Toolbox Choose Add from the Edit menu to display the toolbox with drawing functions. The Add Toolbox contains the following:

■ Selection Pointer

■ Text

■ Lines

■ Connections

■ Symbols (compound objects, computers, and components)

Click on the appropriate button to select the Text, Lines, Connections, or Symbols buttons. Selecting these buttons while holding the Ctrl key allows you to make multiple adds of a given symbol without returning to the Add Toolbox. Click on the Select Object pointer in the Add Toolbox to get out of the multiple add mode.

When you draw a map you can display and choose from various styles of text, lines, and symbols.

Applications that run under OpenView can add their own symbols. Refer to your application documentation for additional information. If symbols in the Display symbols list appear as question marks, they are probably symbols added by an application and have not been properly installed. Check for proper installation of applications that use these symbols.

CH4-23

Select objects

Add text

Add lines

Add connections

Add symbols

Display symbols

Choose text style

Choose line style

Choose symbol set

Choose symbol

Add Toolbox 3-13

Select Object The Select Object pointer button is used to restore the cursor to selection mode when in multi-add mode.

Text You can select from different combinations of size and style of text. Text is available in 8, 9, 10, 12, and 14 points. You can specify each size using regular, bold, or underline styles.

Lines andConnections

You can select lines in 8 thicknesses. Thin lines are available in five patterns, including solid. If you want the line to be attached (“connected” to a symbol) use the Connection button.

You can use different line types to represent different connections in your network. For example, use a thick line to represent a LAN and a thin line for connections from computers to the LAN.

Symbol The Symbol button allows you to add selected symbols to a submap. First select a symbol set, Compound Object, Computer, or Component. Then display a list of the available symbols for the set using the list button at the right of the field.

The Display Symbols button can be used to display the icons for a symbol set. When adding a symbol to a submap you can select the symbol from either the text list or the graphic list.

OpenView provides five Compound Object symbols: Submap, GoTo, Personal Computer, Medium Computer, and File Server. OpenView applications may add additional compound icons. A compound object icon can be opened with a double click. In general, symbols for Compound Objects are displayed with a “+” at the end of their names to help differentiate them from Computer and Component symbols.

OpenView stores names entered for compound objects using uppercase characters. OpenView also truncates these names to 15 characters.

The Submap symbol (shown as a small network) indicates another submap. The background of the Submap symbol displays the status color of the referenced submap. In a hierarchically structured map, the Submap symbol can be used to point to a lower level submap. Double clicking on the Submap symbol will cause the referenced submap to be displayed.


The GoTo symbol does not display status and can be used to reference any submap. Use the GoTo symbol to link any submaps where you do not want status information to pass between the submaps. Double clicking on the GoTo symbol will cause the referenced submap to be displayed.

Other symbols in the Compound Object category are used for devices that provide internal configuration information to OpenView. If a supporting application is installed, opening one of these could display hardware configuration and status, memory usage, disc space, or installed software.

There are several Computer symbols depicting large and medium computers, PCs, and various computer components. OpenView applications can add symbols to or delete symbols from the standard set.

The Component symbol set contains various network components such as hubs, routers, and multiplexers. OpenView applications can add symbols to or delete symbols from the standard set.

Selection Lists If you frequently make changes to a group of map objects, you can make a list of the objects to use as a group selection function. You can use this list to automatically select the objects to perform operations on them as a group. The effect is the same as if you had selected the objects manually.

Two list commands are available in the File menu: Load Selection List and Save Selection List As. For information about using the Selection List commands, refer to Chapter 4.

Extended Locate The Extended Locate command is in the Window Menu. Extended Locate can be used to find and display the submap containing a particular device or object symbol. It’s similar to Locate Object, but with more functionality.

Extended Locate 3-15

Table 3-3 Functions available in Extended Locate

Locate By These buttons allow you to choose the method of finding a device or object. You can search by Object Name, Network Address, Web Site, or MAC Address.

Select on Map This function selects the desired object on the map.

GoTo This function displays the submap containing the selected object. If multiple objects are selected from the scroll box window (lower right), then the submap containing the first object in the list is displayed. If multiple objects are selected from the upper left window, then the function will be disabled.

Delete Deletes the selected object from the map. If multiple objects are selected, then all selected will be deleted from the map. The deleted object(s) remain in the discovery database, and will still be added to the map if another layout is performed.

Options<< The Options button accesses additional search features.

All Submaps You can choose the submaps to searches.

All Object Types

You can choose the types of objects on which to perform searches.

Notepad You can search for notepad entries in objectdescriptions.

Network Address Types

You can specify which types of network addresses to use in the search.

Miscellaneous search tools

Lines & connections, Unique, Nameless and MacAddr Vendor Names.


4
MONITORING DEVICES ON THE NETWORK
OpenView provides several different ways that you can monitor the devices in your network. You can:

■ Customize the access parameters for devices on your network.

■ Poll network devices at set intervals to determine the functioning status of each device.

■ Monitor trap messages sent by network devices alerting you to changes in device status.

■ Configure how alarms are processed, displayed, recorded, and forwarded.

This chapter explains how to configure and use each of these monitoring features.

Figure 4-1 Monitoring devices

Device

OpenView

Applications

Polling

Alarms

Traps Log

Map

Audible alarms,forwarded alarms,triggering of programs

4-2 CHAPTER 4: MONITORING DEVICES ON THE NETWORK

Customizing Device Access

You can associate with a network address control information that is specific to that address. This information is stored in a database that is independent of which map is loaded. For example, you can enter the community name, set community name, and time-out values for devices. These values are used in polling, Autodiscovery, SNMP queries, and third party applications. Devices that you have not customized (devices not in the list) will use the system default values. Only customize the access for devices that require values different from the system default values.

To customize device access, choose Customize Device Access from the Options menu. The following dialog box appears:

The Customize Device Access dialog box lists the default settings for the selected device’s community names, retries and time-out values, and whether it is a proxy agent. A proxy agent is a device that acts on behalf of a device that does not have SNMP capabilities. The trap manager uses the Proxy Agent field.

To change values for any one of the devices listed, select a device and then click on Modify. The following dialog box appears:

CH5-01

Customizing Device Access 4-3

Type in the new values that you want to change and click OK. The values that you entered become the new values for the selected device. Note that the Community and Set Community passwords are case sensitive.

If you select Use Defaults and click OK, the entry for this device will be removed from the database because it is no longer an exception and will now use the default system settings.

To change the default values for devices that aren’t listed in the Network Addresses list (i.e., the device currently is using system default values), click on Add. The Add Device dialog box appears. Type in the network address and then change the values you want. Click OK. The address of the device will appear in the Network Addresses list. Note that if you don’t change any values, the network address will not appear in the list.

Ping The Ping function is used to determine if communication is possible with the selected objects. If the Ping is returned, then network communication (TCP/IP or IPX) is functioning correctly for the device. If the Ping does not return, it could mean that the network communication for the device is not functioning properly, the device being Pinged is down (or not turned on), or that the device is unreachable from your OpenView console.

The Ping command is in the Monitor menu. The Ping command can also be accessed with a right-click on any map object. If the object selected does not have a network address configured, an error message is displayed. Objects that normally would not have a network address

CH5-02


are Submap symbols, Lines, Text, etc. If no object is selected, an error is displayed.

Polling Network Devices

To poll network devices, you perform the following tasks:

■ Create a list of the devices that you want to poll

■ Set the polling parameters (optional)

■ Turn on polling

At any time, you can change the list of devices you want to poll. You can also change the current polling parameters for a specific device using the Configure Device Parameters dialog box. If you do not change the device polling parameters it will use the system defaults. To view the current polling list, choose View Polling List from Polling in the Monitor menu.

A tool bar icon has been added to indicate that polling is active. The symbol in the center of the button rotates when polling is active and is stationary when polling is stopped. You can access the polling menu by clicking on the polling button.

Creating a List ofDevices to Poll

You can poll any device in the map that has an IP or IPX address.

To add a device to poll, follow these steps:

1 Select the device(s) on the map that you want to poll.

(Shift-Click or Ctrl-Click can be used to select more than one device.) If you want to poll all of the devices in a submap, select the submap icon.

CH5-04

Polling Network Devices 4-5

2 Choose Add Device(s) from Polling in the Monitor menu.

The following dialog box appears. The network addresses for the devices that you selected appear in the dialog box.

If a device that you selected to poll has more than one address, a dialog box will ask you to select the address(es) that you want to poll.

3 Click OK.

The list of devices to poll is kept separately with each map. One map with device A may choose to poll the device, another map also showing device A may not poll the device.

Removing Devices toPoll

To remove devices from the polling list, follow these steps:

1 Select the devices on the map that you want removed from the polling list.

You can select a single device, multiple devices, or a submap.

2 Choose Remove Device(s) from Polling in the Monitor menu.

A message appears telling you how many devices were removed from the polling list.

You can also remove devices from the polling list using the Remove button in the View Polling List dialog box.

A shortcut for adding and deleting devices in the polling list is to save the selected devices as a Selection List. The list can then be retrieved using Load Selection List. See the discussion of Selection Lists that follows.

CH5-05


Selection Lists Some applications support operation on a group of objects. If you frequently make changes to a group of map objects, you can make a list of objects to use as a group selection function. You can use this list to automatically select the objects as a group to perform operations on them. The effect is the same as if you had selected the objects manually. Two list commands are available on the File menu: Load Selection List and Save Selection List.

Loading a SelectionList

Use the Load Selection List command to get a previously saved list. A dialog box will ask for the name of the list file to use. When you enter a file name, the objects listed in the file are automatically selected on your map.

Saving a SelectionList

To create a selection list:

1 Select a set of symbols and lines with a Shift click on each map object that you want in the list.

Each object that you select must have been described using the Describe command.

2 Use the Save Selection List As command to save the list to a file.

The default list file name is the current map name with the extension .OVL and is stored in the current map directory. In the future, when you wish to select this set of objects, use the Load Selection List command and specify the list file name.

Editing a SelectionList

To add or delete objects from an existing selection list:

1 Use the Load Selection List command and select the file containing the list that you want to edit.

The objects in the list will be selected on the map.

2 To add objects to the list, Shift click the new objects. To delete objects, Shift click on the objects that are already selected.

This will deselect the objects and delete them from the list.

CH5-08

Selection Lists 4-7

3 Use the Save Selection List As command to save the list to a file.

All map objects that are selected (highlighted), will be saved in the list.

Configuring SystemPolling Parameters

OpenView has preset default values that control the polling interval and determine what action to take when a device starts or stops functioning. Use system defaults to poll the most devices with the longest interval such as PC’s and printers. For large networks you might have to set longer intervals to keep from overloading the system.

To change the system default values, follow these steps:

1 Choose Configure System Defaults from Polling in the Monitor menu.

The following dialog box appears.

2 Select the desired device class.

3 To set the polling interval, enter the appropriate number of hours, minutes, or seconds in the Interval text boxes.

4 Select a severity level for the Device Down and Device Up conditions.

5 Select what types of action to take for the Device Down and Device Up conditions.

For more information about alarms, see the section, Configuring Alarms later in this chapter.

6 Click Apply

Configuring DeviceTypes

There are system defaults for six classes of device. OpenView uses the same predefined values for each of the device types within the device class. You can modify the default values for each device type in the

CH5-10


class. Use Configuring Parameters for Selected Devices to change the settings for a device at a specific address.

To view the settings for a device class:

1 Select a class.

2 Click options.

The Configure Polling System Defaults dialog box expands.

For each class of device there are several device types listed. For example, Network Devices includes bridges, hubs, and routers as device types within the class.

To change the settings for a device type:

1 Select a device class.

2 Click Options.

3 Select the device type.

4 Configure interval, etc.

The Use Defaults field for the changed device type will no longer be set to Yes. The default values for each device type in the class can be modified. If a device type does not use the default settings for the class, selecting the device type will display the custom settings.

Ch5-10a.gif

Selection Lists 4-9

To restore class default settings to a device type:

1 Select the device type.

2 Click on Use Defaults.

You can change the overall default settings for the entire class by selecting All Network Devices and then entering values for the polling Interval and Alarm actions.

ConfiguringParameters for

Selected Devices

You can override the system polling parameters for individual addresses. Use this for setting poll rates for those devices requiring shorter intervals such as routers, bridges, and hubs. Use longer intervals for remote devices.

To do this, follow these steps:

1 Select the desired device on the map and choose Configure Device Parameters from Polling in the Monitor menu.


2 If you did not select a device on the map, enter the device address that you want to exempt from the system polling values.

Note that you don’t have to enter the name.

3 Change the values that you want for the polling interval timing, severity, or alarm action.

4 Click Save to save the new values. Click Use Defaults to restore the system default values.

CH5-12


Turning Polling Onand Off

To start the polling process, choose Start Polling from Polling in the Monitor menu.

To stop the polling process, choose Stop Polling from Polling in the Monitor menu.

AutoPolling When OpenView starts, it will automatically discover the devices in your network. It will then create a map of the discovered devices. All devices in the map are automatically added to the polling list. The devices in the polling list will then be polled based on the default polling settings.

To configure automatic polling of discovered devices, choose Customize HP OpenView from the Options Menu.


To turn automatic polling ON, select Poll after each layout.

To turn automatic polling OFF, deselect Poll after each layout.

Monitoring Traps from Network Devices

Traps are specific types of messages that are generated by some devices to indicate a change in their status. When a device is installed on the network part of its installation procedure is to enter the address of a management console where these traps are to be sent. Refer to the device installation and configuration documentation and set the trap address to the network address of the OpenView console.

Monitoring Traps from Network Devices 4-11

OpenView automatically logs an informational alarm for each trap it receives. You can change OpenView's default response to traps to sound an alarm, change color of the map symbol for the device sending the trap, or enter the trap in the alarm log. You can also change the default response to ignore traps from some or all devices, or configure one trap to auto-acknowledge another one when it is received.

Each device class (hub type 1, hub type 2, router, server, etc.) can be assigned a different set of default and customized trap responses. Initially the default trap response for each device class is set to the OpenView system default response. You can change the default response for each device class. In addition, for each device class you can create a customized response for any trap that might be received from a device in that class.

Customizing Traps Customizing traps consists of:

■ Selecting the device classes for which you want to customize trap alarm actions

■ Selecting or entering the trap IDs for the traps you want to configure

■ Choosing what alarm actions to take when OpenView receives the trap

Some device vendors supply trap definition files (.TDF) that can be used to automate trap configuration. If trap definition files have been installed, you can load the predefined traps using the Load Traps button. When a device class has been selected, any predefined traps for this device class will be displayed in the Customized Traps list.

To customize trap alarms, you use the Customize Traps dialog box. Choose

Customize Traps in the Monitor menu. The following dialog box appears.


Selecting a DeviceClass

To select a device class to change the default trap response, follow these steps:

1 Click ADD.

The following dialog box appears:

2 Select the device class and click OK.

The class name and Enterprise (ObjectID) appears in the Device Class Name list.

To remove a device class from the list, select the device class and click Delete.

Ignoring Traps By default, all traps are logged according to the actions configured for the system. If you have another application managing traps for a

CH5-14

CH5-17


particular class of device, you may want OpenView to ignore traps it receives and let the application maintain the device status.

To ignore incoming traps, select the device class whose traps are to be ignored and click Ignore. “Ignore” appears in the Flag column next to the device class name.

To turn off Ignore, click Include.

Specifying Traps for aDevice Class

You can create a list of the traps that OpenView will respond to for a specific device class. The list of traps will be displayed in the Customized Traps list box of the Customize Traps dialog box. For a list of traps for a particular device see the manufacturer’s documentation.

CH5-19


To add a trap for a device class:

1 Click Add. The following dialog box appears:

2 Select a trap type.

3 Type the name (Generic) or the number (Specific) of the trap in the appropriate field.

4 Select the desired Alarm Action and Severity.

5 Type in a Description.

6 Set desired Automatic Acknowledge Alarms.

7 Click OK.

The type of trap you selected or entered appears in the Customized Traps list in the Customize Trap Alarms dialog box.

Choosing Trap AlarmActions

You can choose to update the map status (change color of map symbols), sound a bell, or log an alarm entry when a trap is received. To select any of these options, click on the appropriate Alarm Actions check box(es). To set the severity level you want for the alarm, select the option you want from the Severity list. For the description and extended description fields, you can specify information from the trap packet to be displayed in the Alarm Log.

■ To select the OpenView response to a trap in the Add Trap dialog box:

CH5-22


1 Choose the Severity of the named trap.

2 Choose the desired alarm actions (Update map, Sound Bell, Log, etc.).

3 Type in a Description.

4 Set desired Automatic Acknowledge Alarms.

5 Click OK.

Description FieldVariable Substitution

Syntax

You can specify how information from the trap packet is displayed in the Description and Extended Description fields using field variables. The extended description allows you to add additional information to the alarm message. The descriptions are entered in the Add Traps dialog box in the following section.

The following table lists the field variables and descriptions.

CH5-23

Alarm Actions


Table 4-1 Field Variable Table

Loading Traps You can select a trap definition file (.TDF) from which you can select a device class. In the Customize Trap Alarms dialog box click the Load button. Select the desired trap definition file and click OK. The traps and their alarm actions for the selected devices class are copied to the trap database (trapmgr.ini).

AutomaticallyAcknowledging

Alarms Generatedby Traps

The Acknowledge on Matching Trap and Variable text box allows you to clear a trap when a new specified trap is received. The original trap is moved from the current alarm log to the history alarm log. A variable in the trap packed that holds the network object’s name can be selected to match the subobject field in the alarm log. This is to make sure that a trap that clears an alarm is referring to a particular device.

If the device uses a variable in the trap message to more exactly specify which device subcomponent is sending the trap, you can require the

Variables Descriptions

\n newline

\t tab

$C trap community string

$E enterprise, represented as a text string if possible

$e enterprise, represented as an object ID string of numbers

$A name of device that sent the trap. If this device is not rep-resent by a symbol in the map, this field defaults to “addressed” concatenated with the device address.

$G generic trap id number

$S specific trap id number

$T timestamp (time since device was last restarted)

$* print all variables in the trap

$# number of variables in the trap

$$ print the $ character

$n print the value of the nth variable in the trap, where n is the variable sequence number starting at 1 used to refer-ence subobjects in a device.

$-n print the nth variable as a “name-type:value” string, where n is the variable sequence number starting at 1 used to reference subobjects in a device.

$+n print the nth variable as a “name:value” string, where n is the variable sequence number starting at 1 used to refer-ence subobjects in a device.

Managing Alarms 4-17

value of this variable to match in the original and acknowledging traps. The variable is used to match the value in the subobject field of the trap message. For example if the trap is from a hub with 16 ports, the trap may contain a value in the subobject field to specify which port caused the trap. Using the variable in the acknowledging trap specification will ensure that if port 7 creates a trap by going down, it will only be cleared by a trap from port 7 going up. This setting will be displayed in the subobject field in the alarm log.

If the subobject field is not used, set it to NONE. Otherwise, set it to the ordinal value of the field (i.e. 1 for the first variable in the trap packet, 2 for the second, etc.).

Managing Alarms Alarms generated by applications, traps, or polling are managed through the map, alarm log, and alarm forwarding functions.

Selecting MapStatus Options

The map symbol of a device is displayed in the color that represents the device status.

To display the available status colors, choose Status Legend from the Monitor menu. The table below lists the status levels and their colors.

Table 4-2 Map Status Colors Legend

CH5-25


The colors displayed in the alarm log are slightly different than those used on maps.

Status Propagation You can select the way device status is propagated to higher submap levels using Customize Alarms in the Options menu. Status propagation can be set to:

■ Do not pass status up

■ Pass status up one level

■ Pass status up all levels

State Map Alarm Log

Description

Critical Red Red The device is unavailable. It may be down or in a critical state.

Major Dark Red

Red There is a problem with the device. Some degradation of function exists.

Minor Orange Yellow A non critical condition has been reported, or the device is in a degraded state.

Warning Yellow Yellow There is a problem with the device. No degradation of function exists.

Marginal Mustard Yellow The device is approaching shutdown or malfunction.

Informational Magenta Magenta An informational message about this device has been sent by an application.

Disabled Cyan Cyan The device is down.

Unmanaged Wheat White The device is not managed by an OpenView application.

Normal Green Green The device is up and working properly.

Unknown Blue Cyan OpenView has no information on the device’s state.


Figure 4-2 Map set to propagate alarms up all levels

Normally, you would select to propagate up all levels. Then, if your home submap contains a submap symbol for each submap in the next lower level in the map, you can check your network's overall status from the home submap. If a submap represents several devices, its submap symbol on the home submap will display the most severe device status for the lower submap. (Note that the GoTo submap symbol does not propagate status.)

You can examine alarms using two methods:

■ Using the map, click on the submap symbol showing an alarm status and “walk” down the submap levels until you display the submap containing the device that generated the alarm

World - “Home Submap”

USA Japan

Europe

U.S.A. Europe Japan

San Jose Dallas New York

= Normal

= Warning

= Critical


Figure 4-3 Submap containing the device that generated the alarm

■ Click Alarm in the tool bar or choose Alarm Log from the Monitor menu to display the Alarm Log. Select the alarm that you want to check and then click GoTo to display the submap containing the device that generated the alarm.

■ Click on the map object using the right mouse button to display the submap containing the device that generated the alarm.

■ Click Alarm in the tool bar or choose Alarm Log from the Monitor menu to display the Alarm Log. Select the alarm that you want to check and then click GoTo to display the submap containing the device that generated the alarm.

CH5-34


■ Click on the map object using the right mouse button to display the submap containing the device that generated the alarm.

Configuring Alarms Applications monitor the state of network devices and processes and can trigger alarms. The alarms alert network managers of changes in the status of a device or group of devices. When an application detects a change in a device status, it can request OpenView to do one or more of the following:

■ Change the device symbol to the new status color

■ Make an entry in the alarm log

■ Forward an alarm to another management console

■ Sound an alarm

■ Run a program

Regardless of whether OpenView is an active window or not, if a device symbol changes color to red, yellow, or magenta, the Alarm icon in the tool bar changes color and displays the most severe unacknowledged alarm in the log. Alarms of all levels are recorded in the Alarm Log.

CH35A

CH5-35

CH35B


Not all applications monitor device status. Check your device and application documentation to find if a particular network device indicates its status.

Viewing Alarms To display the Alarm Log, click on the Alarm button in the toolbar or choose Alarm Log from the Monitor menu. The Alarm Log lists all alarms that have occurred since the last time OpenView was restarted. You can display either Current (unacknowledged) alarms or History (acknowledged) alarms.

You can resize the columns in the Alarm log window by dragging the “|” character in the column labels with the mouse.

You can list the alarms either by the order received or severity using the Sort by controls in Customize Alarms in the Options menu.

Select Time as the sort criteria if you want the alarms to be listed in chronological order with the most recent alarm at the top of the list.

CH5-30

CH5-37


Select Status as the sort criteria if you want the alarms to be listed by the severity of the alarms. Critical alarms are grouped before warning alarms, and alarms within status groups are displayed in chronological order.

The Alarm Log can display up to 900 alarms. Refer to the next section Selecting Alarms for Display for instructions on how to select the alarms displayed.

Selecting Alarms forDisplay

You can display selected groups of alarms from the alarm log. Alarm displays can be limited to a type of device, specific device, or class of alarm severity. To configure an alarm display, click on Filters in the Alarm Log window. This will display the Alarm Log Filters dialog box.

The Alarm Log Filters dialog box contains the following entries:

■ Alarm type (specific alarm name)

■ Object Type (e.g. Personal Computer)

■ Object Name (e.g. PC #21)

■ Object Status (e.g. Critical)

Alarm type – This field allows you to select the alarm message type to be displayed. If you have several OpenView applications, each has its own set of alarms and associated messages. Refer to your application documentation for additional information. To select an alarm type, display the alarm type list and select one or all alarm types from the list. The default is All Alarms.

CH5-38


Object Type – This field allows you to select the types of devices (e.g., hubs, PCs, etc.), whose alarms you want to display. To select an object type, display the list of object types and select one or all object types. The default is All Object Types.

Object Name – This field allows you to select individual devices (e.g., hub #1, PC # 3, etc.) whose alarms you want to display. To select object names, display the list of object names and select one or all names. The default is All Objects.

In addition to specifying map objects by their names, you can also report on specific sub components in a device. To do this enter the desired Subcomponent or Node numbers for the subcomponent devices.

Object Status – This field allows you to select the types of alarms you want to display. To select status type, display the list of status types and select one or all status types. The default is Any Status.

Acknowledging andDeleting Alarms

To acknowledge or “clear” an alarm, select the alarm in the current list, and click Acknowledge. (Note that this does not delete the alarm entry. It moves the entry from the current to the history portion of the alarm log.) The color of the Alarm button on the tool bar is updated to the status of the most severe alarm remaining. The Acknowledge button is disabled unless an alarm is selected. When the last alarm in the list is acknowledged, the Acknowledge button is grayed to indicate that there are no more unacknowledged alarms. You can select multiple alarms to be cleared using Ctrl - click.

To acknowledge all alarms in the list, click Acknowledge All.

To delete all of the alarms from the history log, click on Delete All. To delete selected alarms from the history log, click on Delete.

To display a submap showing the device that generated an alarm, select the alarm in the list, then click GoTo. If possible, the device will be shown in the middle of the map window. If there are multiple instances of the device in the map, a dialog box is displayed to allow you to select the desired submap. If the multiple instances are on different submaps a dialog box will be displayed asking you which submap you wish to use to view the device. If the device does not exist in the map,

Configuring Alarm Processing 4-25

an error message is displayed. The GoTo button is disabled unless an alarm is selected.

If there is additional information about a selected alarm the More Info button will be enabled. To display the additional information, click on it to view the additional information in a separate dialog box.

■ To close the Alarm Log window, click Close.

The alarm log can hold a large number of alarms and is limited primarily by the amount of disk space available. The number of entries in the log that can be displayed is limited by the amount of RAM memory available. You can configure OpenView to delete acknowledged alarms after a set number of days using Customize Alarms in the Options menu. Normally this will be sufficient to maintain a manageable log. If it is necessary to save the alarm data beyond the configured date, you can copy the contents of the alarm database files to archive files.

Configuring Alarm Processing

You can control the way OpenView processes alarm information. The major configuration groups for alarms are:

■ Alarms (general)

■ Alarm Sound

■ Status Propagation

■ Alarm Forwarding

To set the alarm options, choose Customize Alarms from the Options menu to display the following dialog box:

CH5-45


General AlarmSettings

The general alarm settings include:

■ The frequency at which multiple alarms are recognized

■ The length of time that acknowledged alarms are stored in the Alarm Log

■ Whether alarms are displayed by time or status level in the Alarm Log window.

Frequency – This setting is used to prevent multiple alarms of the same state from the same device. Duplicate alarms will be ignored if they occur within the specified time period. The default time is 0 seconds. A duplicate alarm occurring after this time will generate a new entry in the alarm log.

Delete After – This field is used to delete acknowledged alarms from the alarm database after the specified number of days. When OpenView is started and at midnight (if OpenView is running) any acknowledged alarms exceeding this time will be deleted from the database.

Sort By – This field selects whether the alarm log displays alarms in order received (most recent first) or by order of severity, i.e. most critical alarms first. Alarms of the same severity are ordered by time. Note that the color of the Alarm button in the toolbar and the color of an iconized Alarm Log or submap will show the status of the most severe unacknowledged alarmregardless of the Sort By setting.

Alarm SoundSettings

Alarm Sound – The settings control the sounds generated by an alarm. Note that no sound will be generated regardless of the setting unless the application managing a particular device requests an audible alarm. The alarm sound settings allow you to control:

■ whether sounds are enabled

■ whether a sound alarm is generated only once

■ if an alarm is to be repeated, the repeat rate for each status of alarm

You must also have an appropriate sound driver program installed.

Disable Sounds – This turns off sound for all alarms, Sound Once will play the appropriate alarm sound when the alarm is generated. The


Repeat setting will play reminder sound every x minutes until the alarm is acknowledged. The sound used for the Repeat setting will be that for the most severe uncleared alarm at or above the selected status level. For the example shown, a sound is generated whenever an alarm is generated and a sound will be generated every minute if there are any unacknowledged Major or Critical alarms.

Alarm SoundConfiguration

OpenView can generate a sound when a device changes status, and a different sound can be generated for each status level. If you have a sound card and drivers installed, you can use the Sound dialog in the Windows Control Panel to associate OpenView alarms with any Windows .wav wave file. Otherwise, the system beep will be used for all alarm sounds.

Alarm StatusPropagation

The Status Propagation field controls how alarms are passed between submap levels. The Status Propagation setting allows you to select from one of following three status propagation methods:

■ do not propagate status

■ propagate status to the next higher submap only

■ propagate status to all higher submaps

If status is not passed up, submap symbols at higher levels remain unchanged when devices under them change status. If status passes up one level, the submap symbols are displayed with the color of the most severe status of all devices on the level below them. If status passes up all levels, submap symbols are displayed with the color of the most severe status of all devices contained on any level below them. When a submap is minimized, its icon will be the color of the most severe status

CH5-49


contained in the submap and will propagate status based on the Status Propagation configuration.

Alarm Forwarding Alarms can be forwarded to another console. This is useful in complex networks where there is a hierarchical network management scheme using multiple consoles. A console monitoring a local network can pass status information on devices in its network to a master console. Selected alarms at the local console can be converted to traps and sent to another console.

To forward alarms you must configure the following:

■ The address of the console to receive the trap

■ The map objects whose alarms are to be forwarded

■ The types of alarms to be forwarded

CH5-50


The alarm forwarding is configured using the Alarm Forwarding box of the Customize Alarms dialog box.

1 Enter the address of the console where the forwarded alarms are to be sent.

2 Select the map objects whose status is to be forwarded.

If you do not want alarms for all objects on your map to be forwarded, click on the Select button. This will cause a list of map objects to be displayed. You can then select the desired objects.

3 Select the status levels that are to be forwarded.

4 Click on OK in the main Customize Alarms dialog box.

This will save your alarm forwarding information in the OVWIN.INI file.

In the example shown above, two devices, Lab #21 and Lab #22 will forward alarms of Major or Critical status to an OpenView console at address 122.127.120.5.

Running Programs OpenView can run an MS-DOS or Windows program when an alarm is generated. You can select what program is run based on the status of the alarm. Information about the alarm can be passed as command line arguments to the program. You control the program trigger function by making entries in the ovwin.ini file before running OpenView.

(Note that if the alarm is generated by an application program, the application program must have enabled programs to be run in response to the alarm. Refer to documentation for the application program responsible for generating the alarm. Program execution is enabled for

CH5-46

CH5-47


alarms generated by the polling and trap management features of OpenView.)

To run a program for a particular level of alarm, add an entry to the [OVAlarm] section of ovwin.ini as follows:

RunCritical=<command line>RunMajor=<command line>RunMinor=<command line>RunWarning=<command line>RunMarginal=<command line>RunNormal=<command line>RunDisabled=<command line>RunUnknown=<command line>RunInformational=<command line>RunUnmanaged=<command line>

where <command line> is the program name and parameters.

For example: RunCritical=write.exe readme.wri will run MS Write and display the file readme.wri.

OpenView provides alarm information in the following command line variables:

The command line can include these variables to provide more information about the alarm.

For example, if the entry in the OVWIN.INI file for RunCritical was:

RunCritical=prog.exe %t - %o - %a

then a critical alarm on Brian's PC at 2:30 on Feb 16 would execute the following:

%a Alarm text %o Object name

%i Alarm type ID %p Alarm application ID

%m More info field %s Subobject number

%n Node number %t Time of alarm

%y Object type


prog.exe Tue Feb 16 14:30:05 1993 - Brian's PC - Power Supply Overheating

DDE Commands In addition to running a program with a command line string, the alarm system can also pass information to another Windows application using DDE. Refer to Microsoft Windows documentation for more information on DDE operation. DDE exchanges are indicated using the “>” character after the “=” sign in the Run entry in the ovwin.ini file. DDE Run commands use the following format:

RunCritical => <program>,<service>,<topic>;<command>

When an alarm occurs, OpenView will attempt to establish a DDE conversation with the specified service and topic. If the connection to the service cannot be established, the indicated program will be run and another attempt made to establish the conversation. Once established, OpenView will send a DDE Execute message of command, and will then terminate the conversation.

Paging Program OpenView ships with the paging program Notify! Connect from Ex Machina Corporation. This program sends a paging message to a pager when a specified alarm goes off.

For example, Notify! Connect supports the DDE NOTIFYservice and SendPage topic. It sends a pager message when sent a command of the form Username, Message. The ovwin.ini entry would be as follows:

RunCritical => c:\ov\notify\connect.exe,NOTIFY,SendPage;OpenView,Critical Alarm: %o - %a

This will send the following pager message to OpenView when a critical alarm occurs:

Critical Alarm: Brian's PC - Power Supply Overheating

For more information about Notify! Connect, refer to the Notify! Connect documentation.

Alarm Database Every alarm is recorded in an alarm database. Each entry contains the date and time, status, device name, and device type of the alarm.

The alarm log is saved in Borland Paradox database format. The files are named ovalins.* and are stored in the OpenView directory (\OV). You


can copy these files for archival purposes and save alarm history information beyond the deletion date. You can also use a Paradox database application to access the database and create reports or manipulate the archived files.

CAUTION: Do not make changes directly to the OVALINS.* files as this can cause improper operation of OpenView.

The database uses one record for each alarm with a primary key on time and a secondary key on status. The record structure is as follows:

Table 4-3 Database Records

DMI Manager The DMI Manager in the Control Menu allows you to query DMI capable PCs to determine their capabilities, configuration, and status. The interface and dialogs for the DMI Manager are very similar to those of the SNMP Manager. The variables that can be accessed are defined by the DMTF (Desktop Management Task Force). You do not need to compile sets of variables for each device type. A given device type may not support all of the DMI variables. Additional information on the DMI Manager is given in the online help.

Field Format Description

key number Paradox database key, combination of time and object ID.

date date Date at which the alarm occurred.

hours time Hour at which the alarm occurred.

minutes time Minute at which the alarm occurred.

seconds time Second at which the alarm occurred.

severity number Severity of alarm, Critical=10, ..., Unmanaged=1.

application ID number Application that generated the alarm.

device class number Device class.

not used - -

open/cleared number Alarm state, Open=0, Cleared=1.

device type number Device symbol number.

device name 64 characters Name of the map object that generated the alarm.

subcomponent number Subcomponent number or -1 if not used.

node number Part number of subcomponent or -1 if not used.

status number Current status.

message 64 characters Alarm text displayed for this alarm.

extended description blob text Extended description of a field, activated by the More Info button.

DMI Manager 4-33

HP Top Tools HP TopTools is a management tool for DMI (Desktop Management Interface) capable PC’s on your network. Select DMI PC objects on the map to retrieve system and tattoo information about the PC and remotely configure BIOS parameters and security features on the selected PC. For more information, run HP Top Tools and refer to the online help. (Refer to the DMI Manager in the Control Menu for additional information.)


5
MANAGING SNMP NETWORK DEVICES
The SNMP Version 1 network devices store information about themselves in a Management Information Base (MIB). A MIB contains variables that describe the characteristics and current state of a network device. The SNMP Manager can access this information and control network devices. that support SNMP.

You can manage an SNMP device by querying or setting its MIB variables. The SNMP Manager supports all Internet MIB-II variables and can be extended to support other MIBs. Operations on MIB-II variables, such as egp and transmission, will not return values from devices supporting only MIB-I.

In order to manage or query an SNMP device, you must log in as a supervisor or operator.

This chapter provides information about how to define, select and display the query results as a table or graph. It also tells you how to manage the SNMP database.

The OpenView SNMP Manager uses information from MIB files provided by network device manufacturers to build its own database. This database tells the SNMP Manager what device variables are available to query. If you are not familiar with MIBs you should read the section Managing the SNMP Manager Database later in this chapter.

Defining a Query OpenView allows you to generate tables or graphs about information available in a device's MIB database. To define a query, you select a device and then select the variables that you want to query.

5-2 CHAPTER 5: MANAGING SNMP NETWORK DEVICES

To define a query, choose Define Query from SNMP Manager in the Control menu. The following dialog box appears:

To select a device to query you must supply the network address. If an object is selected on the map, its device name and network address will appear in the Device fields.

To select a device to query, use one of the following procedures:

■ Select a device from your map before you open the SNMP Manager.

■ Click on the Name field or use the list button to view the list of all devices configured in your current map. You can then scroll through the list to select the desired device. (If the list of devices is long, some may not be displayed. You will then need to select the device from the map or type in the network address.)

■ Type the first letter of the device name in the name field. The device list from the current map automatically appears and jumps to the first entry starting with that letter. Pressing that letter repeatedly scrolls through the list of all devices starting with that letter.

Once the device name is selected, the network address, as configured for the device in your map, appears in the Network Address field. If no address was configured in the map, type the network address into the field. The SNMP Manager uses the network address, not the device name, to perform the actual query.

CH6-03

Defining a Query 5-3

You can also select a device when you only have the network address. You can use this method to access a device that is not part of your current map:

■ Type in the network address in the Network Address field. The network address does not have to be associated with the current map. The device name will be blank. Addresses must be in IP format (123.123.123.123) or IPX format (12345678-123456789012).

Selecting Variables toQuery

The accessible SNMP variables are listed in the Variables box and may come from various MIBs. An extensive set comes with OpenView. Applications installed into OpenView may have added their own MIBs to the list. You may also use the MIB compiler to add MIBs.

The variables are displayed in a tree fashion with the MIB-II level displayed as a default. The following map will help you navigate through the tree. Additional information about the map and compiling MIBs can be found in the MIB Maps section of this chapter.

CH6-04


Figure 5-1 MIB variables tree

Moving Around theVariable Tree

To move around the variable tree, follow these steps:

1 Select the group variable you want to query.

For example, select [system].

2 To move up the tree, click on Up (this would move you to mib-2).

3 To move down the tree, click on Down (or double-click on the variable name).

internet

iso

org

dod

directory mgmt experimental private

mib-2

system interfaces . . .

enterprises

Default level

CH6-05

Defining a Query 5-5

Entries in the variables list are displayed using the following format:

Table 5-1 Variables List

If you select a group variable to query, all variables in that group will be part of that query. Queries can be for a single table variable (for example, {atTable}) several values from a given table, or one or more non-table variables (ipInReceives). If an SNMP table variable is selected, no other variable may be selected.

Individual values (columns) may be selected for an SNMP table by clicking on the Down button to move down the tree below the table and entry definitions to the individual column variables. You may select multiple column table variables and then click on Add to add these to the query. In this case, any previously selected variables are removed from the selection list, as only columns within a single table may be queried.

Selecting a Variableto Use in the Query

To select a variable to use in the query, follow these steps:

1 In the Available variables box, click on a single variable you want, or ctrl-click to highlight more than one variable.

2 Click Add.

The variable name will move into the Selected Variables box.

Removing a VariableFrom the Query List

To remove a variable from the query list, follow these steps:

1 In the Selected variables box, highlight the variable you want to remove.

2 Click Remove.

It disappears from the Selected Variables box.

Format Description

[square brackets] denote a group that contains additional variables

{curly braces} denote SNMP tables

“double quotes” denote textual values


Variable Descriptions When you highlight a variable, the corresponding description is displayed in the Description box. For example, the description for ifSpeed ([interfaces,], {if Table},[ifEntry]) would be as shown.

.

The Description box displays information about the variable highlighted in the Available or Selected variables boxes. This information uses the standard format for SNMP object identifiers (OID 1.2.3) and an associated description.

Saving a Query You can save a query so that you can query a selected device in the future or use it as a template for creating other queries.

To save a query, follow these steps:

1 Make sure all of the information you want to save has been entered into the Define Query window.

You should perform the query to make sure it generates the expected report.

2 Click on Save.

The following window is displayed.

3 In the Name field, type in a filename of up to 8 characters.

CH6-09

CH6-12

Selecting a Query 5-7

Do not enter a file extension – OpenView will append the .OVQ file extension when the file is saved.

4 If you want, you may use the Description field to describe the saved query.

This is especially helpful where the query has a specific use in your environment or where the query is to be used by others.

5 Make your choice in the check box.

If this box is checked, the next time you start OpenView, the query is listed in the menu under the SNMP Manager command. There is no limit to the number of queries that can be saved.

6 Click OK.

To perform, edit, or delete saved queries, choose Select Query from SNMP Manager in the Control menu. The queries are stored as separate files with the .OVQ extension in the OpenView directory.

Selecting a Query Selecting a query allows you to perform, edit, or delete the query.

To select a query, follow these steps:

1 Choose Select Query from SNMP Manager in the Control menu.


CH6-14


2 Highlight a saved query from the list in the Query box.

A description of the query appears in the Description box.

3 If you want, change the device name and address in the Device box.

4 Click on the appropriate function listed below for the action you want:

Table 5-2 Select Query Functions

Removing a Queryfrom the Menu

Since there is a limit of nine queries that are listed in the menu, you may want to remove a query from the menu commands.

Removing the query from the menu does not delete the query. To delete the query, select the query and click on Delete in the Select Query dialog box. See the previous section, Selecting a Query for information.

CH6-16

Button Description

Perform Executes the Query.

Edit Opens the Define Query window and inserts the query selected in Select Query. Modifications can be made and saved under the same or a new name.

Delete Deletes the query file and all references to the query.

New Opens a blank Define Query window.

CH6-14

Displaying SNMP Query Results 5-9

To remove a query from the menu, follow these steps:

1 In the Select Query dialog box, select a query in the query box.

2 Click on Edit.

The Define Query window is displayed.

3 Click on Save.

The Save Query window is displayed.

4 Remove the x in Display in menu next session by clicking on the check box.

5 Click on OK.

6 Close the Define Query window.

The menu change takes effect when you restart OpenView. (Exit OpenView and restart.)

Displaying SNMP Query Results

After you select the devices and variables you want to query, you can display the query results as a table or a graph. This section describes how to display query results as a table.

To choose the table or graph display option, select Define Query from SNMP Manager in the Control menu.

CH6-17

CH6-18


Displaying a Queryas a Table

Table queries can be for a single table variable (a table variable is displayed in {curly braces} in the variable list), for one or more non-table variables.

The format of the table generated varies, as follows:

■ If the query contains an SNMP table, the variable names will be displayed across the top of the table. There will be numbered rows below the heading. You can scroll through the rows, but cannot add or delete rows.

■ If the query does not contain an SNMP table, the values are listed in scalar format. Any group that you request in the query will be expanded to list individual variables.

Values within a table may appear as strings, integers, network addresses, or object names displayed in 1.2.3 notation. Other data, such as a MAC address, will appear in hexadecimal format (for example: 01 F3 07).

OpenView supports a maximum of 999 rows in each table. If your computer doesn’t have enough memory, the table may not be able to reach this limit. To minimize network traffic and memory requirements, select only the columns that you want to display. For information about how to select specific columns, see the example under Performing a Query.

After selecting to display your query results as a table, click on Options in the Display section of the Define Query dialog or Table dialog box. Then set the polling interval and enter the Community and Set Community names.

Figure 5-2 Table format query options dialog

CH6-19


Table 5-3 Table Format Query Options

To permanently set community values, choose Customize Device Access from the Options menu.

Performing a Query

After you enter the appropriate information for the device, variable, and options, click on Perform to execute the query. If a polling value other than zero was set, the table or graph will be updated periodically.

Example 1: Displaying an SNMP Table Variable

The following screen shows a sample query with results to be displayed as a table. The {ifTable} variable is selected. Since the selected variable is an SNMP table, it is the only variable selected.

When you select the {ifTable} variable, you have two options:

■ You can display the {ifTable} variable with a column for every variable in the table.

■ You can display a subset of the {ifTable} variables. To do this, click on {ifTable} in the Available box and then click on the Down button. [ifentry] appears, click on the Down button again. A list of column names appears. To get a description, click on a column name. To add one or more column names to the Selected box, click on one column name or Ctrl-click to select multiple column names,

Command Description

Polling Polling sets the number of seconds between updates when a query is performed.

For example, if polling is set to 5, once the query is per-formed, the data will be updated every 5 seconds. Polling can be set from 0 to 6000 seconds.

A zero (0) means polling takes place only once when the Per-form or Start button is pressed.

Community Community is the name used by an SNMP device to restrict access to MIB variables. Entering a valid community name gives you read-only access to MIB variables.

Set Community Set Community is the name used by an SNMP device to restrict access to device MIB variables. Entering a valid Set Community name gives you read and write access to device MIB variables.


and then click on Add. When you perform a query, only the selected columns appear in the table.

For this example, polling was set to zero so that the polling only occurs once. If polling were set to 10 seconds, the values in the table would be updated from the device every 10 seconds while this window is displayed on the screen.

Performing this query results in the following table:

CH6-20

CH6-21


Table 5-4 Table Display Options

Example 2: Displaying Non SNMP Table Variables

The following screen also shows a sample query with results to be displayed as a table. The variables selected do not include an SNMP table, so multiple variables can be selected.

Button Description

Start Polls the device. The button will change to STOP until the poll is completed or until pressed again (which cancels the polling). If the polling time is set to anything other than zero, the polling will con-tinue until the STOP button is pressed.

Set Allows a variable's value to be changed if the device permits the value to be changed.

Copy Copies selected cells from the table to the clipboard in tab delimited format. You can paste this information into other applications, such as word processors, spreadsheets, and databases. The variable names corresponding to the selected cells are also included on the clipboard.

Log Allows the current data to be saved to a named file in comma delimited format, replacing the contents of an existing file. Each time you log new data obtained by polling, the log file is appended.

The log file includes the name and address of the logged device followed by a blank line, the names of the variables logged, and a time stamp.

Options Allows you to set the polling rate and community.


Multi-variable results displayed in table form:

Displaying a Queryas a Graph

If single value variables are selected, you can view your query results as a graph. After selecting to display your query results as a graph, you can select several options with the Options button in the Display box.

Table 5-5 Graph Display Options

CH6-24

CH6-25

Command Description

Polling Polling sets the number of seconds between updates when a query is performed. For example, if polling is set to 5, once the query is performed, the data will be updated every 5 seconds. Polling can be set from 0 to 6000 seconds.

A zero (0) means polling takes place only once when the Perform or Start button is pressed. A non-zero value will plot the variables against time.

Samples You may set a sample size when displaying the query as a graph and polling is set to one or greater. For example, if the sample size is set to 10 (the default), the graph will display the last ten sample points – one sample point for each poll.


Performing the Query

As with a table, enter the information into the Define Query window, then click on Perform to execute the query. In this case, a graph will be displayed on the screen. If you set a polling value other than zero, the graph will be updated periodically.

Table 5-6 Graph Display Options

Example 3: Displaying a Query as a Graph

Display variable 1.3.6.1.2.1.4.9 (ipINDelivers). By selecting the Options button in the Display box, a polling rate and a sample size can be set.

Community Community is the name used by an SNMP device to restrict access to MIB vari-ables. It is often used as a password and is obtained from your network manager.

Graph Type Select from several different graph types.

Graph Style Select from a variety of presentation styles based on the Graph Type selected.

Grid You can add a grid to the graph. No grid is the default.

Legend You can add a legend to the graph. Having a legend is the default.

Print Color If you have a color printer, you can print the graph in color. No color is the default (output is shades of gray). NOTE: The Print option is available after the Perform button is pressed.

Function Description

Start Polls the device. The button will change to STOP until the poll is completed or until pressed again (which cancels the polling). If the polling time is set to any-thing other than zero, the polling will continue at its designated interval until the STOP button is pressed.

Print Prints the graph. If you have a color printer, select Print Color from the options button.

Copy Copies the entire graph as a bitmap to the clipboard. You can paste it into drawing programs or word processors.

Log Allows the current data to be saved to a named file in comma delimited format, replacing the contents of an existing file. Each time you log new data obtained by polling, the log file is appended.

The log file includes the name and address of the logged device followed by a blank line, the names of the variables logged, and a time stamp.


In this example, we set polling to 10 seconds and the sample size to 5. .

The type of graph is set to 3D Bar Chart

Click on Perform to generate the graph.

The x axis is time, since the polling is set to 10 (1 or greater). If you set the polling to zero, the x axis would list the variables selected in the Define Query window. The y axis gives the values of the variables. If you wait a minute before you STOP the polling, you can see how polling and sample size work. Because polling was set to 10 seconds, every ten seconds after the perform button was pressed, the device was polled. The sample size was set to 5, so the last five samples are displayed.

CH6-28

CH6-23

CH6-27

Managing the SNMP Manager Database 5-17

Changing aVariable's Value

You can change Read/Write variables when they are displayed as a table.

To change a variable’s value, follow these steps:

1 Select the value you want to modify from the Variable column.

The value will appear in the edit field above the table. If the value cannot be set, the status line displays the message: Read-only variable.

2 Make the change you want to the value in the edit field.

To cancel the changes, press the Cancel button.

3 Press the Update button.

The changed value will be displayed in the table. The value to be changed will be displayed in red. The change has not yet been made to the device.

4 Repeat steps 1 through 3 for each value you wish to modify.

5 To update the device with the changes, press the Set button.

If you click on the Start button before the Set button, all changes to the table values are canceled without changing the device's values. Any table values that were modified will be updated from the device (by polling).

Managing the SNMP Manager Database

The Manage Database command is accessed from the SNMP Manager in the OpenView Control menu. Manage Database accesses a compiler that adds MIBs to the Manager's database. MIBs can contain additional information which change the list of variables displayed in the Define Query window. To use the compiler to modify the existing OpenView MIB database, an SNMP v.1 or v.2 definition file is required. The definition files will normally have the file extension .MIB. After the definition file has been compiled into the OpenView database, the new variables will appear in the variable list in the Define Query window. The MIB compiler can extract device trap definitions to be used with the Trap Manager.

The manage database window consists of several parts:

■ The status line

■ The Available MIB files list


■ The Files in MIB Database list

Status Line The manage database window includes a status line. The status indicator and a line of text indicate the current status. The indicator displays one of three colors:

Table 5-7 Indicator Color Legend

Available MIB Files This section of the Manage Database window allows you to select the file(s) to be compiled.

■ The Import button allows you to browse the directory for the desired MIB files.

■ The Available MIB Files box lists all selected files to be compiled. The MIB files may be SNMP v.1 or v.2. If a definition file is a dependent (a child) of another definition file (parent), the parent MIB files must be previously compiled or currently selected. Missing dependencies will generate a prompt for the MIB file.

■ The Add button compiles the selected files in the Available MIB Files list.

Available MIBfiles list

Files in MIB Database list

Status

Color Description

Green indicates a ready state and, where appropriate, a successful compile

Yellow indicates the compile is in progress

Red indicates an error state

MIB Structure 5-19

Files in MIB Database After MIB files are successfully compiled, they will be listed in this section of the manage Database window. This list of files is maintained in a file in .INI format.

■ The Clear Database button allows you to delete all the files in the MIB database.

MIB Structure One of the keys to using the SNMP Manager is understanding the structure of the MIBs. This understanding is important when navigating through the variable tree. It is also important when compiling your own MIBs – some MIBs have dependencies on MIBs higher in the tree. The MIB structure of OpenView is organized as shown in the map below.

There are two areas where you might commonly add MIBs:

■ MIBs dependent upon MIB-2

■ Vendor-specific private MIBs

MIBs DependentUpon MIB-2

MIB-2 dependent MIBs, such as rmon, would be added to the structure under the MIB-2 group:

CH6-A1

internet

iso

org

dod

directory mgmt experimental private

mib-2

system interfaces . . .

enterprises

Default leveldisplayed


In this example, the MIB defining rmon would have to be compiled. However, its dependent relationship to MIB-2 requires that MIB-2 also be compiled

To accomplish this, use Manage Database to Add both MIBs. Select the MIB for MIB-2 first and then the MIB for rmon. OpenView provides the MIBs for both MIB-2 (RFC1213.MIB) and rmon (RFC1271.MIB). These files are in the MIBS directory under OpenView (ex. C:\OV\MIBS).

Vendor-SpecificPrivate MIBs

To add a private MIB, add it under enterprises as illustrated below.

The structure illustrated above is a basic one. You could create an entire tree hierarchy under the group you create for your company.

Selecting MIB Filesto Add to the

Database

OpenView comes with a MIB-2 SNMP database compiled from RFC1213.MIB. This file is located in the MIBS directory of OpenView.

To add information from other MIB files to this database follow these steps:

1 Select the file(s) you want compiled in the Available MIB Files box of the Manage Database window.

2 Click the Add button.

The compile may take several minutes to complete. Once started, you cannot terminate the process.

CH6-A4

enterprises

xyz company your company

mib #1 mib #2

MIB Structure 5-21

Adding Device Information

Once you have selected the MIB files to be compiled, press the Add button. Add appends the MIBs to the existing OpenView database. Add overwrites duplicate entries.

To completely rebuild the OpenView MIB variables list, click on Clear Database to delete the currently compiled MIBs. You can then select the appropriate MIB files and compile a new database.

Clearing SNMP Database

The Clear Database button deletes the entire OpenView SNMP database and its associated list of variables in the Define Query window.


6
In Case Of Difficulty
HP OpenView for Windows is designed to run several different OpenView applications simultaneously under Microsoft Windows. There are many possible settings and configurations for the WIN.INI and OVWIN.INI files, and a variety of applications and devices that can be used. Be sure to refer to the Installation Tips and Troubleshooting Guide files in the OpenView program group. These files contain the latest configuration and troubleshooting information.

Things You Should Know

Diagnosing problems requires that you provide as much configuration information as possible to software support personnel. To aid in diagnosing and correcting problems you should be able to provide the following:

■ Version of HP OpenView, MS Windows, and MS DOS

■ Network software you are using.

■ List of OpenView applications installed

■ Copies of your ovwin.ini, win.ini, system.ini, config.sys, and autoexec.bat files

■ Error message displayed

■ Brief description of what you were doing at the time of the error

■ Map files (.ovi, .ovd, .ovm, and .adl)

■ Log files (defined in the Log= entry in ovwin.ini)

■ Types of nodes in your map

■ Device type and vendor of a particular device that is causing the problem

■ ov\ovfiles\devices, cdbnodes, cdbnodep

6-2 CHAPTER 6: IN CASE OF DIFFICULTY

You may not be able to provide all this information, but the more you can provide, the more quickly your software support representative can solve the problem.

What You Should Do If you think that the problem occurred with a particular OpenView application, refer to the application documentation for information on error messages and support procedures. Additional troubleshooting information is given in readme and other text files available in the OpenView Program Group.

If the problem is with OpenView or with functions described in this manual, refer to the error message descriptions in on-line help. If you are not able to run OpenView to access help, access help directly using the help icon in the OpenView program group.

Technical support is available for the Workgroup Node Manager at the HP Customer Response Centers. Check the HP OpenView for Windows Web site for the latest support information www.hp.com/go/ovwin.

Phone support: HP Customer Response Center

Other Countries, contact your local HP office or dealer.

Phone Fax

U. S. & Canada (970) 635-1000

Europe English Dutch French German

(+31 20) 581-3330(+31 20) 581-3331(+31 20) 581-3332(+31 20) 581-3333

Asia / Pacific Australia Korea Taiwan China

+61-3-9272 2895+82-2-769 0114+886-2-717-9651+86-10 65053888 ext 5901

+61-3-9898 7831+82-2-3270 7084+886-2-715-3107+86-10 65924566

Faxback - HP First U.S. non U.S.

(800) 333-1917(208) 334-4809

OVMDump Diagnostic Tool 6-3

OVMDump Diagnostic Tool

OVMDump is a utility tool in the default directory C:\OV\DIAG. OVMDump allows you to look at information in an .OVM file. Simply execute OVMDump from this directory, specifying the target .OVM file, and a file to contain the output produced from OVMDump. For example,

C:\OV\DIAG\OVMDUMP T1MAP.OVM > T1DUMP

Your output will have the following format:

H e a d e r File Name: connect.ovmDate of modification: Mon Sep 04 14:28:52 1992File Version 7Number of Symbols 15Number of Names: 6Number of Labels: 5Number of Submaps: 1Current submap context: 0

OLD SYMBOL SUMMARY STATISTICS

SYMBOL ID Description Count-------------------------------0x1400 Submap 10x1209 Line 8 90x1327 Large Computer 1 10x1329 Medium Computer 2 10x1337 T1 Mux 1

Depending on the error, this information may be valuable to your software support representative.

OpenView Backup This section describes how to use the OpenView Data-File Backup utility to backup data files such as configurations and maps for archival purposes.

The HP OpenView Backup utility allows the user to backup, archive, and restore OpenView data files.

6-4 CHAPTER 6: IN CASE OF DIFFICULTY

To backup or restore OpenView data files:

1 Close OpenView. (Backups cannot be performed while OpenView files are open.)

2 From the Start menu, select Programs.

3 Select HP OpenView and then HP OpenView Data-File Backup.

In the Backup Options box, selecting changed data files will backup only files that have changed since the last OpenView Backup. Selecting All data files will do a full backup of HP OpenView data files with a file date newer than OVWIN.Exe.

In the Restore Options box, selecting Overwrite files will restore all files in the archive. Selecting Overwrite older files will restore only data files that are more recent than those found in the OpenView directory structure.

4 If desired, change the backup filename in the Archive Name field.

5 Select the desired Backup or Restore Options (described above).

6 Click the Backup or Restore button, as appropriate.

7 Click Done to exit.

The OpenView Backup File menu lists options to view, rename, and delete existing archives.

The Archive View option lists the files contained within the archive, along with the total number of files in the archive. Selecting one of the filenames in the scroll box displays information about that file in the File Information box. Note that File Information does not provide information about the archive file itself.

The Archive Rename option allows you to rename an archive file.

The Archive Delete option allows you to delete an unwanted archive file.

7
CUSTOM CONTROLS
Included in the Workgroup Node Manager is a set of Visual Basic custom controls designed for OpenView. These controls allow you to create Visual Basic applications to help you manage your network. The controls allow you to access and monitor SNMP devices. All device Mib-variables are read only. The following description assumes that you are familiar with Visual Basic and network operation using SNMP and MIB variables. The remainder of this chapter provides a description of the custom controls and program examples.

The OpenView SNMP custom controls provide visual indications of the values of SNMP variables for any SNMP device. The custom control set consists of the following elements:

Each control can be configured to poll an SNMP variable on a device and display the variable graphically. You can also display the value in a box beneath the control.

The controls also have an Alarm capability which allows you to set low and high thresholds which will cause the control to change from normal to alarm colors when those thresholds are exceeded.

With the exception of the Trap property and menu commands, these controls do not interact with the OpenView map.

LED Control

DB Connector Control

Meter Control

Text Box Control

RJ Jack Control

AC Jack Control

Switch Control

OV1

7-2 CHAPTER 7: CUSTOM CONTROLS

The XOV custom control is used to terminate your program when OpenView terminates. This control is described later in this chapter.

Code Components The code components include:

■ HPOVCC.VBX – OpenView SNMP custom controls.

■ XOV.VBX – OpenView custom control.

■ XOVSRVR.EXE – OpenView application to interface OpenView to the custom controls.

HPOVCC.VBX – This file contains the OpenView SNMP custom controls.

XOV.VBX – The XOV Visual Basic custom control initiates and terminates communication with XOVSRVR. This may be used to shut down your application when OpenView terminates. Only one instance of this Control can be used in your program.

XOVSRVR.EXE – XOVSRVR is an OpenView application. This program is started by OpenView and communicates with your Visual Basic application.

During its initialization, XOVSRVR sets the menus and registers symbols for the Visual Basic applications. These are defined by entries in the XOVSRVR.INI file. It can also start the Visual Basic applications. The applications can be started when OpenView starts or they can be started from an OpenView menu command.

Control Description 7-3

Control Description The following is a list of the unique properties of the OpenView SNMP custom controls.

Control Description Properties

AC Connector The AC Connector indicates the power line status. It displays a standard Three-Blade power cord receptacle.

Orientation: IntegerThis property selects the orientation of the AC connector:

■ Up (0)■ Down (1)■ Right (2)■ Left (3)

DB Connectors

The DB-x represents communications status through a DB-x connector.

Orientation: IntegerThis property selects the orientation of the DB-x connector:

DBConnector: IntegerThis property selects the type of DB-x connector displayed:


■ DB-9 (0)■ DB-15 (1)■ DB-25 (2)

LED The LED displays SNMP values through a simple binary “LED”.

DisplayType: IntegerSets the type of LED to display:

■ Round (0)■ Square (1)

Continued


Meter The Meter provides a method to display integer and counter variables through a meter type display.

Orientation: IntegerThis property selects the orientation of the meter:

Max: IntegerThis property sets the highest value that will be displayed on the gauge. It sets the upper limit of the display.

Min: IntegerThis property sets the lowest value that will be displayed on the gauge. It sets the lower limit of the display.

ScaleType: IntegerThis property selects the type of scale used for the meter:

GaugeType: IntegerThis property selects the type of meter that will be displayed:


■ Linear (1)■ Logarithmic

(2)

■ Bar (0)■ Needle (1)■ Dial (2)

RJ-45 The RJ-45 displays a RJ-45 Jack in various orientations and with color feedback of status.

Orientation: Integer

This property selects the orientation of the RJ-45 connector:

■ Up (0)■ Down (1)■ Right (2)■ Left (3)■

Properties 7-5

Properties All properties except those noted are available at both design time and run time. In addition to the standard Visual Basic properties the OpenView SNMP custom controls have the following properties:

Summary of Control Properties

The following table lists the properties supported by the OpenView custom controls.

Switch The Switch displays a variety of switches with binary attributes of an SNMP device.

Orientation: IntegerThis property selects the orientation of the switch. The orientations, with respect to “on” are:

SwitchType: IntegerThis property selects the type of switch that will be displayed. The type is:

■ Up (0) ■ Down (1)■ Right (2)

■ Left (3)

■ Slide (0)

Text Box The Text Box displays variable values. The Text Box represents text versions of numeric values and ASCII or hexadeci-mal versions of Octet Strings.

About ErrorColor MinThreshold StringValue

Alarm ForeColor NetAddr TableIndex

AlarmColor InstanceIndex NormalColor TimeOut

AlarmValues MaxReset NormalValues Trap

Community MaxThreshold PollRate Value

DataType MibVariable Retries VariableType

Enabled MinReset ShowValue

Name Type Description

(About) String The About property is only available at design time. Clicking on it in the control's property window brings up the standard About box.

Alarm Enum Specifies whether the control should check any of the threshold properties for alarm conditions, and if so, which thresholds to evaluate. Defaults to Disabled. (Disabled (0), Min/Max Thresholds (1), Norm/Alarm Values (2).


AlarmColor Long Sets the color used to draw the control if the value is equal to any of the listed AlarmValues or thresholds. Defaults to Red.

AlarmValues String The AlarmValues property contains a comma-delimited list of values consisting of specific states of the variable that represent alarm conditions (i.e. 5, 6, 7, 200, 201, 1000, 1001). Used when Alarm=Norm/AlarmValues

BackColor The standard VB BackColor property.

BorderStyle The standard VB BorderStyle property.

Community String The Community property contains the name of the community to be used in a Get request. It may be set at design time or runtime. The default community name is “public”.

DataType Integer This property will allow the user to specify how the variable data should be used. Either the Absolute or the Delta (difference between polls) value can be selected. Delta is normally used for counter variables. The DataTypes are:

• Absolute (0)

• Delta (1)

Enabled Integer Standard property to enable control. If false, no SNMP request will be made. Setting this value to TRUE will cause an initial request to be made, and will start polling if Poll-Rate is greater than zero. Enabled is set to FALSE when an error occurs, and must be explicitly set to TRUE to restart polling. This property should be set to TRUE after changing NetAddr or Community to start polling.

ErrorColor Long Color used to draw the control when an error occurs. Defaults to Dark Gray.

ForeColor Long Color used to draw the foreground of the control. Defaults to Black.

Height The standard VB Height property.

Index The standard VB Index property.

InstanceIndex Integer Specifies the Index of the MibVariable Instance that is to be polled. Defaults to zero (0). Not normally changed by the user, this is automatically set by the control at runtime when TableIndex is used.

Left The standard VB Left property.

MaxReset Long Defines the value that the variable must reach, after crossing the threshold, to reset the alarm condition. If the variable drops below this value, and there is an outstanding alarm condition, the control will be displayed in NormalColor if Alarm=Max/Min Thresholds.

MaxThreshold Long Defines the upper limit for the variable. If the variable exceeds this value, and there is not an outstanding alarm condition, an alarm event will be generated and the control will be displayed in AlarmColor if Alarm=Max/Min Thresholds. If the Trap property is set to TRUE an OpenView Alarm will be sent to the AlarmManager.

Summary of Control Properties 7-7

MibVariable String MIB object name to be retrieved from device specified in NetAddress. This name should be of the standard MIB format. (e.g. 1.3.6.1.2) These names may be found in the MIB specification, or examined using the Define Query dialog in OpenView's SNMP Manager.

MinReset Long Defines the value that the variable must reach, after crossing the threshold, to reset the alarm condition. If the variable rises above this value, and there is an outstanding alarm condition, the control will be displayed in NormalColor if Alarm=Max/Min Thresholds. If the Trap property is set to TRUE the corresponding OpenView Alarm will be cleared from the AlarmManager.

MinThreshold Long Defines the lower limit for the variable. If the variable drops below this value, and there is not an outstanding alarm condition, an alarm event will be generated and the control will be displayed in AlarmColor if Alarm=Max/Min Thresholds. If the Trap property is set to TRUE an OpenView Alarm will be sent to the AlarmManager.

MousePointer The standard VB MousePointer property.

Name The standard VB Name property.

NetAddress String Network address for SNMP Get. This should be in standard IP or IPX format (e.g. 1.2.3.4)

NormalColor Long Sets the color used to draw the control if the value is equal to any of the listed Normal-Values or thresholds. Defaults to Green.

NormalValues String The NormalValues property contains a comma-delimited list of values consisting of specific states of the variable that represent normal conditions (i.e. 5, 6, 7, 200, 201, 1000, 1001). Used when Alarm=Norm/Alarm Values.

PollRate Integer Rate in seconds to poll the specified device for the specified variable. If zero then no polling will take place - the device will get a single request for the variable when the control is enabled.

Retries Integer Retries is used to set the number of SNMP request retries that should be attempted by the control before failing with an error event. -1 is the default which will use the system default.

ShowValue Boolean If TRUE then a text box is displayed at the bottom of the control to show the current StringValue.

StringValue String A string version of the variable's current value, which may be displayed at the bottom of the control if ShowValue is TRUE. If the variable is an integer or counter then this contains a string representation of Value; if the variable is a string, object name, or net-work address then this will contain a string version of the variable and Value will be zero.

TableIndex Integer When set to a non-zero value, in the next poll cycle the control will perform this many GET-NEXT requests on the MIBVariable. If no errors are encountered, the control will set the InstanceIndex to the returned table index value.

Tag The standard VB Tag property.

Timeout Long The Timeout property determines how long in milliseconds the SNMP library will wait for a response before timing out. It may be set at design time or runtime. The default value is -1 which will cause the library to use the default system timeout value.


Events These events are designed to allow you to implement your own event handling routines in your program. All of the OpenView SNMP custom controls support the following Visual Basic events:

Top The standard VB Top property.

Trap Boolean Trap is used to tell the control whether to send an SNMP Trap packet when ever alarm conditions are set or cleared. If set to False (default) no SNMP Traps will be sent. If set to True, SNMP Traps will be sent to OpenView whenever a threshold is crossed that creates an alarm condition, and also whenever a reset value is crossed causing an alarm condition to be cleared. These traps will result in alarms in the OpenView Alarm Log.

Value The standard VB Value property.

VariableType Enum Identifies the type of SNMP variable that was polled. This property will contain the variable type of the returned SNMP variable. It will contain the ASN type number of the variable.1 - Bool2 - Integer 3 - BitStr 4 - OctetStr5 - Null6 - ObjectID

Visible The standard VB Value property.

Width The standard VB Value property.

Event Description Visual Basic

Alarm controlName_Alarm is generated anytime the MIB variable being polled changes to cross any thresh-old value or match any of the values in AlarmValues depending on the setting of Alarm. The single parameter passed gives the current value of the variable. You can use this event to write other alarm handling procedures.

Sub controlName_Alarm(Value As Long)

Click controlName_Click is the same as the standard Visual Basic Click event.

Error controlName_Error is generated anytime an error is encountered by the control. This could include SNMP errors such as TimeOut, NoSuchName, WrongCommunity, etc. The single parameter passed gives the value of the error encountered.

Sub controlName_Error(ErrorNum As Integer)


Basic Operation In order for any of the OpenView SNMP custom controls to work you must at a minimum set the following properties:

■ NetAddr

■ MibVariable

■ PollRate

■ Community

These properties are defined as follows:

NetAddr – This must be set to a valid Network Address. This address will be used in all SNMP requests.

MIBVariable – This must be set to the OID of the MIB Variable to be polled. This property will not include the “.0” to indicate a leaf node, or the index if the variable represents a table entry.

PollRate – This will be set to indicate the number of seconds between polls.

Community – This will be set to the string value of the community string for accessing the device at NetAddr.

A simple application could have any one of the controls on a Visual Basic form with these four properties set and it would begin to display SNMP data.

Example: Place an SNMP Text box control on a form and then assign the following values:

NetAddr: 192.63.36.1 (Or the device of your choice)

MibVariable: 1.3.6.1.2.1.1.1 (sysDescr in MIB II)

PollRate: 10 (Every 10 seconds)

Community: public (Or the SNMP Community namefor the device)

Update controlName_Update is generated every time a successful poll cycle completes. The single parame-ter passed gives the current value of the variable.

Sub controlName_Update(Value As Long)


If you run the application, the control will poll the device at NetAddr every PollRate seconds and retrieve the device's System Description in the MibVariable (sysDesc from MIB II).

Data Properties Properties that make it easier to work with SNMP data values are as follows:

■ DataType

■ ShowValue

■ Value

■ StringValue

■ VariableType

DataType – can be set to Absolute or Delta. This tells the control whether to display the actual value that was returned from the SNMP device (Absolute) or the difference in the variable since the last poll (Delta).

The Text Box control could be used to poll the UDPInDatagrams of a device. If you set the DataType of the control to Absolute, you will see a constantly incrementing value displayed which is the total since the last device reset. If you set DataType to Delta, you will see a number that represents the number of UDPInDatagrams since the last poll.

ShowValue - allows you to specify that a small text box be drawn below any graphical controls that are on the form.

The LED control will show only an LED when the ShowValue property is set to False. If the property is changed to True the LED will be displayed with a small text box below it. The text box will display the last polled value of the SNMP MIB variable.

Value and StringValue – are almost exclusively used at run-time to read the last value returned from a device poll. You can use them at design-time to set a value for assisting in design.

If you place a gauge on a form, you can set the initial Value or StringValue so that the needle of the gauge is in a visible range. This value will be overwritten at run-time with the polled value.

VariableType – This will contain the ASN type number of the returned SNMP variable.


Alarm and ThresholdProperties

There are several properties that can be set to provide visual feedback of 'normal' and 'alarm' conditions for the variable being polled. The alarm related properties are:

Alarm – tells the control how to evaluate any thresholds that you have set. This property can take on the following values:

0 – Disabled (do not do threshold checking)

1 – Min/Max Thresholds (use MinThreshold/MaxThreshold)

2 – Norm/Alarm Values (Use NormalValues/AlarmValues)

If this property is 0, no thresholds will be checked and the control will default to the color specified by the NormalColor property. If this property is 1 the control will evaluate the polled value against the configured Min/Max thresholds and set its color appropriately. If this property is set to 2, the polled value will be compared against the NormalValues/AlarmValues.

Trap – tells the control whether to send an SNMP Trap packet whenever alarm conditions are set or cleared. If False (default) no SNMP Traps will be sent. If True, SNMP Traps will be sent to OpenView whenever a threshold is crossed that creates an alarm condition, and also whenever a reset value is crossed causing an alarm condition to be cleared.

Threshold Properties for Integer or Counter Variables

One of the methods to indicate alarms is to determine a normal operating range for a particular variable. Variables of this type will tend to be integer or counter variables and the value will vary within this defined range. Thresholds can be set on the control so that when the variable value moves outside this normal operating range an alarm condition is created. When the variable value returns into the normal operating range, the alarm condition is cleared. These values will only be checked if the Alarm property is set to '1 - Min/Max Thresholds'.

Alarm MaxThreshold Alarm Values

Trap MaxReset AlarmValues

MinThreshold NormalColor

MinReset AlarmColor

NormalValues


MaxThreshold – sets a 'high' threshold for the value being polled. When the polled value is greater than the value of this property the control will change to the color specified by the AlarmColor property.

MaxReset – sets the value at which an alarm condition should be cleared. If the MaxThreshold property value has been crossed and an alarm condition exists, the polled value must drop below the value specified in the MaxReset property before the control will return to the color specified in the NormalColor property.

MinThreshold – sets a 'low' threshold for the value being polled. When the polled value is less than the value of this property the control will change to the color specified by the AlarmColor property.

MinReset – sets the value at which an alarm condition should be cleared. If the MinThreshold property value has been crossed and an alarm condition exists, the polled value must rise above the value specified in the MinReset property before the control will return to the color specified in the NormalColor property.

Threshold Properties for State Variables

Many variables do not fit into the standard threshold definition. For example, a port on an ethernet hub might have a variable that represents 'link status.' This variable might have several possible 'states'. The variable value might be one of several different values and move from one to another as the system operates. In this case, there could be several 'states' that represent a normal status and several that represent an error status. These values will only be checked if the Alarm property is set to '2 - Norm/Alarm Values'.

To provide support for these variables, another form of thresholds has been provided with two additional properties. These properties are NormalValues and AlarmValues.

The NormalValues property is used to specify a list of values that represent 'normal' states. When the control is equal to a value in this list, the control will display in the color specified by the NormalColor property.

The AlarmValues property is used to specify a list of values that represent 'alarm' states. When the control is equal to a value in this list, the control will display in the color specified by the AlarmColor property.


If the same value is included in both the AlarmValues list and the NormalValues list, an alarm condition will be created. This is a safeguard feature to ensure that an operator will always get alarms if they exist.

The NormalColor property is used to set the color of the control when there is no alarm condition present.

The AlarmColor property is used to set the color of the control when an alarm condition is present.

The control will be set to ErrorColor if the variable has a value that is not in the NormalValues or AlarmValues lists.

Table AccessProperties

MIB Tables are more complicated to access. An SNMP table is generally accessed by reading rows, or subsets of rows, using the SNMP GET-NEXT command or, if the manager application knows the index of a particular row, the variables are read using the SNMP GET command.

What makes this more difficult is that indexes can be any value or combination of values. For example, in MIB-II the IP Routing Table is indexed by IP Addresses. This means that for you to obtain a row in this table you would have to walk through the whole table, or know the IP Address of the node you are looking for.

In order to make table variables easier to obtain, the following special Table Access Properties are provided.

■ InstanceIndex

■ TableIndex

InstanceIndex and TableIndex allow you to specify that a control should hold the {n}th entry in a table.

InstanceIndex - contains the index of the variable that was retrieved using the Table Access Properties.

TableIndex - sets the row number of the variable that is to be retrieved.


Each time a control executes its poll cycle it will check:

If TableIndex is zero:

■ do regular GET using MibVariable + InstanceIndex

■ act on returned variable

If TableIndex is non-zero:

■ start with MIBVariable

■ do a GET-NEXT, TableIndex number of times

■ put the returned index into InstanceIndex

■ act on returned variable

This provides you with a method to retrieve any variable in any row, by count, and also to learn the returned index value.

For example, to get the description of the third interface entry in the interfaces table of MIB II, you would set the following properties:

NetAddr: 192.63.36.1 (Or the device of your choice)

MibVariable: 1.3.6.1.2.1.2.2.1.2 (ifDescr column of the interfaces (table)

PollRate: 10 (Every 10 seconds)

Community: public (Or the Community name for thedevice)

TableIndex: 3 (Third entry)

When the control runs, if this third entry exists, the StringValue property will contain the description, TableIndex will be set to 0, and InstanceIndex will contain the SNMP table index of the third entry.

Advanced Properties Two additional properties provide advanced tuning of the polling process. These are:

■ Retries

■ Timeout

Creating an Application 7-15

Retries – sets the number of SNMP request retries attempted by the control before failing with an error event. The default is -1 which will use the system default. Advanced programmers can use this property to override the system default and tune the polling to their desired rates.

Timeout – sets the amount of time that the control should wait for a response before retrying. The default is -1 which will use the system default. Advanced programmers can use this property to override the system default and tune the polling to their desired rates.

Creating an Application

The custom controls are installed automatically when OpenView is installed. They are placed in the \windows\system directory. In order to create an application using the OpenView custom controls, you must do the following:

■ Run OpenView.

■ Run Visual Basic and add the OpenView custom controls to the Toolbox.

■ Add an OpenView custom control to your form.

■ Set the appropriate property values for the control.

■ Run your program.

If you want menu items in OpenView to run your application, or if you want your application to close when OpenView terminates, you can make entries in XOVSRVR.INI to register your program.

Once you have completed your program, you should compile it so that it will use fewer system resources and be suitable for distribution.

Debugging VisualBasic Applications

When developing applications, it is helpful for testing to execute them from Visual Basic. (Note that running your application from Visual Basic uses considerably more system resources than executing it as an .EXE file. The system may not always behave as expected.)

An easy way to find MIB variable object ID's for use in your application is to run the OpenView SNMP Manager. This application contains the standard MIB II (RFC1213) with textual descriptions of each variable. When you have found the variable you want to use, you can copy the MIB variable object ID to the clipboard and paste it into the MibVariable property of your SNMP control.


Sample Programs

The following sample programs are available in the OV\SAMPLES directory. Make sure that Visual Basic is installed and that OpenView is installed and running.

Sample1 – Get the sysUpTime (a simple MIB variable)

Sample2 – Get a device's MAC address (a MIB table variable)

Sample3 – A simple hub manager

Sample 1. Get the sysUpTime for a device

This example describes how to read and display a MIB variable. You will use the Text control to poll and request a device's “sysUpTime.”

1 Start OpenView for Windows.

This will let your application use the OpenView SNMP libraries.

2 Start Visual Basic.

3 Add the HPOVCC.VBX custom control file to your project.

This is the file that contains the custom SNMP controls. It is located in your WINDOWS\SYSTEM directory.

4 Add the Text control to your form.

5 Set the properties on the control.

NetAddr Enter the IP or IPX address of the SNMPdevice you wish to poll.

MibVariable Enter the object ID of the MIB variable youwish to poll. The sysUpTime is in the systembranch of the MIB tree. The object ID is“1.3.6.1.2.1.1.3”

6 Run your application from Visual Basic.

Your application should show a value in the textbox similar to the following:

2 days 20 hrs 38 min 31.69 sec

Sample 2. Get a MAC address

This example describes how to read and display another MIB variable, “ifPhysAddress”. This is a device's MAC address.

Creating an Application 7-17

Repeat steps 1 through 4 in Sample 1.

1 Set the properties on the control.

NetAddr Enter the IP or IPX address of the SNMP device youwish to poll.

MibVariable Enter the object ID of the MIB variable you wish to poll. The MAC Address is in the interfaces branchof the MIB tree. The object ID is “1.3.6.1.2.1.2.2.1.6.”

TableIndex Set this property to 1 for the first row in the interfacetable.

2 Run your application from Visual Basic.

Your application should show a value in the textbox similar to the following:

Hex 08 00 08 49 5A D7

Sample 3. Monitor a Hub

This example illustrates a simple application to monitor a hub. Hubview is a compiled program. The source files are also provided.

1 Make XOVSRVR.INI file entries for Hubview.

[Programs]HUBVIEW=c:\ov\samples\sample3\backbox.exe

[CommandIDs]HPHUBA=&Run HubView,OV_IDMCONTROL,0x107,OVM_ENABLED,HUBVIEW,,Check the hub status

2 Start OpenView.

The entries in the CommandIDs section of the XOVSRVR.INI file will allow you to run Hubview from the OpenView Control menu.

3 Start Visual Basic.

4 Open the Hubview project.

5 Examine the code.

The Hubview program checks the status of 24 ports on the hub. The port ready status is returned as a 24 bit data value. The data is masked to determine the Up/Down status of each port. The port status is then used to select a red or green bitmap to simulate a port indicator. The RJ connectors are used to monitor selected status values for each port.


In order to run this sample, you would need to enter the address and community name of a similar hub installed on your network. You should refer to the MIB files for your network devices to see what status information would be of value to you.

Dim s, s2, number, h, M, PortStat(24)Sub Picture1_Click () hubinfo.ShowEnd SubSub Port_Click (Index As Integer) Traffic.ShowEnd SubSub Text2_Update (Value As Long) s = text2.StringValue s2 = text2.StringValue h = “0123456789ABCDEF”s = ((InStr(1, h, Mid$(s, 5, 1)) - 1) * 256 + (InStr(1, h, Mid$(s, 6, 1)) - 1) * 16 + InStr(1, h, Mid$(s,8, 1)) - 1) s2 = ((InStr(1, h, Mid$(s2, 9, 1)) - 1) * 256 + (InStr(1, h, Mid$(s2, 11, 1)) - 1) * 16 + InStr(1, h,Mid$(s2, 12, 1)) - 1) M = 2048If option1.Value = True Then number = sElse number = s2 End If For I = 1 To 12 If M > number Then portlight(I - 1).Picture = LoadPicture(“\ovdev\abdemo\hubview\redlight.ico”) Else portlight(I - 1).Picture = LoadPicture(“\ovdev\abdemo\hubview\grnlight.ico”) number = number - M End If M = M / 2 Next IEnd Sub

Registering Your Visual Basic Application 7-19

Registering Your Visual Basic Application

In order to launch your application from OpenView you must register it with XOVSRVR. This is done with entries in the XOVSRVR.INI file in the \OV directory. Among the sections in this file are Application, Programs, MenuIDs, CommandIDs, and Objects. Not all sections are required for a particular application. You must make an entry in the Programs section. If you want your application to be started by the user you will need an entry in the CommandID section and optionally in the MenuID section.

XOVSRVR.INI File Format

XOVSRVR gets its initialization instructions for its client programs in its initialization file XOVSRVR.INI. XOVSRVR.INI is a text file and follows the WIN.INI file format. These sections are:

■ [Application] – contains information about the server, XOVSRVR

■ [Programs] – contains information about the client programs

■ [MenuIDs] – defines non-terminal menu items. XOVSRVR adds these to the OpenView menus.

■ [CommandIDs] – defines terminal menu items. XOVSRVR adds these to the OpenView menus.

The following paragraphs describe the entries in XOVSRVR.INI. Optional entry fields are enclosed in brackets. Entry fields which are enclosed in angle braces and represented in italics are supplied by you. Entry fields are separated by commas. Any optional field which is not present must be delimited by commas. Textual description fields, such as the status string fields, may optionally be enclosed in double quotes ( “ ). However, they must be enclosed in double quotes if they contain a comma. Beginning and ending spaces will be stripped from entry fields unless they are textual description fields which are not enclosed in double quotes.

Note that Windows requires that each entry name be unique within its section.

[Applications] Section

The Description entry is required in the [Applications] section. It should be set to:

[Applications]Description=XOVSRVR


The Description should not be changed.

[Programs] Section

This [Programs] section lists the Visual Basic applications and optionally supplies startup information. The syntax is:

TaskName = Program filename[, InitShowCmd]

where:

Task Name is the name of your application and is eight characters or less. The Task name is used to reference your application in other parts of the .INI file.

Program filename is the full path and file name of the your application's executable file (ex. OVTEST = c:\ov\ovtest.exe).

InitShowCmd is an optional field to direct XOVSRVR when to start your application. The default value is 0. The values result in the following actions:

0 Do not start the application during XOVSRVR initialization

1 Start during XOVSRVR initialization and display the application window normally

2 Start during XOVSRVR initialization and display the application window minimized

3 Start during XOVSRVR initialization and display the application window maximized

An invalid value of InitShowCmd is treated as 0. Programs which are not started during XOVSRVR initialization will be WinExeced when one of their menu commands is selected. Their windows will be displayed normally.

Example

[Programs]PROG1=c:\myapp\myexe1.exePROG2=c:\myapp\myexe2.exe, 2PROG3=


The entry shows three OpenView applications as clients of XOVSRVR. At least one entry is required for this section. Note that PROG2 will be started when XOVSRVR is loaded, and its window will be initially minimized. PROG3 is a dummy entry. This allows the program to initialize and connect to XOVSRVR but the program will not be launched by XOVSRVR. This is useful during development. When XOVSRVR reads the empty entry, it will add PROG3 to its list of client applications. But it will not start or try to communicate with the application until contact is initiated by the application (when the application is run from Visual Basic).

Menus andCommands

OpenView applications have two types of menu items: those which bring up a popup menu with more menu items, and those which pass a command to the application. The [MenuIDs] section is used for specifying those menu items which bring up a popup or cascading menu. The [CommandIDs] section specifies menu items that result in a command.

MenuIDs Section

The MenuIDs section is used only if you wish your application's menu item to be a part of a non-standard menu or a cascading menu. The syntax is as follows:

MenuID=Menu Name,[!]Parent Menu,[Description]

where:

MenuID is an identifier to refer to this menu within the .INI file and must be unique within the [MenuIDs] section.

Menu Name is the label to be displayed in the menu. It may be optionally enclosed in double quotes.

[!] is an optional ! character causing a menu separator bar to be drawn above the new menu item.

Parent Menu is the menu under which the new menu will be added.

Description is optional and is the text you will see at the bottom of the OpenView window when the menu item is highlighted. It can be enclosed in double quotes.


Parent Menu is either a menu already described in this section or one of the pre-defined menus listed below.

OV_IDMMAIN add <Menu Name> to the main menu (menubar)

OV_IDMMONITOR add <Menu Name> to the “Monitor” menu

OV_IDMDIAGNOSE add <Menu Name> to the “Diagnose” menu

OV_IDMCONTROL add <Menu Name> to the “Control” menu

OV_IDMHELP add <Menu Name> to the “Help” menu

OV_IDMFILE add <Menu Name> to the “File” menu

OV_IDMEDIT add <Menu Name> to the “Edit” menu

OV_IDMVIEW add <Menu Name> to the “View” menu

OV_IDMOPTION add <Menu Name> to the “Option” menu

OV_IDMPOPUP add <Menu Name> to the popup menu

<Parent Menu> may also be a <MenuID> defined in the <MenuIDs> section.

Using OV_IDMMAIN will place your menu on the menu bar and OV_IDMPOPUP will place the menu in the menu that appears when clicking the right mouse button on a symbol. The following example creates a new menu (HubView) on the menu bar and two cascading menus.

Examples

[MenuIDs]HubView=&HubView,OV_IDMMAIN,Hub ManagerCommand 1=Command &1,HubView,Start HubViewCommand 2=Command &2,HubView,Stop HubView

[CommandIDs] Section

This section is used to specify the menu item that a user would use to start your application. A command ID is required so that OpenView can tell XOVSRVR when one of its commands has been selected. XOVSRVR


will then tell your application if it is running and has a DDE link established. If your application is not running, XOVSRVR will launch it and tell it of the command as soon as a DDE link with your program is established.

The syntax of a [Commands] entry is:

CmdEntry=CommandName,[!]Parent Menu,Command Id,Flags,Task Name, Object Type[, Description]

where:

■ CmdEntry is an identifier to refer to this command within the .INI file. CmdEntry must be unique within the [CommandIDs] section. You should use an identifier that will not conflict with one from another application.

■ CommandName is the string which will appear on the menu. It may be optionally enclosed in quotes. A key mnemonic may be added to a menu or command name by preceding the desired letter with an ampersand (&) in the entry.

■ Parent Menu specifies the menu where CommandName will be displayed. This may be a custom menu name from the [MenuIDs] section as well as the standard OpenView menus listed earlier, other than the main menu.

■ Command ID is a number assigned by you that is unique to your application that refers to the menu item. It can be decimal, hex, or octal. It must be greater than 100. (Values less than 100 are reserved for OpenView.) This value is used by your application. When the user selects CommandName, Command ID will be passed to your application as a parameter in the XOV custom control's command event procedure.

■ Flags is a required field. Flags identifiers are:

OVM_ENABLED command initially enabled

OVM_DISABLED command initially disabled (default)

OVM_CHECKED command initially checked

OVM_UNCHECKED command initially not checked (default)

OVM_OBJSPEC command is object specific

OVM_NOT_OBJSPEC command is not object specific (default)


Flag identifiers which are not mutually exclusive may be or'ed together using a vertical bar:

OVM_DISABLED | OVM_OBJSPEC

■ Task Name specifies the application defined in the [Programs] section that has registered for this command.

■ Object Type is the object type that will enable (ungrey) the menu item if object specific.

■ Description is optional and contains text to be displayed on the OpenView status bar.

A place holder (two commas “,,”) is required if a missing field is not the last field.

Example

[MenuIDs]SMGR=&SNMP Manager,OV_IDMCONTROL,Mib manager tool

[CommandIDs]SMGR1=&Define Query...,SMGR,0x104,OVM_ENABLED,MIB,,Get or Set Mib variablesSMGR2=&Select Query...,!SMGR,0x101,OVM_ENABLED,MIBSMGR3=&Manage Database...,SMGR,0x100,OVM_ENABLED,MIBCOMPMyHelp=MyHelp...,OV_IDMHELP,0x102,OVM_ENABLED|OVM_OBJSPEC,MYTASK

Note the use of key mnemonics in the first four entries. A separator bar will be inserted before the Select Query entry. The &Define Query entry required a place holder (,,) for the missing fields.

The entry to add cascading menus and an additional command for the HubView example (see MenuIDs section) would be:

[CommandIDs]HubView0=Command &3,HubView,0x700,OVM_ENABLED,,,HubView UtilitiesHubView1=&Get Data,Command 1,0x701,OVM_ENABLED,,,Fresh Start,SYM_HUBHubView2=&Report,Command 1,0x702,OVM_ENABLED,,,Print Report HubViewHubView3=&Sleep,Command 2,0x703,OVM_ENABLED|OVM_CHECKED,,,Pause HubViewHubView4=&Quit,Command 2,0x704,OVM_ENABLED,,,End HubView


Figure 7-1 Examples of Menu and Command items

[Objects] Section

The Objects section registers objects to applications running under the server. The format for entries in this section is:

Object Name=[Application Name][,Application Name]...

Object Name is either one of the pre-defined names for the standard objects (listed below) or the number of an object type as listed in OVWIN.INI for user defined symbols.

Application Name is the name of the application (defined in the Programs section) to which the object is to be registered. You may specify the object be registered to multiple applications by separating each name with a comma.

The pre-defined symbol names are:

SYM_SUBPICTURE SYM_GOTOSUBPICT SYM_LINE

SYM_FSERVERPICT SYM_PCPICT SYM_LINE_1

SYM_MEDCOMPPICT SYM_MEDIUM_COMPUTER SYM_LINE_2

SYM_LARGE_COMPUTER SYM_SMALL_COMPUTER SYM_LINE_3

SYM_MEDIUM_COMPUTER_2 SYM_DBSERVER SYM_LINE_4

HUB1

HUB2


SYM_PC SYM_FSERVER SYM_LINE_5

SYM_PSERVER SYM_T1_MUX SYM_LINE_6

SYM_DOCSERVER SYM_MODEM SYM_LINE_7

SYM_ANALYZER SYM_GATEWAY SYM_LINE_8

SYM_ROUTER SYM_DTC SYM_LINE_9

SYM_PBX SYM_X_25 SYM_LINE_10

SYM_BRIDGE SYM_NET_PRINTER SYM_LINE_11

SYM_HP_DTC SYM_SNA SYM_LINE_12

SYM_LOCAL_PRINTER SYM_HUB

The following example will register the hub symbol to the Hubview application:

[Objects]SYM_HUB=HUBVIEW

This completes the registration process.

Adding Features To Your Application

In order for you to make use of the additional program launch and terminate functions you must register your application in the XOVSRVR.INI file. To terminate your program from OpenView, you must add the XOV.VBX control to your form.

When you run your program under Visual Basic, if your XOV custom control Enabled property is TRUE, the control will initiate communication with XOVSRVR and your program will run.

You can make your application shut down upon receiving an End Session message for OpenView by adding the XOV.VBX control to your application and placing an End statement in the EndSession event of the OpenView custom control.

1 Add the needed entries to XOVSRVR.INI to add your application's menu items and commands to OpenView's menu.

2 Run OpenView to start XOVSRVR.

3 Run Visual Basic and select File, Add File, \windows\system\XOV.VBX.

Adding Features To Your Application 7-27

4 Repeat for the SNMP controls, HPOVCC.VBX.

The controls will be added to the tool box.

The XOV custom control is similar to the Visual Basic Timer control in that it is not sizable and is invisible at run-time. The main function of this control is to allow OpenView to send a message to your application when OpenView is terminated.

5 Click OK.

The XOV control will be added to the Visual Basic tool box.

6 Select the XOV control and drag it to your form.

Since this control is visible only at design time, it doesn't matter where you place it on the form. The main form is a good choice to contain XOV. One of the properties of the XOV control is the enabled property. This property is automatically set to TRUE at runtime. Note that this communication will only happen if OpenView is running. Only one instance of this control can be added to your program.

7 Select the Properties command in the Visual Basic Windows menu.

This will display the Properties window for the XOV control.

You must match the TaskName property with the name of your application as defined in the [Programs] section of XOVSRVR.INI (OVTEST for example).

8 Enter the name of your application (OVTEST) in the TaskName field.

9 Add an END statement to the End_Session procedure of the XOV control.

OV2


A
OPENVIEW COMMAND AND TOOL REFERENCE
This appendix lists OpenView menus commands and their functions, and lists the tools in the Toolbar and the tool functions.

Menu Commands The following tables list the OpenView commands by menu.

Figure A-1 OpenView menus

File Menu Commands

Command Description

New Start a new (empty) map.

Open... Open an existing map file.

Save Save the map using the current file name.

Save As... Save the map to a different file name.

Check Map... Check the map for errors.

Print Submap Print the current submap portion displayed on screen.

Print Object List Print a list of all objects in the map, sorted by submap.

Print Setup... Configure printing.

Load Selection List... Select a set of objects whose names have been saved in a file.

Save Selection List As... Save a set of object names to a file.

Exit Exit OpenView.

A-2 APPENDIX A: OPENVIEW COMMAND AND TOOL REFERENCE

Edit Menu Command

View MenuCommands

Command Description

Add Display the Add toolbox.

Cut Copy the last selected object to the clipboard and delete from submap.

Copy Copy the last selected object to the clipboard.

Paste Copy clipboard contents to the next selected position on a submap.

Delete Delete a selected object from the map.

Describe... Add a name, label, addresses, and notes to the selected object.

New Submap... Create a new submap.

Rename Submap... Rename the current submap.

Clear Submap Erase all objects in the current submap.

Delete Submap... Delete a submap and its contents from the map.

Set Background Image... Select a background file for the current submap.

Clear Background Image Delete the reference to a background file for the cur-rent submap.

Set Home Submap... Define the top level (“Home”) submap for the map.

Command Description

Zoom 1 Set the display to normal.

Zoom 1/2 Set the display to 1/2 scale.



Pan... Shift the view in the current submap.

Set Grid... Select a grid spacing as a drawing aide.

Show Grid Display the drawing grid on the current submap.

Menu Commands A-3

Monitor MenuCommands

Control MenuCommands

Command Description

Describe... Add a name, label, address(es), and notes to the selected object.

Status Legend... Display the alarm status colors.

Alarm Log... Display the Alarm Log.

Ping Ping selected device.

Customize Traps... Change default trap settings.

HP TopTools Run TopTools application.

Polling Poll network devices.

View Polling List... List devices in current polling list.

Add Device(s) Add devices to poll to current list.

Remove Device(s) Remove devices to poll from currents list.

Configure System Defaults... Change interval and alarm action defaults for a device.

Configure Device Parameters... Change interval and alarm action defaults for a device.

Start Polling Initiate polling of network devices.

Command Description

Browse Web Home Page Display Web Home Page associated with device.

Browse Web Management Page

Display Web Management Page associated with device.

SNMP Manager Run the SNMP Manager application.

Define Query... Sets query variables and display options.

Select Query... Selects and performs a query.

Manage Database... Selects MIB files to add to the database.

DMI Manager Run the DMI Manager Application.


Autodiscovery MenuCommands

Command Description

Configure Configure the Autodiscovery facility.

Discovery Schedule... Schedule the discovery process.

Discovery Networks... Select networks to be searched.

User-Specified Devices... Specify additional devices.

Ignored-Devices... Specify devices to ignore in layout.

Device Classes... Specify classes of devices to be ignored in layout.

Discover Discover network devices.

Discovery Manager... Display the Discovery Manager Dialog.

Discover Routers Initiate router discovery.

Update Host Names Change the Host names.

Clear Discovery Database Delete the current discovery database.

Dump Discovery Database Copy the discovery database.

Discover Topology Discover network segments

Layout Layout discovered devices.

Do Basic Layout Begin layout.

Basic Layout Options... Configure layout options.

Configure Preferred Name... Enter names for nodes.

Menu Commands A-5

Options MenuCommands

Window MenuCommands

Help MenuCommands

Command Description

Protect Map... Enable or disable manual editing of a map file using a password.

Log In... Log In and select a security level.

Log Out Disables all menu items in OpenView and locks the map.

Set Password... Sets or changes passwords.

Customize HP OpenView... Select maximum symbol and message counts for a map, specify object description operation, log file, and default map.

Customize Alarms... Select alarm frequency, sort order, sounds, and display propagation.

Customize Device Access... Associate control information with a network address.

Command Description

Home Submap Display the home submap.

Previous Submap If you opened a submap symbol to display the current sub-map, this command will return you to the previous submap.

Locate Submap... List all submaps in the map file and display the one selected.

Locate Object... List all objects in the map file and display the submap con-taining the one selected.

Extend Locate... Search for map objects using a variety of selection criteria.

Command Description

HP OpenView Index... Access on-line help for OpenView.

About... Display copyright and version information for OpenView.


Toolbar OpenView displays a toolbar at the top of the main window. The toolbar provides quick access to frequently used functions. The toolbar buttons are described in the following table.

Figure A-2 Toolbar Buttons

Toolbar Functions

pg158.tif

Tool Description

Scissors Cut (same as in the edit menu).

Camera Copy “

Paste Paste “

Eraser Delete “

Pencil Describe “

1:1 Zoom 1 (same as in the View menu).

1:2 Zoom 1/2 “

1:4. Zoom 1/4 “

1:8 Zoom 1/8 “

Home Submap Display the Home submap (same as in the Window menu).

Previous Submap Display the previous submap (same as in the Window menu).

Alarm Bell Display the alarm log. Icon color reflects unacknowledged alarms.

B
CONFIGURING NOTIFY! CONNECT
OpenView is shipped with a remote paging application Notify! Connect from Ex Machina Inc. The application can receive messages from OpenView's alarm system and use a modem to generate a page at a remote location. When OpenView is installed the Notify! Connect application is automatically installed. OpenView makes entries in the OVWIN.INI file and sets several of the Notify! Connect parameters to default values during OpenView's installation. Before you can send pages you must update these values to match your paging configuration.

Values that must be entered or changed are:

■ user to be paged (default is OPENVIEW)

■ paging service (default is SKYPAGE)

■ Pager ID number of user (default is 0)

■ format of paging message (see OVWIN.INI)

OVWIN.INI Configuration

In order to have an alarm generate a page you must make an entry in the OVWIN.INI file under the [OVAlarm] section. The entry instructs OpenView to send a service request to a program. OpenView makes the following default entries in the OVWIN.INI file:

[OVAlarm];RunCritical=>C:\OV\notify\connect.exe,NOTIFY,SendPage;OpenView,Critical Alarm: %o - %a;RunMajor=>C:\OV\notify\connect.exe,NOTIFY,SendPage;OpenView,Major Alarm: %o - %a;RunInformational=>C:\OV\notify\connect.exe,NOTIFY,SendPage;OpenView,Info Alarm: %o - %a

The entries are disabled until the semicolons (;) are removed. When the semicolons are removed and OpenView is restarted, OpenView will request a page be sent to a user named “OpenView” if a major, critical, or informational alarm occurs. (OpenView generates an

B-2 APPENDIX B: CONFIGURING NOTIFY! CONNECT

informational alarm when a users logs in.) Refer to chapter 4 of this manual for more information.

Notify! Configuration

OpenView makes the following default entries in the Notify database:

■ user to be paged: OPENVIEW

■ type of paging service: SKYTEL

■ modem settings

To configure Notify! Connect for use you must enter the correct settings for your paging system.

1 Run Notify! Connect by double-clicking its icon in the HP OpenView program group.

Select the Services function and add your service if necessary and correct any of the settings as needed.

2 Select the Address function and edit the entries for the user “OpenView” (Service, Pager type, Pager ID etc.).

3 Select the Server function and make any required changes to the communications settings.

It is recommended that a business dialing prefix be set here if required.

4 Use the Test function to verify that your pager system is working before using the pager through OpenView.

5 After you have tested the paging configuration in Notify! you can test it with an informational alarm in OpenView.

Logging into OpenView can be used to trigger an informational alarm.

You may wish to have Notify! Connect running as a background server whenever you are running Windows. You can do this by copying the Notify! icon from the HP OpenView group into the Startup group. If you select the properties for this icon you can select “Minimize on Startup” to have Notify! display as an icon when started. This will prevent the main Notify! menu from displaying when an alarm generates a page.

Additional information for configuring and using Notify! is contained in the Notify! Connect documentation.

INDEX 1

INDEX

Symbols.BMP format 3-5.OVD files 3-1.OVI files 3-1.OVS files 3-1.TIF format 3-5

AAdd command 3-12Add window 3-12adding connection example 3-8adding lines, example 3-7address

IP 2-2alarm aging 4-25alarm clearing 4-25alarm configuration 4-25alarm customizing 4-22, 4-25alarm database 4-32alarm DDE access 4-31alarm filter 4-23alarm forwarding 4-28Alarm Forwarding dialog box 4-29alarm frequency 4-25alarm log, closing 4-25alarm log, using the 4-20alarm propagation 4-25alarm selection for display 4-23alarm set 4-24alarm sorting 4-22alarm sounds 4-25alarm system, overview 1-6alarms 4-21alarms, checking 4-19alarms, overview 1-3alarms, running programs from 4-30alarms, sorting by status 4-23alarms, sorting by time 4-23application 3-12ARP 2-2ARP caches 2-2AutoArrange Redrawn Maps 2-16autodiscovery

setup 2-3

Autodiscovery menu A-4Autodiscovery, overview 1-2

Bbackground 3-3, 3-5Basic IP Discovery command

Autodiscovery 2-12Basic IP Discovery field

Autodiscovery 2-12Basic Layout Options dialog 2-15Basic, Discovery 2-2bitmap 3-3, 3-5

Cchecking alarms 4-19Clear Discovery Database command 2-13clearing alarms 4-25closing the alarm log 4-25colors, status 4-17COMCHECK utility 2-3community name 2-2compiling MIBs, defined 1-7component 3-13compound icon 3-13Compound Object 3-13computer, type 3-13Configure Discovery Networks dialog 2-3configuring alarms 4-25Connections 3-1connections 3-13connections, example 3-8Control Menu A-3conventions

notice icons, About This Guide 2text, About This Guide 2

create a new map 3-4creating, home submap 3-4creating, map 3-4customizing alarms 4-22, 4-25customizing device access 4-2customizing the describe function 3-7cut, used with selection list 3-14

Ddatabase

Autodiscovery 2-13Database Contents command

Autodiscovery 2-12database, alarm 4-32DDE access from alarm 4-31default gateway 2-2deferring the describe function 3-7

2 INDEX

Define QuerySNMP Manager 5-1

describe function 3-7Device Classes 2-8device list 3-3device selection

SNMP Manager 5-2diagnostic utility 6-3disabling 3-10Discover All IPX Networks field

autodiscovery 2-5Discovery Manager dialog 2-11display symbols 3-13Display window

Autodiscovery 2-12drawing a 3-2drawing a map 3-2, 3-3Dump Discovery Database command 2-13Dump utility 6-3

EEdit Menu A-2edits 3-10example submap 3-3Extended Discovery command

Autodiscovery 2-12Extended Discovery field

autodiscovery 4-2Extended, discovery 2-2

FFile Menu A-1File, Server 3-13filter, alarm viewing 4-23format, bitmap 3-5frequency of alarms 4-25

Ggateway

default 2-2generic devices

Autodiscovery 2-11gets, defined 1-7GoTo symbol 3-14GoTo, symbol 3-14grid 3-5

HHelp Menu A-5hierarchy 3-3home submap 3-2, 3-3, 3-4

Iicons, application 3-12Ignored Devices. 2-9IP 2-2IP address 2-2IP Default Gateway field

autodiscovery 2-4IP Subnet Mask field

autodiscovery 2-4IPX 2-2

Llayout options

Autodiscovery 2-15autodiscovery B-1, B-2

legend, status 4-17levels, propagation of status across 4-18line weight 3-13Lines 3-1lines 3-13lines, example 3-8list of devices 3-3Load Selection List 3-14load selection list 4-6local submap 3-3

MMac addresses

Autodiscovery 2-16Management Information Base (MIB) 5-1Manager Database command

SNMP Manager 5-17managing alarms 4-21managing Autodiscovery 2-6map 3-2map example 3-3map printing 3-9map, saving 3-9mapping procedure 3-3maps, overview 1-2mask

subnet 2-2Master Console, alarm forwarding 4-29MIB

SNMP Manager 5-1MIB structure

SNMP Manager 5-19MIB variable

Autodiscovery 2-11MIB, adding

SNMP Manager 5-21MIB, defined 1-7

INDEX 3

MIB, deletingSNMP Manager 5-21

MIB-2SNMP Manager 5-19

MIBs, privateSNMP Manager 5-20

multiple adds 3-12

Nname field

SNMP Manager 5-2Netware services 2-2Network Address field

SNMP Manager 5-3network map 3-2Networks field

Autodiscovery 2-11node 3-13node in alarm viewing 4-24

Oobject in alarm viewing 4-24object lists, printing 3-9object name, in alarm viewing 4-24object status in alarm viewing status 4-24object type, in alarm viewing 4-24options for layout

Autodiscovery 2-15Options menu A-5OVALINS.* files 4-32OVDUMPIT file

Autodiscovery 2-13OVM files 3-1OVMDump program 6-3

Ppassword 3-10paste, used with selection list 3-14pointer 3-13polling devices 4-4polling parameters 4-7polling, overview 1-4positioning symbols 3-5printing a map 3-9printing, maps 3-9private MIBS

SNMP Manager 5-20problems 6-1, 7-1procedure for drawing a map 3-3propagation of alarms 4-25propagation of status 4-18Protect Map 3-10

Qqueries, defined 1-7queries, selecting

SNMP Manager 5-6query

SNMP Manager 5-1

Rregional submap 3-3Reset Display command

Autodiscovery 2-12rmon

SNMP Manager 5-19routers

used in autodiscovery 2-2running programs from alarms 4-30

SSave Selection List 3-14save selection list 4-6Save Selection List As 4-6saving a selection list 4-6Segmented View Symbol Spacing 2-16Select Object 3-13selecting alarms 4-23selection list 3-14selection pointer 3-13sets, defined 1-7setting variables

SNMP Manager 5-17SNMP

in discovery 2-2SNMP Manager 5-1SNMP Manager, overview 1-7SNMP, defined 1-7sorting alarms 4-22sorting alarms by status 4-23sorting alarms by time 4-23sounds in alarms 4-25status colors 4-17Status field

Autodiscovery 2-12status legend 4-17status propagation 4-18, 4-25status sorting alarms by 4-23status, alarms 4-21sub object in alarm viewing 4-24submap symbol 3-13submap width

Autodiscovery 2-16submaps 3-1, 3-2subnet mask 2-2

4 INDEX

subobject + 3-13support, technical 7-1symbol 3-13symbol sets 3-12symbol spacing

Autodiscovery 2-15symbol, GoTo 3-14symbol, submap 3-13symbols 3-1symbols, application 3-12

Ttechnical support 7-1technical, support 6-1Text 3-13text size 3-13text tool 3-13text tool, underline 3-13text, example 3-8text, style 3-13thickness 3-13thickness, line 3-13time, sorting alarms by 4-23Topology Discovery 2-8traps 4-10traps, overview 1-5troubleshooting 6-1, 7-1

Uused in a label 3-13

Vvariables, setting

SNMP Manager 5-17View menu A-2viewing alarms 4-22views, of a network 3-2

Wwalking a map 3-2, 4-19weight, line 3-13Window Menu A-5Workgroup Node Manager, overview 1-1

Documents

HP OpenView for Windows User Guide