Hi,

I'm using the “WebNMS SNMP API 4 (Release 4.0.7)” product for remote equipment monitoring.

On the remote Snmp Agent is configured only one user that we say "anyuser"; all the SNMP requests are snmpv3 “authNoPriv” or “authPriv”.

The SnmpEngineID discovery process is executed in asynchronous mode: the “sendDiscoverMsg” method of “com.adventnet.snmp.snmp2.SnmpEngineEntry” class is used.

Everything works fine!!!

However there is a problem on the remote equipment side:

It's raising a warning alarm of the type: ”Illegal attempt to SNMP log-on by initial user“.

It means that a user named “ initial” (not recognized because not configured on the remote Snmp Agent, it knows only “anyuser”)   is trying to illegally access to the system via SNMP !!!

I found the cause of the problem in the engineID discovery phase when the “sendDiscoverMsg” asynchronous method of SnmpEngineEntry class is invoked; in fact during this phase, is sent a noAuthNoPriv Snmpv3 message with username “ initial” as described in the relative documentation (see snapshot below extracted from https://www.webnms.com/webnms/help/javadocs/protocols/snmp_javadocs/com/adventnet/snmp/snmp2/SnmpEngineEntry.html):

A possible solution to my problem is configure the user used for engineId discovery phase with a qualified user (in my case “ anyuser ” instead of “ initial”), but searching in the  documentation, it seems not possible; it seems that the “initial” user is cabled in the code and it isn’t configurable!!!

There is a workaround? Any suggestions?

Thanks,

Pasquale