Re: [nv-l] nvsnmptrap not working

[James Shanks <jshanks@us.ibm.com>]

Only "Trace Starting"?  Are you not getting any other traps?
nvsnmptrap is probably not broken if you had it working before.  But you might not have a good interface to the outside world after your reboot.  Or else the MS Trap Service might not be running
Internal traps do not go out over the network.  They travel internally on a TCP socket and never leave the box.  But nvsnmptrap sends them out over the network to port 162 on your NetView box.  Unless you have changed things, you have to have the Microsoft Trap Service running to receive them.  On most Windows boxes, he owns port 162/udp.  trapd gets them from him. Take a look in the nv.log and see if you can find any trapd error messages about his connection to the Trap Service.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Karl Prinelle" <Karl.Prinelle@elyzium.co.uk> Sent by: owner-nv-l@lists.us.ibm.com 02/03/2004 11:24 AM Please respond to nv-l

To:        <nv-l@lists.tivoli.com>         cc:                 Subject:        [nv-l] nvsnmptrap not working

Hi list,
 
Bit of an odd one....  I'm testing a problem on Win2k and NV 7.1.4 - it's just some updates to the .cds file.  
 
I've already made my changes and they worked ok - nvsnmptrap sends trap to the NV events list & they go on to TEC - a little script I have contains a test of each trap & running that shows they all went through ok.  No problem - left it for a day & a reboot later & now traps don't work!
 
To qualify that - my nvsnmptrap calls run, have no output but nothing appears in the Netview events list or trapd.log.  I've switched tracing on (trapd -t c:\temp\trapd-trace.log), the trace file says nothing too - apart from that it's starting.  
 
Internal traps are coming through, no problem!  The odd thing is that I can still see the traps I sent previously in the events list so I know I'm not going completely mad.  I've checked that the traps are all defined as Status Events & not Log only, but either way they should appear in the trapd.log/trace files???
 
Below is the nvsnmptrap call I'm using.  
 
nvsnmptrap 192.168.1.51 1.3.6.1.4.1.3764.3 10.10.11.51 6 2 1  .1.3.6.1.4.1.3764.3.5 OctetString "Test string" .1.3.6.1.4.1.3764.3.16.3.1.19 Integer 9999
 
As a possibly related aside, I changed the nvsnmptrap call to be snmptrap and ran it on my Linux machine & it worked fine - well, I got unknown formatted trap because I didn't load the trap definitions, but trapd.log on linux shows that it was my correct trap coming in...
 
Any pointers appreciated - have I pressed some magic "switch off my traps" button ?
 
Ta in advance
 
K
 
 
 
---------------------------------------------------------------------------
Karl Prinelle
Consultant
Elyzium Ltd
Mobile: +44 (0)7813 189198
 
E-mail: karl.prinelle@elyzium.co.uk
 
Slough Office, Church Street, Slough, SL1 1PJ. Tel: +44 1753 515000, Fax:+44 1753 515017
Head Office, 12 Queensbrook, Bolton, BL1 4AY. Tel: +44 1204 528628, Fax: +44 1204 534678
 
For further information, please visit our website at www.elyzium.co.uk
 
---------------------------------------------------------------------------
Elyzium Disclaimer:
This email transmission is confidential and intended solely for the person 
or organisation to whom it is addressed. If you are not the intended 
recipient, you must not copy, distribute or disseminate the information, or 
take any action in reliance of it. Any views expressed in this message are 
those of the individual sender, except where the sender specifically states 
them to be the views of any organisation or employer. 
If you have received this message in error, do not open any attachment 
but please notify the sender (above) deleting this message from your system. 
Please rely on your own virus check no responsibility is taken by the
 sender for any damage arising out of any bug or virus infection.
---------------------------------------------------------------------------