[SNMP4J] AgentX SNMP4J subagent and NetSNMP master agent problem

Frank Fock fock at agentpp.com
Wed Jun 21 15:37:31 CEST 2006


Hi Thomas,

I also think that this is one of the various NET-SNMP
AgentX bugs. A GET should always include the OID
itself.

The NET-SNMP sub-agent for example does not handle
search ranges correctly. I have implemented some
workarounds in AGENT++ to successfully handle this
in most cases. I have done similar efforts for
SNMP4J-Agent.

I reported those bugs to the NET-SNMP community
years ago for the 4.x releases and reported them
again for 5.1 several months ago. It does not seem
that there is anyone at NET-SNMP who wants to fix
that.

Best regards,
Frank

Thomas Leseney wrote:
> Hi all,
> 
> I've tried the new AgentX features of SNMP4J and it works great with
> the SNMP4J master agent.
> 
> However I've run across a problem when using NetSNMP as a master agent.
> When an SNMP GET request is sent to NetSNMP it forwards an AgentX GET PDU
> to the SNMP4J subagent. As specified, the GET PDU includes a search 
> range with
> the variable binding's name encoded into the starting OID and null as 
> the ending OID.
> 
> The problem is that, unlike the SNMP4J master agent, NetSNMP sets the 
> include
> bit in the starting OID to 0. As a result, the SNMP4J subagent replies 
> with a no such
> instance error.
> 
> As far as I understood, the include bit should be set to 1 (as the 
> SNMP4J master agent does)
> and the problem lies in the NetSNMP AgentX implementation. Do you agree ?
> 
> Regards,
> 
> Thomas
> 
> 
> 
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j

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




More information about the SNMP4J mailing list