|
Okay....both James and Phillip helped tremendously....I really really
appreciate the time you guys are taking to help with this, and provide as much
input as you do. While you were both responding, I was able obtain a
"wftraps.asn" file that contains the trap definitions for these devices.
Upon running mib2trap against it, it was able to produce the script containing
the "addtrap" commands for each TRAP-TYPE. My only concern before running
the script to add those into Netview, is that in the command window, when
reading each of the TRAP-TYPE 's it produced a message stating that the
"Enterprise object id not found for trap ....". So from this, I made the
assumption that NetView wasn't aware of the Wellfleet enterprise id......so I
added it manually within the Trap Settings tool...... 1.3.6.1.4.1.18 ....
and then ran the mib2trap utility again....same results....it created the script
with the addtrap commands, but while doing so produced the message on the screen
"Enterprise object id not found for trap .... Is it possible the trapd needs to
be stopped and restarted after manually adding the Enterprise OID for wellfleet,
before using the mib2trap command.....or am I just way off here ?
Note: I had also loaded the wfcommon.mib (mib for almost all wellfleet
type devices) previously with the mib loader (V1), and I can "walk" that
enterprise tree.....but from what I am learning, that really doesn't have
anything to do with the trap definitions or trap
settings....true?
(1)Traps are
defined in a MIB either by TRAP-TYPE statements (SNMP V1) or NOTIFICATION-TYPE
(SNMP V2 and later) statements.
If
your MIB doesn't have any of these, then it doesn't define traps.
Running mib2trap on it will give you nothing.
(2) Vendors can send pretty much whatever they want so
long as it is formatted correctly. There is no standard detailing what
has to be in a trap.
A trapd can be
sent with the vendors' OID .1.3.6.1.4.1.18 or with a
standard OID such as MIB-II data, .1.3.6.1.2.1.2.2, which all SNMP
agents are required to support. The vendor gets to choose what he will
do.
When you right-click the event
in the browser on Windows and select "Event Details" it will popup a Window
and show you what all the components of the incoming trap were. The will
be logged the same way in trapd.log (if you have enabled that) when the trap
format is not found. You can use this information to define the trap
manually or to try to find the MIB which defines it so that you have a better
understanding of what the variables mean. mib2trap is just a convenience tool.
If you have the right MIB, it will create an addtrap script
which provide a default definition for that enterprise id and trap number, but
that's about all. Most people will want to modify that entry to make it
more meaningful anyway. If you don't have the right MIB and the meaning
of the data is obvious, it is probably easier just to add the trap with Trap
Settings and be done with it.
James Shanks
Level 3 Support for
Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software
Group
|
| Brian Kraftchick
<Brian.Kraftchick@odfl.com>
Sent by: owner-nv-l-digest@lists.us.ibm.com
10/23/2003 12:41 PM
Please respond to nv-l
|
To:
"NVList (E-mail)" <nv-l@lists.us.ibm.com>
cc:
Subject: [nv-l] mib2trap
utility
|
NV
7.1.2 on Win2K
General question with probably a simple answer on
trying to understand how to get traps defined to NetView: I have been
trying to run mib2trap against several provided and downloaded MIB's to get
the traps defined to NetView, however, I've only been successful in doing so
on only 1 or 2 attempts with many different MIB files. It seems from
this that most MIB's do NOT "carry" the trap definitions....is this more true
than not ? In particular I am trying to get the traps defined to
NetView for Bay Network Advanced Remote Node routers, so that I can get
NetView to properly understand the traps when those routers have an
interface(s) drop...and hence, update the status of those devices in the map,
and send a "meaningful" event over to TEC. A consultant configured those
ARN's to send a generic link up or link down trap to our NetView
server.....but NetView basically "takes them in" and puts! (as J. Shanks
explained) a default wrapper on it since it doesn't know what to do with them.
The devices' interfaces are of type Wellfleet....does this mean that the
traps that are coming in have OIDS of .1.3.6.1.4.1.18 (which is Wellfleet's
enterprise id), or are they simply .1.3.6.1.2.1.2.2........etc.....basic mgmt
type OID's? Well, I don't know....in checking the trapd.log file....the
information provided leads me to believe that the traps are coming in with the
.1.3.6.1.2.1.2.... OID's. What am I missing in understanding here ?
I feel like I am right on the verge of understanding exactly what is
going on and how to "massage" NetView into doing what I want.....but just seem
to be missing something.
As always, thanks for
everyone's help !!!!
Brian Kraftchick
Network Administrator
Old Dominion Freight
Line
Ph: (336)
822-5938
Fax: (336)
822-5149
E-mail: brian.kraftchick@odfl.com
Web Site: www.odfl.com
|