This is a common problem for new NetView users, Larry.
Loading the MIBs does nothing for traps. Loading MIBs allows the MIB Browsers
and their cousins to function correctly.
The data you appended is enough for a manual customization of
the trapd.conf file. You have to either manually customize traps using
the trap tool (xnmtrap is the command line entry to open the interface) or you
need to see if the trap you are interested in is defined in the MIBs.
(Directly editing trapd.conf is not recommended.) Usually the definition is at
the end of the MIB file. Then you run MIB2TRAP, make sure the Enterprise
ID exists in the output file, then execute the output file (it contains
Failing to have all the dependencies in place is the biggest
problem. It usually results in the Enterprise ID not being present in the
ADDTRAP commands which are created. You can add it manually if it's not
Tivoli NetView support for
owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]
On Behalf Of Larry Fagan
Sent: Friday, February 18,
2005 4:30 PM
To: nv-l AT lists.us.ibm DOT com
Subject: [nv-l] trap format not right!
I'm getting these below said
traps in Netview from one
of our Nokia devices. I have
the MIB's loaded and OID
is in the message but nothing
else. no hostname, no
origin and no enterprise nothing
except link up or
down. or is possible that i have
loaded MIB's wrong.
How do i know if MIbs loaded are
not right. I have
loaded two mibs for this device.
First with absolute
no errors, and second MIb with
:enterprise ID not found". SO i used the
-i and OID
from previous addtrap and loaded using
this is one which gives wierd message
format. I used
mib2trap to load mibs.
" TEC_ITS_BASE - Agent Interface Down (linkDown Trap)
(Integer): 5 "
Any ideas.. Many Thanks,
The all-new My Yahoo! - What will yours
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.