Re: Agentx communication issues with net-snmp 5.4.1

Hi Latha,

We had a similar problem going from 5.2.1 to 5.4.1 that was discussed on
this list around April 18. The key fix was to make sure the NetSNMP::OID
call comes AFTER the NetSNMP::agent call. The ordering did not use to matter
but now it does.

Larry Dickson
Cutting Edge Networked Storage

On 5/14/08, [email protected] <[email protected]>
wrote:
>
>
> Hi,
>
> I was using net-snmp 5.1.4 earlier and we have a subagent communicating
> using agentx with our master agent. Things were working fine.
>
> We are now trying to upgrade to net-snmp 5.4.1 and the master agent and
> the subagent are not communicating. The subagent seems to register the
> MIBS fine, I can see this when I turn on logging using -Dagentx. After
> that the snmpget requests are timing out. I see that the master agent is
> sending these requests but not getting any response and is eventually
> timing out and closing the connection. On the subagent's  end, the
> 'agent_check_and_process(1)' call does not come out indicating that it
> did not receive any packets ?
>
> 1. I am building net-snmp 5.4.1 with openssl10.9.7m and ipv6 enabled.
> 2. Running SNMPv3 and snmpd.conf has
> master agentx
> agentXTimeout 10
> agentXRetries 6
> agentXSocket tcp:127.0.0.1:705 (we are using tcp sockets and not unix
> stream sockets).
> 3. snmpd is run as follows $MY_SNMP_PATH/snmpd -x tcp:127.0.0.1:705
> udp:8500 -c /MY_SNMP_PATH/snmpd.conf ie. master is listening on 8500 and
> to subagent (agentX) on 705
> 4.Subagent code does -
> netsnmp_ds_set_boolean(NETSNMP_DS_APPLICATION_ID,NETSNMP_DS_AGENT_ROLE,
> 1); -
> netsnmp_ds_set_string(NETSNMP_DS_APPLICATION_ID,NETSNMP_DS_AGENT_X_SOCKE
> T,"tcp:127.0.0.1:705"); prior to init_agent and init_snmp
> Is it really necessary to have a configuration file with the name given
> in init_agent() ? We have not had that so far and things worked fine ?
> An snmpwalk on .1.3.6.1.2.1 snmpd responds no problems.
> Snmpwalk for my subagent OID results in packets piling on the 705
> connection and it eventually closes with log trace - Timeout: No
> Response from localhost:8500
> netstat traces
> udp 0 0 0.0.0.0:8500 0.0.0.0:*
> ...
> tcp 0 0 127.0.0.1:705 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:705 127.0.0.1:41817 ESTABLISHED
> tcp 3168 0 127.0.0.1:41817 127.0.0.1:705 ESTABLISHED
> ...
> tcp 0 0 127.0.0.1:705 0.0.0.0:* LISTEN
> tcp 4513 0 127.0.0.1:41817 127.0.0.1:705 CLOSE_WAIT
> tcp 0 0 127.0.0.1:705 127.0.0.1:41817 FIN_WAIT2
> This has been working fine with NetSNMP-5.1.4 . Appreciate any inputs as
> to what I'm missing !!!  Is there anything new in 5.4.1 not present in
> 5.1.4 ?
> Thanks in advance.
> -Latha.
>
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Net-snmp-coders mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders