RE: IpAddress types being rewritten as signed integer
"Larry Low" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <016901c861f0$cbbfd050$633f70f0$@com> |
Here is the capture from an event. As you can see the issue. IpAddress is by definition formatted as an unsigned integer but snmptrapd is detecting it as a signed integer. dumph_recv: SNMP version dumpx_recv: 02 01 01 dumpv_recv: Integer: 1 (0x01) dumph_recv: community string dumpx_recv: 04 05 74 72 61 70 73 dumpv_recv: String: traps dumph_recv: PDU dumpv_recv: Command INFORM dumph_recv: request_id dumpx_recv: 02 02 0C 8E dumpv_recv: Integer: 3214 (0xC8E) dumph_recv: error status dumpx_recv: 02 01 00 dumpv_recv: Integer: 0 (0x00) dumph_recv: error index dumpx_recv: 02 01 00 dumpv_recv: Integer: 0 (0x00) dumph_recv: VarBindList dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 08 2B 06 01 02 01 01 03 00 dumpv_recv: ObjID: DISMAN-EVENT-MIB::sysUpTimeInstance dumph_recv: Value dumpx_recv: 43 04 02 D4 ED 99 dumpv_recv: UInteger: 47508889 (0x2D4ED99) dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 0A 2B 06 01 06 03 01 01 04 01 00 dumpv_recv: ObjID: SNMPv2-MIB::snmpTrapOID.0 dumph_recv: Value dumpx_recv: 06 09 2B 06 01 02 01 0E 10 02 02 dumpv_recv: ObjID: OSPF-TRAP-MIB::ospfNbrStateChange dumpx_recv: 06 09 2B 06 01 02 01 0E 10 02 02 dumpv_recv: ObjID: OSPF-TRAP-MIB::ospfNbrStateChange dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 08 2B 06 01 02 01 0E 01 01 dumpv_recv: ObjID: OSPF-MIB::ospfRouterId dumph_recv: Value dumpx_recv: 02 04 D8 1B D4 26 dumpv_recv: Integer: -669264858 (0xD81BD426) dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 09 2B 06 01 02 01 0E 0A 01 01 dumpv_recv: ObjID: OSPF-MIB::ospfNbrIpAddr dumph_recv: Value dumpx_recv: 02 04 D8 1B D4 25 dumpv_recv: Integer: -669264859 (0xD81BD425) dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 09 2B 06 01 02 01 0E 0A 01 02 dumpv_recv: ObjID: OSPF-MIB::ospfNbrAddressLessIndex dumph_recv: Value dumpx_recv: 02 01 00 dumpv_recv: Integer: 0 (0x00) dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 09 2B 06 01 02 01 0E 0A 01 03 dumpv_recv: ObjID: OSPF-MIB::ospfNbrRtrId dumph_recv: Value dumpx_recv: 02 04 D8 1B DA C5 dumpv_recv: Integer: -669263163 (0xD81BDAC5) dumph_recv: VarBind dumph_recv: Name dumpx_recv: 06 09 2B 06 01 02 01 0E 0A 01 06 dumpv_recv: ObjID: OSPF-MIB::ospfNbrState dumph_recv: Value dumpx_recv: 02 01 01 dumpv_recv: Integer: 1 (0x01) dumpx_recv: 02 01 01 dumpv_recv: Integer: 1 (0x01) 2008-01-18 10:17:41 216.27.212.18 [UDP: [216.27.212.18]:52826]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (47508889) 5 days, 11:58:08.89 SNMPv2-MIB::snmpTrapOID.0 = OID: OSPF-TRAP-MIB::ospfNbrStateChange OSPF-MIB::ospfRouterId = Wrong Type (should be IpAddress): INTEGER: -669264858 OSPF-MIB::ospfNbrIpAddr = Wrong Type (should be IpAddress): INTEGER: -669264859 OSPF-MIB::ospfNbrAddressLessIndex = INTEGER: 0 OSPF-MIB::ospfNbrRtrId = Wrong Type (should be IpAddress): INTEGER: -669263163 OSPF-MIB::ospfNbrState = INTEGER: down(1) ---- Larry Low 4150 N Drinkwater Blvd., 5th Floor Scottsdale, AZ 85251 Office: 480.385.7045 E-mail: [email protected]' Telesphere Networks, Inc > -----Original Message----- > From: [email protected] [mailto:net-snmp- > [email protected]] On Behalf Of Dave Shield > Sent: Wednesday, January 16, 2008 3:27 PM > To: Larry Low > Cc: [email protected] > Subject: Re: IpAddress types being rewritten as signed integer > > On 15/01/2008, Larry Low <[email protected]> wrote: > > Anyone having problems where snmptrapd is receiving an trap with an > > IpAddress field, rewriting it to a signed integer, and then reporting > it as > > "should be IpAddress"? I get other traps without this problem on the > same > > MIB (OSPF-TRAP-MIB) so I am leaning towards this being a problem with > the > > format of the trap. > > > > I am running 5.4.1. > > > > I'll try and dig deeper into this. > > Try running snmptrapd with the option -Ddump, > which will print a formatted display of the incoming PDU > before snmptrapd tries to process it. > That should help determine whether it's a problem > with the code generating this particular trap, or the code > that processes it. > > Dave > > ----------------------------------------------------------------------- > -- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Net-snmp-users mailing list > [email protected] > Please see the following page to unsubscribe or change other options: > https://lists.sourceforge.net/lists/listinfo/net-snmp-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users