[SNMP4J] trap display problem

[Frank Fock]

Hi Jiang,

Obviously, this is a bug/shortcoming in the OpManager
software. I have had other issues with AdventNet tools
(the Advent SNMP API for instance) that sometimes do
not fully comply to the SNMP standard in the past.

May be this is another issue, but it might be also a
configuration problem (output string length?).

Best regards,
Frank

Jiang wrote:
> Hi,
> 
> I am using SNMP4J to send trap and using AdventNet OpManager to capture it.
> But all the traps cannot be displayed in full, as shown below:
> 
>     Attention       May 17,2006 08:44:20 PM      convertercoldstart is
> received from 10.226.200.107 with the following related information :
> sysUpTime: 0 hours, 0 minutes, 0 seconds. , .1.3.6.1.6.3.1.1.4.1.0:
> .1.3.6.1.4.1.3830.65.1.1.100.2.1, .1.3.
>    Critical     May 17,2006 08:38:43 PM     convertercoldstart is received
> from 10.226.200.107 with the following related information : sysUpTime: 0
> hours, 0 minutes, 0 seconds. , .1.3.6.1.6.3.1.1.4.1.0:
> .1.3.6.1.4.1.3830.65.1.1.100.2.1, .1.3.
> 
> You may notice that the varbind is not a complete one. I did a tcpdump and
> it shows everything well:
> 
> Simple Network Management Protocol
>    Version: 2C (1)
>    Community: public
>    PDU type: TRAP-V2 (7)
>    Request Id: 0x35692f17
>    Error Status: NO ERROR (0)
>    Error Index: 0
>    Object identifier 1: 1.3.6.1.2.1.1.3.0 (SNMPv2-MIB::sysUpTime.0)
>    Value: Timeticks: (59) 0:00:00.59
>    Object identifier 2: 1.3.6.1.6.3.1.1.4.1.0 (SNMPv2-MIB::snmpTrapOID.0)
>    Value: OID: SNMPv2-SMI::enterprises.3830.65.1.1.100.2.1
>    Object identifier 3: 1.3.6.1.4.1.3830.65.1.1.100.1.1 (SNMPv2-SMI::
> enterprises.3830.65.1.1.100.1.1)
>    Value: STRING: "2006-05-17 20:52:10"
>    Object identifier 4: 1.3.6.1.4.1.3830.65.1.1.100.1.2 (SNMPv2-SMI::
> enterprises.3830.65.1.1.100.1.2)
>    Value: STRING: "info"
>    Object identifier 5: 1.3.6.1.4.1.3830.65.1.1.100.1.3 (SNMPv2-SMI::
> enterprises.3830.65.1.1.100.1.3)
>    Value: STRING: "snmpAgent started!"
> 
> So I am thinking if it is opmanager's problem? Or if I have missed 
> something
> here?
> 
> Thanks!
> 

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com