[snmp] SNMP Set Response is lost / packet dropped by Westhawk API

[Birgit Arkesteijn]

Hi Kevin,

Not a problem.

Reusing a context (where possible) is always a good idea. Also, when 
calling destroy() immediately, you run the risk that the context is gone 
before the response is received.

We always advocate sending a next (or sequential) request when the 
response to the previous request is received (in update()).
This way you allow the network to drive the speed of your requests.

Cheers, Birgit


On 04/06/08 20:09, Kevin Bond wrote:
> Hi Birgit,
> 
>     Thanks for your quick response and I apologize for my delayed reply.
> 
>     I resolved the issue after making some changes to the frequency of 
> SNMP V2C Context creation. I have given root cause observed to help you 
> get a better handle on the issue.
> 
>     In the project, I had an SNMP Adapter layer where I used to create a 
> Context to execute the command and destroy the context immediately after 
> the execution. This layer had no visibility on the frequency of execution.
> 
>     In the particular scenario, the layer using the SNMP Adapter sent a 
> lot of set requests in sequence (one by one). In this scenario WestHawk 
> stack had the mentioned problem in receiving the response from the 
> device. I changed the context handling to use the same SNMP V2c Context 
> for subsequent requests to avoid the problem.
> 
>    I am using the latest 6.0 stack and only V2C Contexts.
> 
> Hope this helps,
> Kevin


-- 
-- 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>