[prev in list] [next in list] [prev in thread] [next in thread]
List: net-snmp-users
Subject: Re: Trap event not passing snmptrapd
From: Bill Fenner <fenner () gmail ! com>
Date: 2017-10-09 19:04:35
Message-ID: CAF4SogaLGxowrusG6kqkcQ07t7zhXiPnDVb0X0AVMpn3979deA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Per https://tools.ietf.org/html/rfc3416#section-4.2.6, "The first two
variable bindings ... are sysUpTime.0 and snmpTrapOID.0". Your trap
contains sysUpTime.0 and snmpTrapEnterprise (with no instance ID, making it
invalid anyway). So, snmptrapd is probably just discarding it because it
is malformed.
Bill
On Fri, Oct 6, 2017 at 2:23 AM, marian szczepkowski <marian@jozep.com.au>
wrote:
> We have a small device that send a trap on events I have configured
> anmptrapd to pass traps generated manually but snmptrapd doesn't pass
> the events generated by our devices the event doesn't show up when run
> with -d so I'm guessing it's some thing fundamental. The following is
> the wireshark trace of our snmp event and I'm hoping someone can shed
> light on what we are doing wrong.
>
> Raw
>
> 0000 00 24 1d 89 13 1d 00 18 1f 02 3a 9e 08 00 45 00 .$........:...E.
> 0010 00 64 00 46 00 00 80 11 26 39 0a 00 00 0a 0a 00 .d.F....&9......
> 0020 00 01 00 a2 00 a2 00 50 80 b6 30 46 02 01 01 04 .......P..0F....
> 0030 06 70 75 62 6c 69 63 a7 39 02 04 00 00 00 03 02 .public.9.......
> 0040 01 00 02 01 00 30 2b 30 10 06 08 2b 06 01 02 01 .....0+0...+....
> 0050 01 03 00 43 04 00 00 0d 0d 30 17 06 09 2b 06 01 ...C.....0...+..
> 0060 06 03 01 01 04 03 04 0a 48 61 6e 64 73 65 74 20 ........Handset
> 0070 75 70 up
>
>
>
> Decoded, the interesting bits.
>
> Frame 11: 114 bytes on wire (912 bits), 114 bytes captured (912 bits)
> Ethernet II, Src: Palmmicr_02:3a:9e (00:18:1f:02:3a:9e), Dst:
> Giga-Byt_89:13:1d (00:24:1d:89:13:1d)
> Internet Protocol Version 4, Src: 10.0.0.10, Dst: 10.0.0.1
> User Datagram Protocol, Src Port: snmptrap (162), Dst Port: snmptrap (162)
> Source Port: snmptrap (162)
> Destination Port: snmptrap (162)
> Length: 80
> Checksum: 0x80b6 [unverified]
> [Checksum Status: Unverified]
> [Stream index: 3]
> Simple Network Management Protocol
> version: v2c (1)
> community: public
> data: snmpV2-trap (7)
> snmpV2-trap
> request-id: 3
> error-status: noError (0)
> error-index: 0
> variable-bindings: 2 items
> 1.3.6.1.2.1.1.3.0: 3341
> Object Name: 1.3.6.1.2.1.1.3.0 (iso.3.6.1.2.1.1.3.0)
> Value (Timeticks): 3341
> 1.3.6.1.6.3.1.1.4.3: 48616e64736574207570
> Object Name: 1.3.6.1.6.3.1.1.4.3
> (iso.3.6.1.6.3.1.1.4.3)
> Value (OctetString): 48616e64736574207570
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Net-snmp-users mailing list
> Net-snmp-users@lists.sourceforge.net
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>
>
[Attachment #5 (text/html)]
<div dir="ltr">Per <a \
href="https://tools.ietf.org/html/rfc3416#section-4.2.6">https://tools.ietf.org/html/rfc3416#section-4.2.6</a>, \
"The first two variable bindings ... are sysUpTime.0 and snmpTrapOID.0". \
Your trap contains sysUpTime.0 and snmpTrapEnterprise (with no instance ID, making \
it invalid anyway). So, snmptrapd is probably just discarding it because it is \
malformed.<div><br></div><div> Bill</div><div><br></div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 6, 2017 at 2:23 AM, \
marian szczepkowski <span dir="ltr"><<a href="mailto:marian@jozep.com.au" \
target="_blank">marian@jozep.com.au</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">We have a small device that send a trap on events I have \
configured<br> anmptrapd to pass traps generated manually but snmptrapd doesn't \
pass<br> the events generated by our devices the event doesn't show up when \
run<br> with -d so I'm guessing it's some thing fundamental. The following \
is<br> the wireshark trace of our snmp event and I'm hoping someone can shed<br>
light on what we are doing wrong.<br>
<br>
Raw<br>
<br>
0000 00 24 1d 89 13 1d 00 18 1f 02 3a 9e 08 00 45 00 .$........:...E.<br>
0010 00 64 00 46 00 00 80 11 26 39 0a 00 00 0a 0a 00 .d.F....&9......<br>
0020 00 01 00 a2 00 a2 00 50 80 b6 30 46 02 01 01 04 .......P..0F....<br>
0030 06 70 75 62 6c 69 63 a7 39 02 04 00 00 00 03 02 .public.9.......<br>
0040 01 00 02 01 00 30 2b 30 10 06 08 2b 06 01 02 01 .....0+0...+....<br>
0050 01 03 00 43 04 00 00 0d 0d 30 17 06 09 2b 06 01 ...C.....0...+..<br>
0060 06 03 01 01 04 03 04 0a 48 61 6e 64 73 65 74 20 ........Handset<br>
0070 75 70 <wbr> \
up<br> <br>
<br>
<br>
Decoded, the interesting bits.<br>
<br>
Frame 11: 114 bytes on wire (912 bits), 114 bytes captured (912 bits)<br>
Ethernet II, Src: Palmmicr_02:3a:9e (00:18:1f:02:3a:9e), Dst:<br>
Giga-Byt_89:13:1d (00:24:1d:89:13:1d)<br>
Internet Protocol Version 4, Src: 10.0.0.10, Dst: 10.0.0.1<br>
User Datagram Protocol, Src Port: snmptrap (162), Dst Port: snmptrap (162)<br>
Source Port: snmptrap (162)<br>
Destination Port: snmptrap (162)<br>
Length: 80<br>
Checksum: 0x80b6 [unverified]<br>
[Checksum Status: Unverified]<br>
[Stream index: 3]<br>
Simple Network Management Protocol<br>
version: v2c (1)<br>
community: public<br>
data: snmpV2-trap (7)<br>
snmpV2-trap<br>
request-id: 3<br>
error-status: noError (0)<br>
error-index: 0<br>
variable-bindings: 2 items<br>
1.3.6.1.2.1.1.3.0: 3341<br>
Object Name: 1.3.6.1.2.1.1.3.0 \
(iso.3.6.1.2.1.1.3.0)<br> Value (Timeticks): 3341<br>
1.3.6.1.6.3.1.1.4.3: 48616e64736574207570<br>
Object Name: 1.3.6.1.6.3.1.1.4.3 \
(iso.3.6.1.6.3.1.1.4.3)<br>
Value (OctetString): 48616e64736574207570<br>
<br>
<br>
<br>------------------------------<wbr>------------------------------<wbr>------------------<br>
Check out the vibrant tech community on one of the world's most<br>
engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" \
rel="noreferrer" target="_blank">http://sdm.link/slashdot</a><br>______________________________<wbr>_________________<br>
Net-snmp-users mailing list<br>
<a href="mailto:Net-snmp-users@lists.sourceforge.net">Net-snmp-users@lists.<wbr>sourceforge.net</a><br>
Please see the following page to unsubscribe or change other options:<br>
<a href="https://lists.sourceforge.net/lists/listinfo/net-snmp-users" \
rel="noreferrer" target="_blank">https://lists.sourceforge.net/<wbr>lists/listinfo/net-snmp-users</a><br>
<br></blockquote></div><br></div>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic