Todd -
I am sorry Todd but you are just wrong about this. I work on mib2trap so I
know, and I have fixed several bugs in it between 6.0 and 6.0.2. I suspect
your comments are driven by the fact that you may not have been working
with a current version.
First, mib2trap is not a script but a program, which has to parse the MIB
in order to construct all those elements, like the enterprise id, which are
needed to define a trap to trapd.conf. It uses the same library are
xnmloadmib2 (UNIX) or loadmibv2 (NT) so it DOES understand the same SNMPV2
MIB constructs as the SNMPV2 loader, including NOTIFICATION-TYPE, which it
can use to generate an addtrap statement. It is NOT necessary to use only
SNMPV1 MIBs with mib2trap. This is true no matter whether you use the NT
version or the UNIX version.
James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Tivoli Software
IBM Software Group
Please note that my new id is jshanks@us.ibm.com
netview@toddh.
net (Todd H.) To: IBM NetView Discussion
<nv-l@tkg.com>
Sent by: cc:
owner-nv-l@tkg Subject: Re: [NV-L] snmp setup
(traps, mib
.com files, snmpv1/v2, mib2trap)
10/05/01 06:20
PM
Please respond
to IBM NetView
Discussion
Daniel Lehman <dlehman@hurricanetechgroup.com> writes:
> Hello All,
>
> I am having a little issue, i loaded the required mib in to Netview
> 6.02 on NT. I am able to use the MIB Browser and walk through the
> tree succesfully.
This confused me too when I was getting started. Loading MIB files in
Netview basically just feeds the MIB variable browser for pollable
element--it does nothing to define traps.
Traps are defined in Netview via the addtrap command (for which there
is a man page) which essentially loads the definitions into
/usr/OV/conf/trapd.conf (at least on UNIX it does).
mib2trap is (rather limited) script for generating some addtrap
commands from a set of MIB files. First, you will need a fairly
complete set of mib files that define things all the way up the OID
tree for mib2trap to make sense of things. In addition, mib2trap
doesn't seem to understand SMIv2 (aka SNMPv2 style files) so you will
need SMIv1 versions of all the MIB files if you even wish to try
mib2trap.
If you're unsure what type your MIB files are, SMIv2 files define
traps using a NOTIFICATION-TYPE keyword while SMIv1 files use the
keyword TRAP-TYPE. If you see NOTIFICATION-TYPE in your mib files, I
don't think mib2trap can help you. Note also, that if your devices
send snmpv2c traps, avoid using a NetView Mid-level Manager (MLM)--it
doesn't seem to forward snmpv2c traps. You'll have to send snmpv2c
traps directly to the NetView server.
All my comments refer to the UNIX version--I'm not sure how many
differences the NT version has in this regard.
--
Todd H.
http://www.toddh.net/
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|