Re: Discovering peer engineID while sending INFORMS
Wes Hardaker <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Organization | Sparta |
| Message-ID | <[email protected]> |
>>>>> "EBP" == Enric Bel Prim <[email protected]> writes: EBP> I've found that when the first inform is not 'aknowledged' by the trap EBP> receiving system (after 5 retries), the agent doesn't send any inform to it EBP> anymore. I believe this is fixed in very recent versions... Or I thought it was at least. But you indicate otherwise: EBP> I've detected this behaviour using net-snmp versions 5.3.0.1 and EBP> 5.3.1libraries in a subagent module through agentx (SNMPV3) EBP> running on Linux. Is this behaviour correct? Shouldn't the EBP> agent keep trying to obtain the engineID of the receiver if the EBP> previous communication failed? Yes, it should. It wasn't handled for a very long time in the code and it was a known inefficiency. EBP> But this modification provoques two effects: 1) the engineID is EBP> requested for every inform while we have no answer from the EBP> receiver (OK ;)))). 2)The informs are repeated a lot of times EBP> when the receiver acknowledge them (BAD!!!). Obviously we'll have to do something to fix #2 of your solution ;-/ -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users