HP SIM V5.1 User Guide (356920-009, January 2007)

Updating a MIB
1. Download and copy MIBs and any matching .cfg files to the mibs directory. The mibs directory is
typically located at c:\program files\hp\systems insight manager\mibs for Windows
and at /opt/mx/mibs for Linux and HP-UX.
Note: If a .cfg file is available and no customizations have been made, proceed to step 2.
2. Run mcompile to create and update any .cfg file that exists.
Note: If the old .cfg file had any customizations, these must be reapplied.
3. Run mxmib -a
updatedfile.cfg
to update the MIB data in the database.
Service trap and service MIB information
HP SIM ships with a version of the service MIB to support service traps sent by Open Service Event Manager
(OSEM) and Web-Based Enterprise Services (WEBES). The service MIB is comprised of the cpqservice.mib
and cpqservice.cfg files. To obtain the service MIB separately, see http://h18023.www1.hp.com/
support/svctools/ and select Service MIB Zip file under WEBES or OSEM. The zip file contains the .mib
and .cfg files. HP recommends you review the readme.txt file contained in the zip file for compatibility
instructions.
Beginning with OSEM 1.3.6, the tool must be configured to generate the new trap type by accessing the
Internal Settings for OSEM: HP SIM trap revision. WEBES sends the trap by default.
Related procedures
Viewing a MIB
Compiling a MIB
Unregistering a MIB
Editing a MIB
Related topics
Managing MIBs
Service notification events
Unregistering a MIB
HP MIBs can be unregistered using the command line. The command line interface (CLI) is the same for all
CMS types to include Windows, Linux, and HP-UX.
To unregister a MIB from HP SIM:
1. Open an MS-DOS window or UNIX shell.
2. Run mxmib -d
file.mib
to unregister the MIB in HP Systems Insight Manager (HP SIM).
Related procedures
Viewing a MIB
Compiling a MIB
Registering a MIB
Editing a MIB
Related topics
Managing MIBs
Service notification events
Presentation of SNMP traps in HP SIM
You can map a severity from a varbind to the event severity displayed in the event view. The mechanism
uses two keywords annotated as comments within the trap definition (VARBINDSEVERITY and
SEVERITYMAP). The following is an example of a trap definition:
Managing MIBs 341