[SNMP4J] TestAgent and SNMPv3

Ricardo Nabinger Sanchez rnsanchez at wait4.org
Tue Dec 19 02:23:49 CET 2006


On Mon, 18 Dec 2006 20:12:24 +0100
Frank Fock <fock at agentpp.com> wrote:

> Yes, you are missing something obvious:
> You have *excluded* the sub-trees from your
> view and you then try to access them.
> When you *include* them you probably have more
> luck ;-)

Geez!  I need a pointy hat for those.

Well, after including them (basically I switched the VacmMIB.vacmViewExcluded
by VacmMIB.vacmViewIncluded for the few ones there), I still get the same
output:

Client:

% java -jar SNMP4J.jar -a SHA -A maplesyrup -u TEST -p GETNEXT -Ow 127.0.0.1/12345 .1.3.6.1.2.1.4.24
Dec 19, 2006 1:16:43 AM org.snmp4j.log.JavaLogAdapter log
INFO: UDP receive buffer size for socket 192.168.1.100/0 is set to: 42080
Dec 19, 2006 1:16:44 AM org.snmp4j.log.JavaLogAdapter log
WARNING: 1.3.6.1.6.3.15.1.1.2.0 = 1
Dec 19, 2006 1:16:45 AM org.snmp4j.log.JavaLogAdapter log
WARNING: 1.3.6.1.6.3.15.1.1.2.0 = 2

Total requests sent:    1
Total objects received: 0
Total walk time:        2196 milliseconds
Request timed out.


Agent:

UsmUser[secName=SHADES,authProtocol=1.3.6.1.6.3.10.1.1.3,authPassphrase=SHADESAuthPassword,privProtocol=1.3.6.1.6.3.10.1.2.2,privPassphrase=SHADESPrivPassword,localizationEngineID=null]
UsmUser[secName=TEST,authProtocol=1.3.6.1.6.3.10.1.1.3,authPassphrase=maplesyrup,privProtocol=1.3.6.1.6.3.10.1.2.2,privPassphrase=maplesyrup,localizationEngineID=null]
UsmUser[secName=SHA,authProtocol=1.3.6.1.6.3.10.1.1.3,authPassphrase=SHAAuthPassword,privProtocol=null,privPassphrase=null,localizationEngineID=null]
...
3161 [DefaultUDPTransportMapping_0.0.0.0/12345] WARN org.snmp4j.MessageDispatcherImpl  - 1.3.6.1.6.3.15.1.1.4.0 = 1
3654 [DefaultUDPTransportMapping_0.0.0.0/12345] WARN org.snmp4j.MessageDispatcherImpl  - 1.3.6.1.6.3.15.1.1.2.0 = 1
4198 [DefaultUDPTransportMapping_0.0.0.0/12345] WARN org.snmp4j.MessageDispatcherImpl  - 1.3.6.1.6.3.15.1.1.2.0 = 2


This:

% snmptranslate 1.3.6.1.6.3.15.1.1.2.0
SNMP-USER-BASED-SM-MIB::usmStatsNotInTimeWindows.0

Probably tells me that I need to raise the timeout.  Am I right this time?

Although I don't know where should I set the timeout (I've seen messages on the
list setting it, but I don't know where should I do this for the TestAgent).

Any hints much appreciate, and in the meantime I'll try to find it.

Thanks again.  :)
Regards.

-- 
Ricardo Nabinger Sanchez     <rnsanchez@{gmail.com,wait4.org}>
Powered by FreeBSD

  "Left to themselves, things tend to go from bad to worse."



More information about the SNMP4J mailing list