Larry, you need not be sorry for asking basic questions.
But the answer is that loading MIBs has almost nothing to do with the way
traps will be formatted.
In order to get traps formatted you must have a definition for them in
trapd.conf. You can add that manually using the GUI, xnmtrap, or by the
addtrap command. To get a MIB to produce a trap definition you run
/usr/OV/bin/mib2trap on the MIB file. Loading it with either xnmloadmib or
xnmloadmib2 will not do that by itself. In fact, if all you want to do is
format the trap, and you never want to query the agent using either MIB
browser, then you don't have to load the MIB at all. The only caveat
about that is that the MIB must be loadable by the SNMPv1/v2 loader,
xnmloadmib2. That is, if xnmloadmib2 won't load it, because of an internal
syntax problem, then mib2trap, which uses the same libraries, will be
unable to build an addtrap script from it.
There are other issues with using addtrap that I don't want to go into
here, under this thread, but you can check the archives for them or post
your questions here when you run into them, but that's how you turn a MIB's
trap definition into an entry in trapd.conf.
So have we been going down the wrong path all this time trying to load
MIBs?
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
|