[SNMP4J] Problem listening to SNMP v3 traps

Thu Feb 28 21:33:10 CET 2008

Frank,

I couldn't get the DEBUG thing to work, even after I set the LogLevel to 
DEBUG with:

LogFactory.getLogFactory().getRootLogger().setLogLevel(LogLevel.DEBUG);

But I did traced where the message is received and printed it out to the 
console. The message in HEX is:

Received message from /10.10.200.4/161 with length 636: 
30:82:02:78:02:01:03:30:0d:02:01:12:02:02:05:c0:04:01:00:02:01:03:04:20:30:1e:04:09:80:00:04:50:01:0a:0a:c8:04:02:01:09:02:02:13:8d:04:06:55:53:45:52:49:44:04:00:04:00:30:82:02:40:04:00:04:06:55:53:45:52:49:44:a7:82:02:32:02:02:00:cd:02:01:00:02:01:00:30:82:02:24:30:0f:06:08:2b:06:01:02:01:01:03:00:43:03:07:a3:63:30:1a:06:0a:2b:06:01:06:03:01:01:04:01:00:06:0c:2b:06:01:04:01:02:06:81:1e:03:00:16:30:3b:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:01:04:2a:44:61:74:65:28:6d:2f:64:2f:79:29:3d:30:37:2f:31:37:2f:30:31:2c:20:54:69:6d:65:28:68:3a:6d:3a:73:29:3d:31:35:3a:32:31:3a:30:32:30:37:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:02:04:26:42:6c:61:64:65:43:65:6e:74:65:72:20:41:64:76:61:6e:63:65:64:20:4d:61:6e:61:67:65:6d:65:6e:74:20:4d:6f:64:75:6c:65:30:20:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:03:04:0f:53:4e:23:30:4a:31:55:39:45:35:38:39:31:30:52:30:31:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:04:04:20:32:36:41:46:38:46:30:31:32:46:44:38:31:31:44:37:38:32:30:32:41:31:46:39:42:41!
 :31:36:34:36:44:36:30:18:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:05:04:07:32:33:41:30:31:30:33:30:12:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:06:02:01:16:30:12:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:07:02:01:04:30:2f:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:08:04:1e:41:70:70:6c:69:63:61:74:69:6f:6e:20:70:6f:73:74:65:64:20:61:6c:65:72:74:20:74:6f:20:4d:4d:30:26:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:09:04:15:4e:6f:20:43:6f:6e:74:61:63:74:20:43:6f:6e:66:69:67:75:72:65:64:30:27:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:0a:04:16:4e:6f:20:4c:6f:63:61:74:69:6f:6e:20:43:6f:6e:66:69:67:75:72:65:64:30:11:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:0b:04:00:30:11:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:0c:04:00:30:11:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:0d:04:00:30:12:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:0e:42:01:14:30:19:06:0d:2b:06:01:04:01:02:06:81:1e:03:01:01:0f:04:08:53:45:52:56:50:52:4f:43

I couldn't find where you decode this message in you API. Can you tell me 
what this message means or how to decode it? Thanks.

Regards,

Pedro Franceschi
Automation Developer COOP
FVT Automation Team

Frank Fock <fock at agentpp.com> 
02/28/2008 01:49 PM

To
Pedro Franceschi/Raleigh/IBM at IBMUS
cc
snmp4j at agentpp.org
Subject
Re: [SNMP4J] Problem listening to SNMP v3 traps

Hi Pedro,

The Java logger probably wrote the output to stderr.
You then need to redirect stderr to stdout to see it
on the console.

The warning says, that a PDU type has been received
that either does not exists or is not compatible with
the SNMP protocol version used or the operation mode
of the application.

Best regards,
Frank

Pedro Franceschi schrieb:
> Hi,
>
> I set the log level to DEBUG as you said by using the built in option u 
> have (-d DEBUG). I am not seeing any difference in the log output at 
all. 
> Is there anything else I should add for the output to show up? 
>
> The WARNING: 1.3.6.1.6.3.11.2.1.3.0 = 1  message I'm receiving, what 
does 
> it mean? Obviously, that number corresponds to an OID from the MIB file 
> and it says:
>
> "The total number of packets received by the SNMP engine which were 
> DROPPED because the PDU contained in the packet could not be passed to 
an 
> application responsible for handling the pduType..."
>
> Hope it helps. Thanks.
>
> Regards,
>
> Pedro Franceschi
> Automation Developer COOP
> FVT Automation Team
>
>
>
> Frank Fock <fock at agentpp.com> 
> 02/27/2008 06:27 PM
>
> To
> Pedro Franceschi/Raleigh/IBM at IBMUS
> cc
> snmp4j at agentpp.org
> Subject
> Re: [SNMP4J] Problem listening to SNMP v3 traps
>
>
>
>
>
>
> If you set the log level to debug on the console tool (SnmpRequest)
> then you should see the incoming message's bytes as hex string.
> You may post that message here or you may analyse it yourself
> with a sniffer or MIB Explorer Pro. I am pretty sure that SNMP4J
> is capable of receiving SNMPv3 notifications, so I expect a simple
> solution for the problem.
>
> Best regards,
> Frank
>
> Pedro Franceschi schrieb:
> 
>> The agent I'm using to send  traps is an IBM server. It does everything 

>> automatically. It generates the SNMPv1 traps, as well as the SNMPv3 
>> 
> ones. 
> 
>> I am just generating a Test Alert from the server's own web interface 
to 
>> 
>
> 
>> make sure the manager receives it. What is odd is that I could receive 
>> 
> the 
> 
>> v3 traps with another program, which leaves the problem to SNMP4J. 
Also, 
>> 
>
> 
>> and what makes it more interesting, is that I could actually 
>> 
> send/receive 
> 
>> Get /SET commands with v3 using SNMP4J. Btw, the last output I sent you 

>> was using the SnmpRequest class, with NOTHING changed. This is why I 
>> 
> have 
> 
>> no idea what is going on since I ended using exactly the same code you 
>> provided. Any ideas on what could be wrong? Is there any way those 
>> 
> Unknown 
> 
>> PDUs can be accessed?
>>
>> I appreciate your fast response on my first post. Thanks.
>>
>> Regards,
>>
>> Pedro Franceschi
>> Automation Developer COOP
>> FVT Automation Team
>> _______________________________________________
>> SNMP4J mailing list
>> SNMP4J at agentpp.org
>> http://lists.agentpp.org/mailman/listinfo/snmp4j
>>
>> 
>
>
>
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j
> 