Both computers have the same "snmpd.conf" file. Besides, supposing that the engineId and incremented engineBoots values were different, I still can  use my function when I exit the CLI and start it again. There must be a way to clean all the variables so that, from the function perspective, it seems that the CLI was re-started.


Thanks,
            Rafael.

On 8/31/05, Thomas Anders <[EMAIL PROTECTED]> wrote:
Rafael Garabato wrote:
>           The problem is that there are two computers that has the snmp
> agent and they switch between each other to be the active computer. When
> they switch the snmp configuration parameters (user, password and  ip)
> remains the same so it should be possible to continue using my snmpget
> function without problems (because the session is opened inside this
> function). Unfortunatelly this does not happen. Despite the fact that
> the session is opened correctly when I read the data I get a timeout
> error. If I exit the cli and start it again everything works fine.

Are you sure the other box takes over *all* the necessary *persistent*
configuration? With SNMPv3 this especially involves to come up with the
*same* engineId and an *incremented* engineBoots value. Otherwise you'll
get what you ask for: trouble.


+Thomas

--
Thomas Anders ( thomas.anders at blue-cable.de)


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to