Re: [nv-l] Trap SNMP V2

[Mike Pearson <pearsom@us.ibm.com>]

Hi Maxime:
        Try
this.  edit /usr/OV/conf/tecint.conf
change the following line:
UseStateCorrelation=YES
to
UseStateCorrelation=NO
Or just comment it out.
This may work.  We have found at
times that this causes problems with events heading to TEC.


Regards, 
Michael Pearson

Tivoli NetView for UNIX and NT Support
Building 660, Office  CC105B;
HWY. 54 & 600 PARK OFFICES DR
Research Triangle Park, N.C. 27709
(919) 254-2270
pearsom@us.ibm.com
******************************************************************

******************************************************************
Need help with Tivoli Software Products? 
Ask Tivoli! 
http://www.tivoli.com/asktivoli

Maxime TRANNOY <MTRANNOY@fr.ibm.com>
Sent by: owner-nv-l@lists.us.ibm.com

01/11/2006 10:06 AM

Please respond to
nv-l@lists.us.ibm.com

To	nv-l@lists.us.ibm.com
cc
Subject	Re: [nv-l] Trap SNMP V2

Hello James,

I look at my trapd.conf and my event are status event.

I look at nvccord.log and I saw :


10/01 16:06:33       CorrDnodes.C[1111] : Forward::resolve()
queueing event
for forwaring:Event(CID(1184775),
Attr(EnterpriseID='(char,1.3.6.1.6.3.1.1.5.3)') Attr(Generic='(ulong,2)')
Attr(Specific='0') Attr(Origin='(ulong,xxxxxxxx)')
Attr(sysUpTime='(ulong,3544505043)') Attr(Community='(char,xxxxxxx)')
Attr(1='(char,6)') Attr(2='(char,GigabitEthernet3/3)') Attr(3='(char,6)')
Attr(4='(char,down)') Attr(Category='(ulong,3)') Attr(Source='(char,A)')
Attr(Severity='(ulong,4)'))


10/01 16:06:33       CorrDnodes.C[391] :   Forward
notification to
appl(18288, /usr/OV/conf/rulesets/pilotage_trap_and_syslog.rs, Active)
CID(1184775) SEV(99) STATUS(99)
2006/10/01 16:06:33       CorrDnodes.C[419] :   forwarding
EventInst:
                    
                     
  Event CID(1184775) 16:06:33

Attr(EnterpriseID='(char,1.3.6.1.6.3.1.1.5.3)')
                    
                     
       Attr(Generic='(ulong,2)')
                    
                     
       Attr(Specific='0')

Attr(Origin='(ulong,xxxxxxxx)')

Attr(sysUpTime='(ulong,3544505043)')

Attr(Community='(char,xxxxxxx)')
                    
                     
       Attr(1='(char,6)')

Attr(2='(char,GigabitEthernet3/3)')
                    
                     
       Attr(3='(char,6)')
                    
                     
       Attr(4='(char,down)')

Attr(Category='(ulong,3)')
                    
                     
       Attr(Source='(char,A)')

Attr(Severity='(ulong,4)')
2006/10/01 16:06:33       CorrDnodes.C[524] :   Forwarding
buffer.
cid=1184775 length=139 buffer=0x30328878
2006/10/01 16:06:33       CorrDnodes.C[526] :    
      severity=99
status=99 causingCID=0 causedCID=0 primeTime=0
2006/10/01 16:06:33       CorrDnodes.C[277] :   ===>
Completed actions for
/usr/OV/conf/rulesets/pilotage_trap_and_syslog.rs forwards=1 overrides=0
resolves=0

So it hink htey should be forwarded.

In the event desk they are forwarded because I see the event in my dynamic
workspace. But they are not in nvserverd.log neither on TEC.






Kind Regards/Cordialement/S pozdravem.

Maxime TRANNOY
IGS - Network Delivery Support Center
Tel : +33 (0) 492 114 767
mailto:mtrannoy@fr.ibm.com



                    
                     
                     
          
             James Shanks      
                     
                     
             <jshanks@us.ibm.c  
                     
                    
             om>      
                     
                     
     To 
             Sent by:      
           nv-l@lists.us.ibm.com    
          
             owner-nv-l@lists.    
                     
               cc 
             us.ibm.com      
                     
                     
 
                    
                     
                     
  Subject 
                    
                  Re: [nv-l]
Trap SNMP V2             
             10-01-2006 19:41    
                     
                   
                    
                     
                     
          
                    
                     
                     
          
             Please respond to    
                     
                  
                   nv-l  
                     
                     
     
                    
                     
                     
          
                    
                     
                     
          




 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
if
      (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
status.

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
             <MTRANNOY@fr.ibm.
             com>      
                     
                     
    To
             Sent by:      
           nv-l@lists.us.ibm.com
             owner-nv-l@lists.    
                     
               cc
             us.ibm.com
                    
                     
                     
  Subject
                    
                  [nv-l] Trap
SNMP V2
             01/10/2006 05:41
             AM


             Please respond to
             nv-l@lists.us.ibm
                   .com






Hi

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 1.3.6.1.6.3.1.1.5.

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
TEC.





Kind Regards/Cordialement/S pozdravem.

Maxime TRANNOY
IGS - Network Delivery Support Center
Tel : +33 (0) 492 114 767
mailto:mtrannoy@fr.ibm.com