Hello,

We have setup the AdventNet SNMP V3 trap receiver using the TrapReceiver class (http://www.webnms.com/snmp/help/snmpapi/snmpv3/examples/applications/trapreceiver.java.txt ) .

java -cp TestCode.jar snmp.TrapReceiver -p 162 -u USERM2 -e abc -a SHA -w test1234 -s test1234 -pp DES

When we tried to send an SNMP v3 trap using one of our High end server, the trap is not being received,
and the AdventNet APIs are logging the following text: (when we set in debug mode).

Plain Text Engine ID: abc
Trap Receiver started at port == 162
Principal = USERM2
Auth Protocol = 22
Auth Pwd = test1234
Priv Protocol = 50
Priv Pwd = test1234

Packet from: 10.163.228.46:1111 MessageID: 735951054
Received Time: Thu Nov 01 12:20:57:706 MDT 2012
Length of SNMP DATA: 404
DATA:
30 82 01 90 02 01 03 30 11 02 04 2b dd b8 ce 02 03 00 ff e3
04 01 03 02 01 03 04 2c 30 2a 04 03 61 62 63 02 01 00 02 01
00 04 05 41 53 52 4d 32 04 0c fd 6c 04 35 2b 78 33 9d 3d 44
70 2e 04 08 00 00 00 36 a6 f5 37 16 04 82 01 48 67 44 1b e2
d3 a6 de 24 47 2e a4 38 bd cd 66 e3 14 32 bd 27 25 19 05 66
ef 7a 9c b3 52 64 84 4a 85 d8 34 8d d7 7d 3d db fd 97 76 53
41 f0 13 38 00 ab bf 54 4e b1 1f d5 6b 99 39 85 99 f5 5b c6
9b 4d 78 02 fe ad fe 09 36 d7 18 20 21 2c e2 ec 06 52 a3 68
d7 c3 18 7f 23 e8 58 12 ba 2a 28 df 10 bc 23 ad cc 22 51 25
c8 03 b8 eb 43 1b d6 5d 70 61 43 4c c0 05 78 72 da 73 d9 e5
85 3a 27 32 85 a0 03 53 1b 8d 36 94 47 95 ef 17 34 8f 16 32
21 52 b7 44 e5 6e 90 d3 19 12 ea 7b fd dd 15 49 19 17 89 3c
a8 16 2c fe 34 24 d3 0c 3d c8 06 cf ac 3b d3 a5 d4 59 e2 2f
65 d4 ba b8 6e 73 a0 40 21 55 f6 b5 db cb 6f 28 09 72 78 57
6b e6 86 f0 a9 b3 34 a9 bc bf 12 09 b2 59 61 b7 a5 d9 7b 24
05 6f 6b 86 be a4 f6 29 b7 b7 a4 16 58 90 de 55 fa 0f 27 5f
3a 19 98 88 70 3a 86 85 b7 95 90 5a 7d cd 6c 1a f0 53 69 d0
9f 38 c1 30 bd 8c 20 4d 84 31 9d 76 e9 da c2 a6 09 b9 b2 5d
ca eb 9d 22 6f ce c4 98 5b 76 a4 8c 0c 39 8c 2f de 66 de a5
b7 25 35 70 6e 40 84 dd 86 a6 f4 f5 2c 11 79 f8 7f 98 5b 45
b5 68 c2 da

Sent Type: REPORT. MessageID: 735951054 to "10.163.228.46:1111".
Sent Time: Thu Nov 01 12:20:57:716 MDT 2012
Length of SNMP DATA: 104
DATA
30 66 02 01 03 30 11 02 04 2b dd b8 ce 02 03 00 ff e3 04 01
01 02 01 03 04 24 30 22 04 03 61 62 63 02 01 00 02 01 07 04
05 41 53 52 4d 32 04 0c 71 66 9c 9a a9 15 83 87 dd d7 2a 22
04 00 30 28 04 03 61 62 63 04 00 a8 1f 02 04 2a 9b 1c f2 02
01 00 02 01 00 30 11 30 0f 06 0a 2b 06 01 06 03 0f 01 01 02
00 41 01 01


The trap is not even coming to the receivedTrap method:
  // we need to instantiate a trap listener to listen for trap events
        TrapListener listener = new TrapListener() {
            // This method is called when trap is received by SnmpTrapReceiver
            public void receivedTrap(TrapEvent trap) {
                System.out.println("Trap received : ");



However, when I used the same trap receptor and send V3 traps from AdventNet SNMP v3 trap sender API
or from other ILOM processor, things are working fine with SNMP v3 traps.

Also, for the same High end server where we are having SNMP v3 issues,
we are able to send V2C traps and receive using AdventNet V2C Trap receptor fine.

Here is the V2 trap (sent from the High end server) which is working fine:
2012-10-04 17:13:36 hostabc.com [10.163.226.140]:         DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1794542864) 207 days, 16:50:28.64     SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.42.2.195.1.7.0.1         SNMPv2SMI::enterprises.42.2.195.1.1.1.2.36.56.50.56.55.51.101.98.53.45.55.100.100.57.45.52.53.49.54.45.57.53.50.51.45.56.48.98.49.50.51.98.53.54.102.102.102 = STRING: "82873eb5-7dd9-4516-9523-80b123b56fff"    SNMPv2SMI::enterprises.42.2.195.1.1.1.3.36.56.50.56.55.51.101.98.53.45.55.100.100.57.45.52.53.49.54.45.57.53.50.51.45.56.48.98.49.50.51.98.53.54.102.102.102 = STRING: "8000-NP"   SNMPv2SMI::enterprises.42.2.195.1.1.1.4.36.56.50.56.55.51.101.98.53.45.55.100.100.57.45.52.53.49.54.45.57.53.50.51.45.56.48.98.49.50.51.98.53.54.102.102.102 = STRING: "http://knowledge-link-msgid/NP"


Could you please let us know why the V3 traps are not getting received, and assist with debugging this issue?

I suspect that there is a bug in the AdventNet SNMP API.