Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1/2” SPINE
1/4”
User Guide
f o r Tr 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
Version 6.1 for Windows® and ‘97 for Windows NT®
3Com Corporation
5400 Bayfront Plaza
P.O. Box 58145
Santa Clara, CA
95052-8145
http://www.3com.com
© 1997
3Com Corporation
All rights reserved.
Printed in the U.S.A.
09-1114-001
HP OpenView for
Windows® User’s Guide
®
http://www.3com.com/
ii
CONTENTS
1 OVERVIEW
HP OpenView Interface 1-1
Maps 1-2
Autodiscovery 1-2
Alarms 1-3
Polling 1-4
Trapping 1-5
Alarm System 1-6
SNMP Manager 1-7
iii
Map Example 3-3
Creating a Map File and Home Submap 3-4
Adding a Background 3-5
Adding Submap Symbols 3-6
Adding Lines 3-7
Adding Text 3-8
Add Remaining Submaps 3-8
Saving a Map 3-9
Printing a Map 3-9
Web Browser 3-9
Disabling the Map Editing Feature 3-9
Map Toolbar and Commands 3-10
Status Bar 3-10
Toolbar 3-11
Add Toolbox 3-12
Select Object 3-13
Text 3-13
Lines and Connections 3-13
Symbol 3-13
Selection Lists 3-14
Extended Locate 3-14
iv
Monitoring Traps from Network Devices 4-10
Customizing Traps 4-11
Selecting a Device Class 4-12
Ignoring Traps 4-12
Specifying Traps for a Device Class 4-13
Choosing Trap Alarm Actions 4-14
Description Field Variable Substitution Syntax 4-15
Loading Traps 4-16
Automatically Acknowledging Alarms Generated by Traps 4-16
Managing Alarms 4-17
Selecting Map Status Options 4-17
Status Propagation 4-18
Configuring Alarms 4-21
Viewing Alarms 4-22
Selecting Alarms for Display 4-23
Acknowledging and Deleting Alarms 4-24
Configuring Alarm Processing 4-25
General Alarm Settings 4-26
Alarm Sound Settings 4-27
Alarm Sound Configuration 4-27
Alarm Status Propagation 4-28
Alarm Forwarding 4-28
Running Programs 4-30
DDE Commands 4-31
Paging Program 4-32
Alarm Database 4-32
DMI Manager 4-33
HP Top Tools 4-33
v
Selecting a Query 5-7
Removing a Query from the Menu 5-8
Displaying SNMP Query Results 5-9
Displaying a Query as a Table 5-10
Displaying a Query as a Graph 5-14
Changing a Variable's Value 5-17
Managing the SNMP Manager Database 5-17
Status Line 5-18
Available MIB Files 5-18
Files in MIB Database 5-19
MIB Structure 5-19
MIBs Dependent Upon MIB-2 5-19
Vendor-Specific Private MIBs 5-20
Selecting MIB Files to Add to the Database 5-20
6 IN CASE OF DIFFICULTY
Things You Should Know 6-1
What You Should Do 6-2
OVMDump Diagnostic Tool 6-3
OpenView Backup 6-3
7 CUSTOM CONTROLS
Code Components 7-2
Control Description 7-3
Properties 7-5
Summary of Control Properties 7-5
Events 7-8
Basic Operation 7-9
Data Properties 7-10
Alarm and Threshold Properties 7-11
Table Access Properties 7-13
Advanced Properties 7-14
Creating an Application 7-15
Debugging Visual Basic Applications 7-15
Registering Your Visual Basic Application 7-18
Menus and Commands 7-21
Adding Features To Your Application 7-26
vi
A OPENVIEW COMMAND AND TOOL REFERENCE
Menu Commands A-1
File Menu Commands A-1
Edit Menu Command A-2
View Menu Commands A-2
Monitor Menu Commands A-3
Control Menu Commands A-3
Autodiscovery Menu Commands A-4
Options Menu Commands A-5
Window Menu Commands A-5
Help Menu Commands A-5
Toolbar A-6
Toolbar Functions A-6
INDEX
vii
viii
ABOUT THIS GUIDE
Finding Specific This table shows where to find specific information in this guide.
Information in
This Guide If you are looking for Turn to
An overview of HP OpenView features and how it manages Chapter 1
networks
How to create a map using Autodiscovery Chapter 2
How to create and edit network maps using the map toolbar Chapter 3
and commands
A description of polling, trapping, and configuring alarms Chapter 4
(continued)
2 ABOUT THIS GUIDE
How to use the SNMP Manager to query SNMP devices and Chapter 5
display query results
What to do if you are having difficulty getting HP OpenView to Chapter 6
work
The HP OpenView Visual Basic custom controls that are Chapter 7
provided for application development
A list of all the HP OpenView commands and tools and their Appendix A
functions
How to configure Notify! Connect Appendix B
Conventions Table 1 and Table 2 list conventions that are used throughout this
guide.
Table 1 Notice Icons
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
Convention Description
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” When you see the word “enter” in this guide, you must
and “type” 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 Menu commands or button names appear in italics.
and buttons Example:
From the Help menu, select Contents.
Words in italicized Italics emphasize a point or denote new terms at the place
type where they are defined in the text.
Words in bold-face Bold text denotes key features.
type
4 ABOUT THIS GUIDE
OVERVIEW
1
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
Applications
HP OpenView
* Maps * Alarms
User Devices
* Autodiscovery * SNMP Manager
Applications
User Autodiscovery
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.
CH1-A3
CH1-A4
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.
CH1-A5
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.
CH1-A6
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.
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.
CH1-A7
CH1-A8
Figure 1-8 SNMP Manager can be used to obtain information from devices or
change device settings
CREATING NETWORK MAPS
2 AUTOMATICALLY
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
Configure
Discovery Discovery
Networks
IP and IPX Autodiscovery searches IP, IPX, and VINES networks, identifies devices
Discoveries 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.
Preparing for a To start a discovery, you need to know some information about your
Discovery own network and the networks you want Autodiscovery to search.
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
You can use the form provided here to record the information.
IP Subnet Mask . . .
IP Network Addresses . . .
. . .
. . .
IP Router/Gateway . . .
Address
IP Router/Gateway Community Name
IPX Network Names
Configuring Before you can run a discovery, you need to enter information
Autodiscovery 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.
CH3-05
2-4 CHAPTER 2: CREATING NETWORK MAPS AUTOMATICALLY
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’s IP Subnet Mask – Enter your subnet mask. This mask should be
Settings 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.
Networks
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
Preparing for a Discovery 2-5
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.
CH3-04
2-6 CHAPTER 2: CREATING NETWORK MAPS AUTOMATICALLY
For more information about how to use the Customize Device Access
dialog box, see Chapter 4.
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.
CH3N-04
IPRouterAskForCommunity=yes
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.
Preparing for a Discovery 2-9
CH3A-07
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.
CH3A-06
2-10 CHAPTER 2: CREATING NETWORK MAPS AUTOMATICALLY
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.
User-Specified Devices
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.
CH3-06
The list box in the Discovery Manager displays the address, device
name, and System Description MIB variable of each discovered
SNMP device.
Display – You can control the contents of the device list by choosing
one or more of the display options.
Totals – This box displays current totals of devices and networks for
the display list and for the Autodiscovery database.
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.
Maintaining the You can save the contents of the Autodiscovery database. If the
Autodiscovery Autodiscovery database has more information than you want, you
Database 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.)
CH3-08
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.
CH3A-04
Creating Submaps Once you have used Autodiscovery to identify network devices, you can
of Discovered create submaps containing the discovered devices. To create submaps
Devices using information obtained from Autodiscovery you:
Configuring You can associate a more meaningful name (for example, Denver Office
Preferred Names #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.
CH3-11
Setting Layout You can change the general appearance of your layout map by
Options 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.
CH3-13
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 The Do Basic Layout command creates a new submap named
Layout “ALLNETS” with the notation “Internetwork View” and a set of
“Network View” submaps consisting of one submap for each network
containing discovered devices.
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
MAP:ALL NETS
Internetwork View MAP:C
Segmented View
Network B
Network C.S2
Network A Network C
Network C.S1 Network C.S3
Internetwork View
All Nets
CHN-24
CH3N-18 CH3N-20
Network View Network View
0000BEEF CH3N-19
Segmented View BABABABA
0000000A
CH3N-24
Segment View S3
CH3N-23 CH3N-21
Segment View S1 Segment View S2
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.
You can assign a background image for a map that shows the physical
location of the network devices.
CH4-01
Drawing A Simple Before you create a network map, you need to know the physical
Map 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 B
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.
3-4 CHAPTER 3: CREATING NETWORK MAPS MANUALLY
World
Creating a Map File To create a map file and home submap, follow these steps:
and Home Submap
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.
Drawing a Network Map 3-5
CH4-02
4 Choose Set Home Submap from the Edit menu and select WORLD as
the home submap.
CH4-03
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.
CH4-04
Adding Submap To add submap symbols to your map, follow these steps:
Symbols
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).
CH4-05
CH4-07
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.
3-8 CHAPTER 3: CREATING NETWORK MAPS MANUALLY
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.
Add Remaining If you have the “Create Submaps Automatically” option turned on in
Submaps 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
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.
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 You can disable OpenView's map editing to prevent accidental
Editing Feature 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.
3-10 CHAPTER 3: CREATING NETWORK MAPS MANUALLY
CH4-17
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.
CH4-19
Map Toolbar and OpenView provides a toolbar and menu items for creating and
Commands modifying network maps. Each of these tools and commands are
described below.
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
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.
CH4-21
CH4-22
Tool Description
Scissors Cut (same as in the Edit menu).
Alarm Bell Display the alarm log. Icon color reflects the
highest unacknowledged alarm.
3-12 CHAPTER 3: CREATING NETWORK MAPS MANUALLY
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)
Select objects
Choose text style
Add text
Add lines
Choose line style
Add connections
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.
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 and You can select lines in 8 thicknesses. Thin lines are available in five
Connections patterns, including solid. If you want the line to be attached
(“connected” to a symbol) use the Connection button.
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.
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.
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
Select on Map This function selects the desired object on the map.
OpenView provides several different ways that you can monitor the
devices in your network. You can:
Device
OpenView
Map
Alarms
Audible alarms,
forwarded alarms,
Applications triggering of programs
Customizing You can associate with a network address control information that is
Device Access 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.
CH5-01
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:
Customizing Device Access 4-3
CH5-02
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.
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
4-4 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
Polling Network To poll network devices, you perform the following tasks:
Devices ■ 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.
CH5-04
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 of You can poll any device in the map that has an IP or IPX address.
Devices to Poll
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.
Polling Network Devices 4-5
CH5-05
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 to To remove devices from the polling list, follow these steps:
Poll
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.
4-6 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
CH5-08
Loading a Selection Use the Load Selection List command to get a previously saved list. A
List 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.
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 System OpenView has preset default values that control the polling interval and
Polling Parameters 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.
CH5-10
Configuring Device There are system defaults for six classes of device. OpenView uses the
Types 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
4-8 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
Ch5-10a.gif
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.
Configuring You can override the system polling parameters for individual addresses.
Parameters for Use this for setting poll rates for those devices requiring shorter
Selected Devices intervals such as routers, bridges, and hubs. Use longer intervals for
remote devices.
CH5-12
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.
4-10 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
Turning Polling On To start the polling process, choose Start Polling from Polling in the
and Off 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.
Monitoring Traps Traps are specific types of messages that are generated by some devices
from Network to indicate a change in their status. When a device is installed on the
Devices 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
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.
CH5-14
Selecting a Device To select a device class to change the default trap response, follow
Class these steps:
1 Click ADD.
CH5-17
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
Monitoring Traps from Network Devices 4-13
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.
CH5-19
Specifying Traps for a You can create a list of the traps that OpenView will respond to for a
Device Class 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.
4-14 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
CH5-22
Choosing Trap Alarm You can choose to update the map status (change color of map
Actions 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:
Monitoring Traps from Network Devices 4-15
Alarm Actions
CH5-23
Description Field You can specify how information from the trap packet is displayed in
Variable Substitution the Description and Extended Description fields using field variables.
Syntax 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.
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).
Automatically The Acknowledge on Matching Trap and Variable text box allows you
Acknowledging to clear a trap when a new specified trap is received. The original trap
Alarms Generated is moved from the current alarm log to the history alarm log. A variable
by Traps 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
Managing Alarms 4-17
CH5-25
Selecting Map The map symbol of a device is displayed in the color that represents the
Status Options 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.
Critical Red Red The device is unavailable. It may be down or in a critical state.
Major Dark Red There is a problem with the device. Some degradation of function exists.
Red
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.
Informational Magenta Magenta An informational message about this device has been sent by an
application.
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
Managing Alarms 4-19
Europe
USA Japan
= Warning
= Critical
CH5-34
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.
Managing Alarms 4-21
CH35A
CH5-35
CH35B
■ 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
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.
CH5-30
You can list the alarms either by the order received or severity using the
Sort by controls in Customize Alarms in the Options menu.
CH5-37
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.
Managing Alarms 4-23
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 for You can display selected groups of alarms from the alarm log. Alarm
Display 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)
CH5-38
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.
4-24 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
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.
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 and To acknowledge or “clear” an alarm, select the alarm in the current list,
Deleting Alarms 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 delete all of the alarms from the history log, click on Delete All. To
delete selected alarms from the history log, click on Delete.
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 You can control the way OpenView processes alarm information. The
Processing 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
4-26 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
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 alarm
regardless of the Sort By setting.
Alarm Sound Alarm Sound – The settings control the sounds generated by an alarm.
Settings 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
Disable Sounds – This turns off sound for all alarms, Sound Once will
play the appropriate alarm sound when the alarm is generated. The
Configuring Alarm Processing 4-27
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 Sound OpenView can generate a sound when a device changes status, and a
Configuration 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.
CH5-49
Alarm Status The Status Propagation field controls how alarms are passed between
Propagation 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
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.
CH5-50
CH5-46
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.
CH5-47
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.
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>
%y Object type
For example, if the entry in the OVWIN.INI file for RunCritical was:
RunCritical=prog.exe %t - %o - %a
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>
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.
This will send the following pager message to OpenView when a critical
alarm occurs:
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
4-32 CHAPTER 4: MONITORING DEVICES ON THE NETWORK
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.
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:
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.
DMI Manager 4-33
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
CH6-03
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:
CH6-04
Selecting Variables to The accessible SNMP variables are listed in the Variables box and may
Query 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.
5-4 CHAPTER 5: MANAGING SNMP NETWORK DEVICES
iso
org
dod
internet
mib-2 enterprises
Moving Around the To move around the variable tree, follow these steps:
Variable Tree
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).
CH6-05
Defining a Query 5-5
Entries in the variables list are displayed using the following format:
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.
Selecting a Variable To select a variable to use in the query, follow these steps:
to Use in the Query
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 Variable To remove a variable from the query list, follow these steps:
From the Query List
1 In the Selected variables box, highlight the variable you want to
remove.
2 Click Remove.
It disappears from the Selected Variables box.
5-6 CHAPTER 5: MANAGING SNMP NETWORK DEVICES
CH6-09
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.
CH6-12
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.
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.
CH6-14
6 Click OK.
Selecting a Query Selecting a query allows you to perform, edit, or delete the query.
CH6-16
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.
Removing a Query Since there is a limit of nine queries that are listed in the menu, you
from the Menu may want to remove a query from the menu commands.
CH6-14
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.
Displaying SNMP Query Results 5-9
CH6-17
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 After you select the devices and variables you want to query, you can
Query Results display the query results as a table or a graph. This section describes
how to display query results as a table.
CH6-18
5-10 CHAPTER 5: MANAGING SNMP NETWORK DEVICES
Displaying a Query Table queries can be for a single table variable (a table variable is
as a Table displayed in {curly braces} in the variable list), for one or more
non-table variables.
CH6-19
Command Description
Polling Polling sets the number of seconds between updates when a
query is performed.
A zero (0) means polling takes place only once when the Per-
form or Start button is pressed.
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.
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,
5-12 CHAPTER 5: MANAGING SNMP NETWORK DEVICES
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.
CH6-20
CH6-21
Displaying SNMP Query Results 5-13
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.
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.
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.
CH6-24
Displaying a Query If single value variables are selected, you can view your query results as
as a Graph 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.
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.
Displaying SNMP Query Results 5-15
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 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.
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.
CH6-28
CH6-23
CH6-27
Changing a You can change Read/Write variables when they are displayed as a
Variable's Value table.
Managing the The Manage Database command is accessed from the SNMP Manager
SNMP Manager in the OpenView Control menu. Manage Database accesses a compiler
Database 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.
Status
Available MIB
files list
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
Color Description
Green indicates a ready state and, where appropriate, a
successful compile
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.
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.
iso
org
dod
internet
mib-2 enterprises
There are two areas where you might commonly add MIBs:
■ MIBs dependent upon MIB-2
■ Vendor-specific private MIBs
MIBs Dependent MIB-2 dependent MIBs, such as rmon, would be added to the
Upon MIB-2 structure under the MIB-2 group:
5-20 CHAPTER 5: MANAGING SNMP NETWORK DEVICES
enterprises
mib #1 mib #2
CH6-A4
Selecting MIB Files OpenView comes with a MIB-2 SNMP database compiled from
to Add to the RFC1213.MIB. This file is located in the MIBS directory of OpenView.
Database
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.
MIB Structure 5-21
Things You Should Diagnosing problems requires that you provide as much configuration
Know 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.
Phone Fax
Europe
English (+31 20) 581-3330
Dutch (+31 20) 581-3331
French (+31 20) 581-3332
German (+31 20) 581-3333
Asia / Pacific
Australia +61-3-9272 2895 +61-3-9898 7831
Korea +82-2-769 0114 +82-2-3270 7084
Taiwan +886-2-717-9651 +886-2-715-3107
China +86-10 65053888 ext 5901 +86-10 65924566
Faxback - HP First
U.S. (800) 333-1917
non U.S. (208) 334-4809
Header
File Name: connect.ovm
Date of modification: Mon Sep 04 14:28:52 1992
File Version 7
Number of Symbols 15
Number of Names: 6
Number of Labels: 5
Number of Submaps: 1
Current submap context: 0
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
LED Control
OV1
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.
7-2 CHAPTER 7: CUSTOM CONTROLS
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.
LED The LED displays SNMP values DisplayType: Integer ■ Round (0)
through a simple binary “LED”. Sets the type of LED to display: ■ Square (1)
Continued
7-4 CHAPTER 7: CUSTOM CONTROLS
Min: Integer
This property sets the lowest
value that will be displayed on
the gauge. It sets the lower limit
of the display.
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 The following table lists the properties supported by the OpenView
Control Properties custom controls.
(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).
7-6 CHAPTER 7: CUSTOM CONTROLS
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.
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.
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.
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.
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.
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.
7-8 CHAPTER 7: CUSTOM CONTROLS
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.
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 - Bool
2 - Integer
3 - BitStr
4 - OctetStr
5 - Null
6 - ObjectID
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:
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
Example: Place an SNMP Text box control on a form and then assign
the following values:
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
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.
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.
Summary of Control Properties 7-11
Alarm and Threshold There are several properties that can be set to provide visual feedback
Properties of 'normal' and 'alarm' conditions for the variable being polled. The
alarm related properties are:
Alarm MaxThreshold Alarm Values
Trap MaxReset AlarmValues
MinThreshold NormalColor
MinReset AlarmColor
NormalValues
Alarm – tells the control how to evaluate any thresholds that you have
set. This property can take on the following values:
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 Access MIB Tables are more complicated to access. An SNMP table is generally
Properties 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.
■ InstanceIndex
■ TableIndex
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:
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
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.
Once you have completed your program, you should compile it so that
it will use fewer system resources and be suitable for distribution.
Debugging Visual When developing applications, it is helpful for testing to execute them
Basic Applications 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.
7-16 CHAPTER 7: CUSTOM CONTROLS
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
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.
[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.
7-18 CHAPTER 7: CUSTOM CONTROLS
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.
Registering Your In order to launch your application from OpenView you must register it
Visual Basic with XOVSRVR. This is done with entries in the XOVSRVR.INI file in the
Application \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.
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
7-20 CHAPTER 7: CUSTOM CONTROLS
[Programs] Section
This [Programs] section lists the Visual Basic applications and optionally
supplies startup information. The syntax is:
TaskName = Program filename[, InitShowCmd]
where:
Program filename is the full path and file name of the your
application's executable file (ex. OVTEST = c:\ov\ovtest.exe).
Example
[Programs]
PROG1=c:\myapp\myexe1.exe
PROG2=c:\myapp\myexe2.exe, 2
PROG3=
Registering Your Visual Basic Application 7-21
Menus and OpenView applications have two types of menu items: those which
Commands 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.
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.
7-22 CHAPTER 7: CUSTOM CONTROLS
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 Manager
Command 1=Command &1,HubView,Start HubView
Command 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
Registering Your Visual Basic Application 7-23
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.
where:
Flag identifiers which are not mutually exclusive may be or'ed together
using a vertical bar:
OVM_DISABLED | OVM_OBJSPEC
Example
[MenuIDs]
SMGR=&SNMP Manager,OV_IDMCONTROL,Mib manager tool
[CommandIDs]
SMGR1=&Define Query...,SMGR,0x104,OVM_ENABLED,MIB,,Get or Set Mib variables
SMGR2=&Select Query...,!SMGR,0x101,OVM_ENABLED,MIB
SMGR3=&Manage Database...,SMGR,0x100,OVM_ENABLED,MIBCOMP
MyHelp=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 Utilities
HubView1=&Get Data,Command 1,0x701,OVM_ENABLED,,,Fresh Start,SYM_HUB
HubView2=&Report,Command 1,0x702,OVM_ENABLED,,,Print Report HubView
HubView3=&Sleep,Command 2,0x703,OVM_ENABLED|OVM_CHECKED,,,Pause HubView
HubView4=&Quit,Command 2,0x704,OVM_ENABLED,,,End HubView
Registering Your Visual Basic Application 7-25
HUB1
HUB2
[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.
SYM_LOCAL_PRINTER SYM_HUB
The following example will register the hub symbol to the Hubview
application:
[Objects]
SYM_HUB=HUBVIEW
Adding Features In order for you to make use of the additional program launch and
To Your Application 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.
OV2
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.
7-28 CHAPTER 7: CUSTOM CONTROLS
OPENVIEW COMMAND AND
A TOOL REFERENCE
Menu Commands The following tables list the OpenView commands by menu.
Command Description
New Start a new (empty) map.
Print Object List Print a list of all objects in the map, sorted by submap.
Load Selection List... Select a set of objects whose names have been saved
in a file.
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.
View Menu
Commands
Command Description
Zoom 1 Set the display to normal.
Monitor Menu
Commands
Command Description
Describe... Add a name, label, address(es), and notes to
the selected object.
Configure System Defaults... Change interval and alarm action defaults for
a device.
Configure Device Parameters... Change interval and alarm action defaults for
a device.
Control Menu
Commands
Command Description
Browse Web Home Page Display Web Home Page associated with device.
Autodiscovery Menu
Commands
Command Description
Configure Configure the Autodiscovery facility.
Options Menu
Commands
Command Description
Protect Map... Enable or disable manual editing of a map file
using a password.
Window Menu
Commands
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.
Help Menu
Commands
Command Description
HP OpenView Index... Access on-line help 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.
pg158.tif
Toolbar Functions
Tool Description
Scissors Cut (same as in the edit menu).
Camera Copy “
Paste Paste “
Eraser Delete “
Pencil Describe “
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.
CONFIGURING NOTIFY! CONNECT
B
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.
OVWIN.INI In order to have an alarm generate a page you must make an entry in
Configuration 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
Notify! OpenView makes the following default entries in the Notify database:
Configuration ■ 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
B
background 3-3, 3-5
Basic IP Discovery command
Autodiscovery 2-12
Basic IP Discovery field
Autodiscovery 2-12
Symbols Basic Layout Options dialog 2-15
.BMP format 3-5 Basic, Discovery 2-2
.OVD files 3-1 bitmap 3-3, 3-5
.OVI files 3-1
.OVS files 3-1
.TIF format 3-5 C
checking alarms 4-19
Clear Discovery Database command 2-13
A clearing alarms 4-25
Add command 3-12 closing the alarm log 4-25
Add window 3-12 colors, status 4-17
adding connection example 3-8 COMCHECK utility 2-3
adding lines, example 3-7 community name 2-2
address compiling MIBs, defined 1-7
IP 2-2 component 3-13
alarm aging 4-25 compound icon 3-13
alarm clearing 4-25 Compound Object 3-13
alarm configuration 4-25 computer, type 3-13
alarm customizing 4-22, 4-25 Configure Discovery Networks dialog 2-3
alarm database 4-32 configuring alarms 4-25
alarm DDE access 4-31 Connections 3-1
alarm filter 4-23 connections 3-13
alarm forwarding 4-28 connections, example 3-8
Alarm Forwarding dialog box 4-29 Control Menu A-3
alarm frequency 4-25 conventions
alarm log, closing 4-25 notice icons, About This Guide 2
alarm log, using the 4-20 text, About This Guide 2
alarm propagation 4-25 create a new map 3-4
alarm selection for display 4-23 creating, home submap 3-4
alarm set 4-24 creating, map 3-4
alarm sorting 4-22 customizing alarms 4-22, 4-25
alarm sounds 4-25 customizing device access 4-2
alarm system, overview 1-6 customizing the describe function 3-7
alarms 4-21 cut, used with selection list 3-14
alarms, checking 4-19
alarms, overview 1-3
alarms, running programs from 4-30 D
alarms, sorting by status 4-23 database
alarms, sorting by time 4-23 Autodiscovery 2-13
application 3-12 Database Contents command
ARP 2-2 Autodiscovery 2-12
ARP caches 2-2 database, alarm 4-32
AutoArrange Redrawn Maps 2-16 DDE access from alarm 4-31
autodiscovery default gateway 2-2
setup 2-3 deferring the describe function 3-7
2 INDEX
Define Query
SNMP Manager 5-1 I
describe function 3-7 icons, application 3-12
Device Classes 2-8 Ignored Devices. 2-9
device list 3-3 IP 2-2
device selection IP address 2-2
SNMP Manager 5-2 IP Default Gateway field
diagnostic utility 6-3 autodiscovery 2-4
disabling 3-10 IP Subnet Mask field
Discover All IPX Networks field autodiscovery 2-4
autodiscovery 2-5 IPX 2-2
Discovery Manager dialog 2-11
display symbols 3-13
Display window L
Autodiscovery 2-12 layout options
drawing a 3-2 Autodiscovery 2-15
drawing a map 3-2, 3-3 autodiscovery B-1, B-2
Dump Discovery Database command 2-13 legend, status 4-17
Dump utility 6-3 levels, propagation of status across 4-18
line weight 3-13
Lines 3-1
E lines 3-13
Edit Menu A-2 lines, example 3-8
edits 3-10 list of devices 3-3
example submap 3-3 Load Selection List 3-14
Extended Discovery command load selection list 4-6
Autodiscovery 2-12 local submap 3-3
Extended Discovery field
autodiscovery 4-2
Extended, discovery 2-2 M
Mac addresses
Autodiscovery 2-16
F Management Information Base (MIB) 5-1
File Menu A-1 Manager Database command
File, Server 3-13 SNMP Manager 5-17
filter, alarm viewing 4-23 managing alarms 4-21
format, bitmap 3-5 managing Autodiscovery 2-6
frequency of alarms 4-25 map 3-2
map example 3-3
map printing 3-9
G map, saving 3-9
gateway mapping procedure 3-3
default 2-2 maps, overview 1-2
generic devices mask
Autodiscovery 2-11 subnet 2-2
gets, defined 1-7 Master Console, alarm forwarding 4-29
GoTo symbol 3-14 MIB
GoTo, symbol 3-14 SNMP Manager 5-1
grid 3-5 MIB structure
SNMP Manager 5-19
MIB variable
H Autodiscovery 2-11
Help Menu A-5 MIB, adding
hierarchy 3-3 SNMP Manager 5-21
home submap 3-2, 3-3, 3-4 MIB, defined 1-7
INDEX 3
MIB, deleting
SNMP Manager 5-21 Q
MIB-2 queries, defined 1-7
SNMP Manager 5-19 queries, selecting
MIBs, private SNMP Manager 5-6
SNMP Manager 5-20 query
multiple adds 3-12 SNMP Manager 5-1
N R
name field regional submap 3-3
SNMP Manager 5-2 Reset Display command
Netware services 2-2 Autodiscovery 2-12
Network Address field rmon
SNMP Manager 5-3 SNMP Manager 5-19
network map 3-2 routers
Networks field used in autodiscovery 2-2
Autodiscovery 2-11 running programs from alarms 4-30
node 3-13
node in alarm viewing 4-24
S
Save Selection List 3-14
O save selection list 4-6
object in alarm viewing 4-24 Save Selection List As 4-6
object lists, printing 3-9 saving a selection list 4-6
object name, in alarm viewing 4-24 Segmented View Symbol Spacing 2-16
object status in alarm viewing status 4-24 Select Object 3-13
object type, in alarm viewing 4-24 selecting alarms 4-23
options for layout selection list 3-14
Autodiscovery 2-15 selection pointer 3-13
Options menu A-5 sets, defined 1-7
OVALINS.* files 4-32 setting variables
OVDUMPIT file SNMP Manager 5-17
Autodiscovery 2-13 SNMP
OVM files 3-1 in discovery 2-2
OVMDump program 6-3 SNMP Manager 5-1
SNMP Manager, overview 1-7
SNMP, defined 1-7
P sorting alarms 4-22
password 3-10 sorting alarms by status 4-23
paste, used with selection list 3-14 sorting alarms by time 4-23
pointer 3-13 sounds in alarms 4-25
polling devices 4-4 status colors 4-17
polling parameters 4-7 Status field
polling, overview 1-4 Autodiscovery 2-12
positioning symbols 3-5 status legend 4-17
printing a map 3-9 status propagation 4-18, 4-25
printing, maps 3-9 status sorting alarms by 4-23
private MIBS status, alarms 4-21
SNMP Manager 5-20 sub object in alarm viewing 4-24
problems 6-1, 7-1 submap symbol 3-13
procedure for drawing a map 3-3 submap width
propagation of alarms 4-25 Autodiscovery 2-16
propagation of status 4-18 submaps 3-1, 3-2
Protect Map 3-10 subnet mask 2-2
4 INDEX
subobject + 3-13
support, technical 7-1
symbol 3-13
symbol sets 3-12
symbol spacing
Autodiscovery 2-15
symbol, GoTo 3-14
symbol, submap 3-13
symbols 3-1
symbols, application 3-12
T
technical support 7-1
technical, support 6-1
Text 3-13
text size 3-13
text tool 3-13
text tool, underline 3-13
text, example 3-8
text, style 3-13
thickness 3-13
thickness, line 3-13
time, sorting alarms by 4-23
Topology Discovery 2-8
traps 4-10
traps, overview 1-5
troubleshooting 6-1, 7-1
U
used in a label 3-13
V
variables, setting
SNMP Manager 5-17
View menu A-2
viewing alarms 4-22
views, of a network 3-2
W
walking a map 3-2, 4-19
weight, line 3-13
Window Menu A-5
Workgroup Node Manager, overview 1-1