Hello All,
I am currently working on an SNMP connector that polls data from a CMTS device.
Now, the connector must also be capable of going to each individual Cable Modem and polling some data. For this feature, I defined an additional SNMP Connection and implemented a Multithreaded timer.
The issue is that with this new implementation, only the logic linked to the multithreaded timer is getting executed.
The old SNMP Groups never get executed. These groups never appear in the Stream viewer, and in the Pending calls tool, I see that one of the SNMP groups is added to the stack, but it is simply stuck.
I tried incrementing the time interval of the Multithreaded Timer and switching the SNMP connections so this Multithreaded Timer uses the Main connection. But I haven’t had any results.
Is there any restriction with using a Multithreaded Timer and Polling at the same time SNMP groups? Or does anyone have any suggestions on how to solve this behavior?
Hi,
I have tested this with DataMiner version 10.1.12.0 and there it’s working correct. I’m only using one main SNMP connection where both the multithreaded timer and polling groups are making use of. So that seems to be working correct.
Possible issues I can think of:
- Are you using any <Threads> in the driver to define multiple SLProtocol threads instead of only one thread? There is a known issue that this is not compatible with an SNMP connection and causes the SNMP poll groups to be stuck and never get executed
- Is the “loadOID” removed from the “normal” snmp parameter?
Possible workaround in case of the <Threads> issue:
- Define a poll action group to execute a QAction, from there poll the SNMP data through a NotifyProtocol NT_SNMP_GET