HP (Hewlett-Packard) 7 SNMP User Manual

hp industry

november 2002

standard servers

technical

white paper

table of contents

Insight Manager 7 SNMP Extensions utility

abstract 2 take control of the management environment 2 management basics 2

information retrieved from MIBS 5 SNMP operations by agent 5 how can SNMP Extensions help? 6

SNMP Extensions features 7

setting up the environment 7 the set of installed MIBs 8 protecting source MIBs 8 managing MIBs from Insight Manager 7 8

registering a MIB 10 why registration fails 11 unregistering a MIB 12 uploading a MIB 12 editing registered MIB information 12 unregistering an installed MIB 14 unregistering a MIB from the MIB Registration page 14

deleting unregistered MIBS 14

using trap categories 15

using SNMP Explorer 16 managing MIBs from the batch command 19

command syntax conventions 19 the command syntax 19

command switches 20

running the mCompile command 21

a command line example 22

troubleshooting a failed registration 24

registration error messages 24 compiling a MIB with an Error: badmib.MIB 25 the referenced badmib.mib 25

for more information 34

Insight Manager 7 SNMP Extensions utility

abstract

Insight Manager 7 is a systems management application that lets you monitor the status of a

device, its component objects, and their attributes. Insight Manager 7 reports on the device status, creates event and trap reports on device conditions, and performs a specific set of actions on managed devices.

Insight Manager 7 includes SNMP Extensions Toolkit, a group of components that allows you to manipulate your management environment. You can use SNMP Extensions from the graphical user interface of Insight Manager 7 or from the command line.

SNMP Extensions consists of the following components.

• SNMP MIB Registration

• SNMP MIB Upload

• MIB Check

• Trap Editor

• Trap Categories Editor

• Command Line Utility

take control of the management environment

management basics

Over time, the typical network changes in topology, function, and content. As an administrator,

you are challenged to manage devices that are not fully recognized by your management application. How can you address the problem of classifying the devices? SNMP Extensions can help you by providing ways to add input to your network management.

To use SNMP Extensions successfully, you should be familiar with the following terms and

concepts.

Management—Management is the process of acquiring information about devices on a network or enterprise. Management if performed when an application, such as Insight Manager 7, requests data or accepts traps (a type of message) from devices on a network. The management application communicates the request and receives responses to the request using a protocol like SNMP (Simple Network Management Protocol) for communication.

SNMP—SNMP is the most commonly used protocol for exchanging management information between devices. SNMP retrieves data from a target device. The data is accessed through an SNMP agent, a program that interrogates the device and returns the response to the management application. In order for the devices to be monitored (read) or controlled (written to) by a management application, an agent must reside on the device or interact with the device. The data about the device is found in a MIB (Management Information Base).

MIB—A MIB is a repository of information. A MIB describes manageable objects or devices. (An SNMP manageable object and an Insight Manager 7 device are generally equivalent. Either term refers to SNMP-manageable entities).

Insight Manager 7 SNMP Extensions utility

The MIB is a virtual mapping of variables to physical hardware and its related devices. SNMP

abstracts the control of the device through these variables. The below figure illustrates the interaction of the management application, the agents on a device, and the MIB databases. The configuration in this diagram shows two MIB databases. Multiple MIB databases within the same configuration should have the same versions of a MIB. MIB databases must be synchronized so interpretations of data are uniform.

Management Application Agents

MIBs

The MIB is analogous to a database schema because it represents data and data structures.

MIBs have been defined for TCP/IP routers and hosts, interface types, such as token ring and FDDI, and devices, such as servers and bridges. HP has defined MIBs for all of its SNMPcapable devices. These MIBs are pre-compiled into the database and can be used by Insight Manager 7.

Other third-party devices like routers and hubs exist on a network. Vendors of these network devices also define MIBs. When the vendor MIB is registered into the database, you can use Insight Manager 7 to monitor and control the devices.

The MIB structure is explained in the IETF (Internet Engineering Task Force) Standards RFC 1155. Because the MIB structure resembles the directory and subdirectory file structure used for an operating system, it is often referred to as a tree with a root.

MIB files often contain groups of variables that define the types of information that can be retrieved from a device. MIB information and characteristics include an object identifier, or OID, and a unique identifier that identifies the MIB and the variable. A variable can have one or more values. The OID is in numeric dot format. The tree structure determines the unique name and OID notation for each manageable entity.

MIB variables declare certain characteristics of the device, such as the operating system. HP MIBs include information like version numbers and product names. For example, the following table shows variables for an HP server running Windows NT 4.0. The values for the variables include the product and other information derived from the MIB database.

Insight Manager 7 SNMP Extensions utility

variable name and description

Syslocation

The physical location of this node. (For example, the telephone closet, 3 floor).

SysDescr

A textual description of the entity. This value should include the full name and version identification of the system’s hardware type, software operating system, and networking software. It is mandatory that this only contain printable ASCII characters.

SysObjectID

The vendor’s authoritative identification of the network management subsystem contained in the entity.

OID data type value

1.3.6.1.2.1.1.6 ASCII String MRO1-2/KL24

1.3.6.1.2.1.1.1 ASCII String Hardware: x86 Family 6 Model 3 Stepping 4 AT/AT COMPATIBLESoftware: Windows NT Version 4.0 (Build Number: 1381 Uniprocessor Free)

1.3.6.1.2.1.1.2 Object

Identifier

1.3.6.1.4.1.311.1.1.3.

1.1

This value is allocated within the SMI enterprise subtree (1.3.6.1.4.1) and provides an easy and unambi

uous means for determining what kind of box is being managed.

For Example, if vendor Flintstones, Inc. was assigned the subtree

1.3.6.1.4.1.4242, it could assign the identifier

1.3.6.1.4.1.4242.1.1 to its Fred Router.

Insight Manager 7 SNMP Extensions utility

information retrieved from MIBS

MIBs often organize their information by object groups that contain a related collection of variables. MIB variables contain attributes that include:

• The data type

• A textual description

• The read or write access

• Whether the variable is mandatory or optional

MIBs contain the traps that the device can generate. Traps are messages the device sends when specific conditions occur. Traps can include:

• The trap object identifier (trap OID)

• The agent IP address

A trap can be interpreted and formatted for display.

MIBs can contain one or more MIB variable bindings. Bindings convey useful information associated with the condition that triggered the trap. Bindings include the Description, the Type, the Category, and the Severity. For example, the trap cpqclusterFailed has the following bindings:

SNMP operations by agent

binding content

Description This trap will be sent any time the condition of the cluster

becomes failed

Type Cluster Failed

Category Cluster

Severity Major

The agent performs the following SNMP operations:

GET and GET NEXT—Retrieve information about the managed device and return the information to the management application. In Insight Manager 7, the terms Monitor and Read are equivalent to a GET.

SET—Changes the value of a managed device variable in the MIB database. Only variables whose device definitions have read and write access can be set. In Insight Manager 7, the terms Control and Write are equivalent to a SET.

TRAP—Sends messages to the management application when a change or error occurs in a managed object. The trap is the only operation initiated by the agent without a specific request from the management program. The MIB defines the syntax of any trap messages initiated by the agent. Systems must be configured to receive traps.

Insight Manager 7 SNMP Extensions utility

In order to send and receive traps, the managed object and the management application must be configured correctly:

• The managed object must have a trap destination to direct traps to the server running the management application.

• The management server must be configured to receive the traps.

• The correct SNMP security needs to be established between the managed device and

the management server using SNMP community strings, a type of authentication. If the community strings do not match, communication between the devices does not occur.

• The management application must understand the format of the trap.

how can SNMP Extensions help?

SNMP Extensions can help because it enables you to extend the SNMP V1.0 Management Information Base (MIB) of Insight Manager 7. SNMP Extensions lets you fully explore most devices on your network, broaden the scope of your network management, and prepare you to manage the network of the future.

Exploring your network—You can achieve greater understanding of your network because you can interrogate most MIB variables that have been incorporated into SNMP-compliant devices. Better understanding of the variables makes it easier to create Insight Manager 7 tasks that are based on SNMP events.

Broadening your management scope—Most likely, your network includes third-party devices. Insight Manager 7 ships with a variety of third-party MIBs, not all Third-party MIBs are registered by default. Using SNMP Extension, you can register the third-party MIBs.

Registration of third-party MIBs improves manageability in several ways:

• Registration enables the discovery process of third-party devices

• Registration adds event recognition

• Registration enhances event display

New versions of MIBs are available periodically. SNMP Extensions allows you to update your MIB database to the latest MIB revisions so you can discover and identify new devices using the latest information about the devices.

SNMP Extensions adds to event recognition by allowing you to optimize the event data to individual network requirements. For Example, you can include references to maintenance procedures. SNMP Extensions also permits you to construct your own interpretation of device events through the use of Trap Categories. You can organize your device maintenance by creating logical event categories. Then, exercise your judgment in assigning events to them. Furthermore, you can use the event categories to query for events according to a category of traps.

Preparing your network for the future—As time goes by, new network devices will be developed that you wish to add to your network. You can add the new devices, discover, and identify them if you have an associated MIB to register.

Insight Manager 7 SNMP Extensions utility

In addition to external MIB sources for third-party devices, you can continue to register new releases of HP MIBs that are distributed between releases of Insight Manager 7. New MIBs are distributed periodically on Management CDs. For the latest versions of HP MIBs, visit the website

SNMP Extensions features

http://www.hp.com./

SNMP Extensions contains a graphical user interface to a MIB compiler that is a part of Insight Manager 7. It also has a command line utility that you use from a DOS command box. The command line utility performs a superset of the functions you can perform through the graphical interface.

IMPORTANT: Simultaneous use of both tools can have adverse affects on SNMP Explorer, Automatic Discovery, device identification, and event viewing.

SNMP Extensions contains the following functions:

MIB Registration—MIB Registration compiles new MIBs into the Insight Manager 7 database. MIB Registration also includes the Unregister function. Unregister removes the information about a registered MIB from the database. You might unregister a MIB before installing a new version of the MIB or when the device associated with the MIB is removed from the network. You can use MIB Register and MIB Unregister from either the Insight Manager 7 graphical user interface or from the command utility.

MIB Trap Edit—Trap Edit lets you customize the MIB information by modifying the text that describes traps. For example, replace cryptic default text with an easily understood message. You might include instructions, such as Refer to our website http://… for faster problem resolution. You can edit traps from either the Insight Manager 7 graphical user interface or from the command utility.

setting up the environment

MIB Upload—Enables you to copy a MIB from your browser system to Insight Manager 7 server and directory.

Trap Categories—Enables you to use default trap categories or create you own logical groups for trap assignments. The same trap categories are available when you create a query. Using your own category, you can monitor your choice of devices for specific traps. Trap Categories is not a command line option

SNMP Explorer—Displays a selected, registered MIB and its variables on discovered devices. Simply examining a MIB and its variables and descriptions enhances your understanding of the MIB and how it works with the device. You might choose to modify the description or other modifiable attributes of the variable. You can open SNMP Explorer from a Device Link from the Device page of SNMP-compliant devices. SNMP Explorer is not a command line option.

The SNMP Extensions toolkit is intended for system administrators and network managers, who are familiar with SNMP management, network fundamentals, and their operating system environment. Refer to the specific documentation for your network and operating systems. SNMP Extensions Toolkit requires the same hardware and software requirements of Insight Manager 7. Consult the Insight Manager 7 Technical Reference Guide on the Management CD for details.

Insight Manager 7 SNMP Extensions utility

The SNMP Extensions Toolkit is intended for administrators and network managers who also have administrator privileges in Insight Manager 7. SNMP Extensions requires administrator privileges because core server SNMP definitions of Insight Manager 7 might be modified.

the set of installed MIBs

Insight Manager 7 provides a set of MIBs that are already registered into the database. The default location for registered and non-registered MIBs is the following directory unless you have specified another at installation:

\Program Files\HP\ Insight Manager 7\compaq\protocol\snmp\Mibs

When you supplement the MIB set with new or revised MIBs, always copy them to this directory. The MIB Upload feature always installs the MIBs into the correct location. The registered MIBs and related files include:

• IETF Standard RFC 1213 Host Resources MIB and IETF Standard 1155 Structure of Management Information

• A set of HP MIBs, which are identified by the prefix CPQ, such as CPQCLUS. MIB, the HP cluster MIB or CPQIDE.MIB, the MIB for IDE drives.

• Third-party MIBs, such as the PATROL.MIB.

protecting source MIBs

managing MIBs from Insight Manager 7

An excellent practice in MIB management is to never modify the MIB. Therefore, SNMP Extensions was designed to enable changes to trap declarations and other trap information without modifying the source MIBs. SNMP Extensions creates an editable file called the editfile. The editfile is a textual revision file identified by the file extension of REV. The editfile is applied after the MIB is compiled

Because the changes are not made to the MIB, you can reinstall MIBs and replace the changes if the database is corrupted or deleted. Therefore, keep backup copies of the REV editfiles. You can find the REV files in the same directory as the set of installed MIBs.

\Program Files\HP\Insight Manager 7\compaq\protocol\snmp\Mibs

You can perform the most commonly used functions of SNMP from Insight Manager 7. These include:

• Registration of new HP and third-party MIBs

• Modification of registered MIBs and related browsing of all MIB variables

• Deletion of obsolete or unused MIBs

• Uploading new MIBs to be registered

• Use of trap categories for organization and event queries

Insight Manager 7 SNMP Extensions utility

starting SNMP Extensions

1. Browse to Insight Manager 7 on the server system using the URL for the server. For example:

http://server_name:280/

2. After the Device Overview page is displayed, click the Tools tab.

3. Select SNMP Extensions and click MIB Registration. The MIB Registration page is displayed.

4. Examine the elements on the page. You will see the lists of registered and unregistered MIBs and the options you have for working with them.

Insight Manager 7 SNMP Extensions utility

registering a MIB

Registration of a MIB compiles the information into the Insight Manager 7 database. MIBs require a short interval to become fully registered. The more information, such as the number of traps, the longer the registration takes.

When you register, you can create a logfile and an editfile for a MIB.

Logfiles—A logfile is a record of the MIB registration. A logfile is created in the subdirectory Program Files\HP\HP Insight Manager 7.07\log. It has the registered name of the MIB with the suffix of TXT. For example, the CPQClus.MIB log file is CPQCLUS.TXT. You can find the logfiles in the default directory:

\Program Files\HP\Insight Manager 7\log

Editfiles—An editfile, known as the REV file, is the mechanism that enables you to introduce edited MIB information into the database without modifying the source MIB. The editfile has the registered name of the MIB with the suffix REV. For example, the editfile for the CPQHLTH.MIB is CPQHLTH.REV.

You can find the REV editfile in the same directory as the MIBs:

\Program Files\HP\Insight Manager 7\compaq\protocol\snmp\Mibs

The editfiles that are provided have the addition of modifiable fields called #TYPE, #SEVERITY, and #CATEGORY. These fields have values for trap descriptions. When a MIB is registered using the REV files, the additional information is placed into the database. Once a MIB is registered, a REV file can be created from the database after the MIB is registered.

In the future, if you choose to register a MIB from its source file, the information that is contained only in the REV file will no longer be in the database. In addition, the information would not be in a REV file that was created from the database after the source MIB registration.

You should back up the REV file changes, so if the installed REV editfiles are lost or damaged, you can reinstall them from from your back up copy.

You can use the REV editfile in any of the following ways:

• If an editfile exists, you can edit it and maintain more complete information in the database. You can edit from the Insight Manager 7 or the command line.

• After you have registered a MIB, you can register the REV editfile.

• An accurate and recent MIB is your best source of device management information.

Insight Manager 7 SNMP Extensions utility

registering a MIB

1. Click the Tools tab.

2. From the menu, select SNMP Extensions and click MIB Registration.

3. Select a MIB from the Unregistered MIBs column.

4. At Options for Register, select either or both file creation options:



Then choose one of the following options:

Create Logfile

Use Editfile.

• Create Editfile—Registers the selected MIB (using the source MIB file), and

creates a new REV file if one does not exist for the selected MIB.

• Replace Editfile—Registers the selected MIB (using the source MIB file) and

overwrites the existing REV file in the MIB folder.

• Register Editfile—Registers the selected MIB using the existing REV file

contents to populate the database MIB tables.

why registration fails

5. Click Register. When registration is complete, the MIB is removed from the Unregistered MIBs column and is highlighted in the Registered MIBs column. If you do not see the MIB immediately, scroll to find it.

MIB registration typically fails for the following reasons:

• The MIB contains a syntax error—Syntax errors affect the MIB compilation phase.

SNMP Extensions can resolve some syntax errors, but if the error cannot be resolved, the registration fails. For example, if the MIB structure is invalid, the MIB cannot be compiled.

• Elements in the MIB are not unique—MIB module names must be unique. If you try

to register a MIB with a module name that is already used by another registered MIB, the compile will fail.

• The MIB has dependent MIBs that cannot be found—A new MIB will not have all

the components necessary to compile by itself. Most MIBs depend on other MIBs. If a MIB imports variables from other MIBs, the importing MIB needs a copy of the referenced MIBs to compile along with the specified new MIB. The importing MIB will resolve the unknown references from dependent MIBs. If the referenced MIBs are not in the correct directory, use the Upload feature and register them. Then reregister the failed MIB.

Note: A registration may appear to fail if the browser times out before registration is complete. However, the registration continues and will be successful as long as none of the failure conditions exist. During a timeout, you will lose your connection. To resume working in Insight Manager 7, log in again.

+ 23 hidden pages