[Top] [All Lists]

Re: [nv-l] Trap SNMP V2

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Trap SNMP V2
From: James Shanks <jshanks@us.ibm.com>
Date: Tue, 10 Jan 2006 13:41:19 -0500
Delivery-date: Tue, 10 Jan 2006 18:41:58 +0000
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <OFE5525F97.31D5EEB3-ONC12570F2.0039B335-C12570F2.003AC48A@fr.ibm.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
 Hello Maxine,

>From your talk about rulesets, I'm assuming you have a UNIX implementation.
And in that case, the code in trapd on UNIX has always received and
translated SNMPv2 traps into SNMPv1, and then handled them just like any
other SNMPv1 trap.   So there is no API for you to have to deal with in the
sense that there is no user configuration required for this to happen. It
happens automatically.

But this translation from SNMPv2 to SNMPv1 s a syntactic one, not a
semantic one.  A linkUp  trap in SNMPv1 has different contents than its
SNMPv2 counterpart, so the two are going to look different and have
different OIDs.  So there is going to have to be a separate entry for each
of them in trapd.conf and in the ruleset you use to send them to an event
window or to TEC.

Now from everything you've said, it certainly sounds as though you have
everything configured correctly for trapd.conf and the ruleset.  So I don't
know what else to do but give you diagnostic advice.  The only reason I can
think of  why a trap would not be forwarded to TEC from nvserverd would be
      (a) it were not selected by the ruleset which does the forwarding, or
      (b) it has  LOGONLY status in trapd.conf

The only way to diagnose (a) would be to turn on the nvcorrd trace with
"nvcdebug -d all" and look in the nvcorrd.alog and blog when the trap is
processed. The only way to diagnose (b) would be see what happens after (a)
is determined to be correct, since I don't think there are any other trace
points in nvserverd to show which traps are being suppressed by LOGONLY

If this doesn't help, then I suggest you contact IBM Support.

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

             Maxime TRANNOY                                                
             com>                                                       To 
             Sent by:                  nv-l@lists.us.ibm.com               
             owner-nv-l@lists.                                          cc 
                                       [nv-l] Trap SNMP V2                 
             01/10/2006 05:41                                              
             Please respond to                                             


Tivoli Netview 7.1.4 FP03 AIX 5.2

I  have cisco devices that sends me SNMP V2c traps.But from this device I
receive only V1 traps on my netview so i started to look at documentation
and I found that there is an API which transform V2 traps into V1 format in
order that Netview can handle it.
The problem is that specific V2 traps like coldstart warmstart linkUp and
Linkdown stay in the V2 Format with the EID

I add the description of this trap in the trapd.conf (as I do for a normal
V1 traps) and  add them in my rulsets in order to forward them to the TEC.
What I have seen is that in the trapd.log  the traps are correctly
translated the way I want but there are not forwarded to the TEC.
I test with a Dynamic workspace with my rulestes and saw that they pass my
filter and are well translated but are not send to TEC.
I verify in the nvserved.log ( with the tracevent to YES in tecint.conf)
and I don't see my V2 generic traps.

Why the generic traps are not transformed by the API into the V1 format?
Why my V2 generic traps goes through my filter but are not forwarded to

Kind Regards/Cordialement/S pozdravem.

IGS - Network Delivery Support Center
Tel : +33 (0) 492 114 767

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web