Re: [pysnmp-users] Mixed version Trap duplicate message
Brought to you by:
elie
From: Ilya E. <il...@gl...> - 2015-10-12 19:41:46
|
Hi Laszlo, From the first glance the problem is related to misconfigured SNMP “tags”. When sending SNMPv1/2c traps, you may need to “tag” SNMP community information and destination address with the same tag to logically bind one to the other. When you are working with different destinations, that is not that important, but since you are sending different TRAPs to the same destination, that may mess things up. You can read the details in SNMP RFCs. So, please, see your slightly modified script attached to this message. -ilya > On 12 Oct 2015, at 13:37, László Tamás Zeke <las...@er...> wrote: > > Hi, > > I made a simple script using 4.3.0 to send v2 and v3 trap messages. My issue is that when I send mixed version messages (reusing the same SnmpEngine object) in succession, then 2 messages are sent for one call of sendNotification after the first. > > ctx.send_trapv3() > ctx.send_trapv2() > -> v3,v3,v2 > > and > > ctx.send_trapv2() > ctx.send_trapv3() > -> v2,v2,v3 > > but > > ctx.send_trapv2() > ctx.send_trapv2() > -> v2,v2 // OK > > ctx.send_trapv3() > ctx.send_trapv3() > -> v3,v3 // OK > > also, > > ctx.send_trapv3() > ctx.send_trapv2() > ctx.send_trapv3() > -> v3, v3, v2, v3, v2 > > Am I doing something wrong or is this a bug? I can send sample code but it is really simple calls of hlapi's sendNotification. > I'm using Python 2.7.3 on Ubuntu 12.04. > > Best regards, > Laszlo |