First, is this NetView for Windows or NetView for UNIX? Big difference, if
the trap is in SNMPv2 format or not.
On Windows you will need to have 7.1.4 FP03 to be able to receive and
display SNMPv2 traps, and even then you will have to configure trapd
correctly for that to happen. The procedure is outlined in the FP03
Release Notes. On UNIX trapd has always supported SNMPv2 traps.
If that's not the issue, and you see nothing in the trapd.log, most likely
the trap is not getting to NetView. You can set trapd to run with the -x
option (hexdump all packets) and then start the trace. On UNIX you do
that dynamically from the command line -- "trapd -T " will toggle the trace
on and off again. Everything that come into port 162/UDP will be dumped
and displayed. On Windows you have to manually configure the ovsuf file
for trapd to say both -x and -tC:\usr\ov\log\trapd.trace to get the trace
going when you start the daemon. But it too will dump everything that
comes in or give you an error message trying. As I said before , however,
most likely the issue is that the trap never arrived in the first place.
To prove that you'll probably need a network trace of some kind, iptrace on
AIX, snoop on Solaris, or a third-party product like Ethereal on Windows,
to show you what traffic has come to port 162.
Remember that everything you did with regard to the trap on the NetView
side was only to format it correctly, IF it gets there. There is nothing
you can do on the NetView side to ensure that. If you don't see it in your
traces, then I'd start by examining whatever log is available on the
sending device to verify ti was sent and sent to the correct IP address and
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
05/18/05 10:39 PM
Please respond to
[nv-l] Not receiving traps from OEM
Our DBAs are trying to send traps from the OEM product to NetView.
I've loaded the MIBs with the Web Console MIB Loader, run mib2trap and
executed the script. All appeared to work well. I've also verified our
community name in the product configuration and snmpd.conf.
Needless to say, no traps are arriving. Using the Web Console MIB
Browser, I can query the base MIB. However, the enterprise.oracle section
returns "Not Supported". I'd like to dig a little deeper into the "Not
Supported" response and also see if the traps are actually being sent. I
don't see anything in trapd.log to indicate that they are. Have I forgotten
something? Can someone suggest the next step in sorting this out?
PJM Interconnection, llc