HP Systems Insight Manager - Manual (Page 140)

FROM RFC1213-MIB
hpSwitchBladeType2-Mgmt
FROM HP-SWITCH-PL-MIB
agSlotNumber
FROM BLADETYPE2-SWITCH-MIB
ipCurCfgGwIndex
FROM BLADETYPE2-NETWORK-MIB
In this example, TRAP-TYPE and sysName are readily resolved as in the example above.
hpSwitchBladeType2-Mgmt is resolved by mcompile checking HP-SWITCH-PL.MIB. agSlotNumber
is resolved from BLADETYPE2-SWITCH.MIB and ipCurCfgGwIndex is resolved from
BLADETYPE2-NETWORK.MIB
.
To illustrate further how imports are resolved — the following procedure is how mcompile would
attempt to resolve the import for hpSwitchBladeType2-Mgmt:
Procedure 34 How MIB imports are resolved
1. Search for a file named HP-SWITCH-PL-MIB.mib (module name, uppercase).
2. Search for a file named HP-SWITCH-PL.mib (module name without -MIB, uppercase).
3. Search for hp-switch-pl.mib (convert name to lowercase for case sensitivity in
Linux/HP-UX).
4. Search for hp-switch-pl.mib.mib (convert name to lowercase for case sensitivity in
Linux/HPUX).
5. Report an error indicating that the imported MIB could not be found.
A major consideration when importing MIBs is locating variables from other third-party MIBs. In
many cases, MIBs are named to match module names. However, in some circumstances it might
be necessary to rename MIB files to match the module names prior to compilation. For example,
some vendors might provide MIB files with different extensions such as .my. In this case, before
using mcompile, the mibfile.my file must be renamed to mibfile.mib.
mxmib
The mxmib tools registers MIBs into the Systems Insight Manager database by using their
corresponding CFG files. This tool has the capability to list all registered MIBs, to display a list of
traps contained in each individually registered MIB, and to unregister MIBs that you or the system
have previously registered.
IMPORTANT: While it is possible to unregister MIBs currently registered in the Systems Insight
Manager database, HP strongly advises you do not unregister any files that have been registered
by default. Doing so can impair Systems Insight Manager's ability to correctly process traps from
other HP systems on the network.
If you unregister a MIB from Systems Insight Manager, the corresponding received events in Systems
Insight Manager are automatically deleted.
mxmib expects to find all files located in the <BASE>\mibs directory. Usage for mxmib is as
follows:
mxmib -a <myfile.cfg>
mxmib -f <mylist.list>
mxmib -l
mxmib -t <myfile.mib>
mxmib -d <myfile.mib>
The switches work as follows:
•
-a registers a new CFG, <myfile.cfg>, or replaces the data of a previously registered MIB.
•
-f reads and processes a list of CFGs from a file, <mylist.list (one mibname per line)>, to
register with Systems Insight Manager. This file must reside in the <BASE>\mibs directory
140 Compiling and customizing MIBs