[SNMP4J] Trying to send out SNMP Trap

Jim Chan jchan at incognito.com
Tue Mar 18 08:16:32 CET 2008


Thanks Frank,

> Stack Trace from the client indicates it received the trap but an error
occurred:
> 
> Mar 17, 2008 1:20:12 PM org.snmp4j.log.JavaLogAdapter log
> INFO: UDP receive buffer size for socket 192.168.75.108/162 is set to:
8192
> Mar 17, 2008 1:20:20 PM org.snmp4j.log.JavaLogAdapter log
> SEVERE: RFC3412 §7.2.4 - Unsupported security model: 3
> 

> Just configure the USM on the trap receiver site correctly!

> Best regards,
> Frank

I configured a user on my trap receiver as per the TestAgent.  It got passed
the security model, but now it encounters SNMPv3_USM_UNKNOWN_ENGINEID error.

        Snmp snmp = new Snmp(mtDispatcher, transport);
        
        byte[] localEngineID = MPv3.createLocalEngineID();
        snmp.setLocalEngine(localEngineID, 0, 0);
        
        UsmUser user = new UsmUser(
            new OctetString("SHADES"),
            AuthSHA.ID,
            new OctetString("SHADESAuthPassword"),
            PrivDES.ID,
            new OctetString("SHADESPrivPassword"));        
        
        //snmp.getUSM().addUser(new OctetString("SHADES"), 
        //   new OctetString(localEngineID),  user);

        snmp.getUSM().addUser(new OctetString("SHADES"), 
               snmp.getUSM().getLocalEngineID(),  user);
        
        snmp.addCommandResponder(this);
        transport.listen();

2008-55-17 23:03:30 [DEBUG] <DefaultUDPTransportMapping_127.0.0.1/162>
Received message from /192.168.18.100/1610 with length 61:
30:3b:02:01:03:30:11:02:04:75:da:ac:b8:02:03:00:ff:ff:04:01:04:02:01:03:04:1
0:30:0e:04:00:02:01:00:02:01:00:04:00:04:00:04:00:30:11:04:00:04:00:a6:0b:02
:01:00:02:01:00:02:01:00:30:00
2008-55-17 23:03:30 [DEBUG] <DispatcherPool.0> SNMPv3 header decoded:
msgId=1977265336, msgMaxSize=65535, msgFlags=04, secModel=3
2008-55-17 23:03:30 [DEBUG] <DispatcherPool.0> RFC3414 §3.2.3 Unknown engine
ID:

Does anybody know how to resolve this?  I feel I am getting close.  Any help would be appreciated.

Thanks.

Jim





More information about the SNMP4J mailing list