[snmp] SNMP v3 discovery bug in 5.1

[Birgit Arkesteijn]

Hi Josh,

I'm still not too sure.
Timeline is only discovered when the engineid was successfully 
discovered, so when timing out on engineid, it shouldn't go for timeline.

Birgit


On 11/10/07 19:29, Josh Bers wrote:
> Birgit,
> 
> I think in your response you may have answered the question: since discovery
> involves potentially two PDU's (timeline & engineid) that would result in 2x
> the timeout :-) Make sense?
> 
> Josh
> 
>> -----Original Message-----
>> From: Birgit Arkesteijn [mailto:birgit at westhawk.co.uk] 
>> Sent: Wednesday, October 10, 2007 6:02 AM
>> To: Josh Bers
>> Cc: Jonathan Tung; 'List for discussion of the Westhawk SNMP 
>> stack'; 'Stephane Blais'
>> Subject: Re: [snmp] SNMP v3 discovery bug in 5.1
>>
>>
>> Hi Josh,
>>
>> Sorry for my late reply, I was on holiday for two weeks.
>>
>> I don't know where the 10s comes from.
>> Discovery is only done (if needed) when adding the pdu to the 
>> v3 context. First the engineid is discovered (unless already 
>> known), then the 
>> timeline is discovered (only if the engine id is known AND 
>> the timeline 
>> isn't known yet).
>>
>> Cheers, Birgit
>>
>>
>> On 28/09/07 22:45, Josh Bers wrote:
>>> Birgit,
>>>
>>> I have confirmed the success of the fix. One strange behavior: On 
>>> failure when disconnected, it takes about 10 seconds for 
>> the discovery 
>>> timeout to happen even though my retry array is [750, 1500, 2250]. 
>>> Does discovery try twice per retry?
>>>
>>> Regards,
>>>
>>> Josh


-- 
-- Birgit Arkesteijn, birgit at westhawk.co.uk,
-- Westhawk Ltd, Albion Wharf, 19 Albion Street, Manchester M1 5LN, UK
-- Company no: 1769350
-- Registered Office:
-- 15 London Road, Stockton Heath, Warrington WA4 6SJ. UK.
-- tel.: +44 (0)161 237 0660
-- <URL: http://www.westhawk.co.uk>