Hi Dojo,
I am currently working with a slower SNMP device, so I need to make some delay between polling the parameters, otherwise I get command timeouts.
I tried to use "next" attribute (next attribute | DataMiner Docs) and I specified next="2000", but it seems that it adds delay only after the last parameter in the group (delay before polling the parameter from the group that is polled afterwards). I expected that it will add delay after each parameter (poll one parameter, wait for 2000 ms, then poll the second one...)
Could you please help me? Am I missing some part of the implementation important for this "next" attribute or is this a bug?
Thank you in advance for your assistance and time. 🙂
Thank you, Robbie, so it is probably a software bug.
At first, it was implemented with multipleGet=”true” but device cannot handle it. There were even more timeouts with that configuration.
Hi,
That is a software issue. Due to an internal lock, all items are added to the polling queue with the needed delay but are then all processed in one go.
Please create a ticket for this software issue so it can be fixed.
Regards,
A workaround for the current slow device could be to create a group per parameter that needs to be retrieved, this way there will be the spreading of one request per 2 seconds. I know it’s not an ideal solution, but it seems the only possibility at this moment to spread the parameter requests
Your implementation and logic are correct according to the documentation.
For the slower device, is it possible to retrieve all the data when having multipleGet=”true” in the group instead of false? as it will only do 1 request instead of 4 to get the data.