Hi,
We are having issues retrieving data via the NotifyProtocol 295/"NT_SNMP_GET". This issue seems to occur only when certain OIDs from the table are included within the call, if those OIDs are omitted the call works perfectly and is able to bring all of the data. Unfortunately, this seems to be random we have only seen it happen for two tables. This table is able to poll fine through DM native SNMP polling but due to the size and it being apart of an EPM solution Qaction polling was the best course of action. Have anyone experienced this issue using the 295 calls within a Qaction?
Picture of the data in the two columns that caused the call to fail.
Picture of the request
Hi Aldrick,
Can you provide a bit more detail on the actual issue you are experiencing? Do you get any errors or is the response just empty?
Correct, you can only request a limited set of data at once.
The solution here will be to request less values per get request.
Hi, I'm not sure how much data you try to receive in one get request here? Looking at your expected response data, the content looks to be large per record.
Note that the timeout on single command is taken from the Element configurations. In case you want to overrule this, you can put the timeout time along with your request as well. (Please have a look at the help, it also shows other options you can configure)
NT_SNMP_GET (295)
elementInfo[10] (int): Timeout. (Default: The interface port value)
Do you get any kind of response or error returned?
Hi Thijs, the timeout time in the element wizard is 120000ms so this should be sufficient time. The Wireshark response is empty but after further review, I notice the error-status mentioned that it is too big. Is this related more to the size of the response? then a timeout issue correct? Side note, I did some further investigation, when we request all the information at once as oppose to requesting in bulks of 50 cells I was able to retrieve all the data, this issue could be due to appending the instance at the end of the column.
Hi Joey, The Wireshark response is empty but after further review, I notice the error-status mentioned that it is too big. Is this related more to the size of the response? then a timeout issue correct? Side note, I did some further investigation, when we request all the information at once as oppose to requesting in bulks of 50 cells I was able to retrieve all the data, this issue could be due to appending the instance at the end of the column.