Hi Dojo,
I’m encountering an issue with the NT_SNMP_GET call on DataMiner version 10.6.5.0-17061.
Standard SNMP GET/SET operations are working correctly for all parameters, and the GET also works as expected when performed via the MIB Browser. However, when executing the same request using NT_SNMP_GET, it fails.
Below is the exception I’m receiving:
2026/05/04 15:28:39.617|SLManagedScripting.exe|ManagedInterop|ERR|-1|16104|7|NotifyProtocol with 295 failed. 0x80040221 QA: 10000 Var1: VT_ARRAY|VT_VARIANT (6) 0 VT_I4 : 2443 1 VT_BSTR : 10.22.172.225 2 VT_I4 : 0 3 VT_BSTR : 4 VT_I4 : 0... Var2: VT_ARRAY|VT_BSTR (1) : 1.3.6.1.4.1.2928.6.2.16.1.2.3.1.8.3 2026/05/04 15:28:39.619|SLManagedScripting.exe|ManagedInterop|ERR|0|16104|7|QA10000|498|Run|Exception thrown: System.ArgumentNullException: Value cannot be null. Parameter name: source at System.Linq.Enumerable.Select[TSource,TResult](IEnumerable`1 source, Func`2 selector) at Skyline.Protocol.Netinsight.Nimbra.Snmp.ProtocolExtensions.SnmpGet(SLProtocol protocol, String pollingIP, Boolean multipleGet, String commmunityString, String[] oids) at Skyline.Protocol.Manager.ExternalCommands.SetItsDestinationHandler..ctor(SLProtocolExt protocol, IRequest request) at QAction.SetItsDestination(SLProtocolExt protocol, ContextData contextData) at QAction.OriginatingTtpDestinationContext(SLProtocolExt protocol, ContextData contextData) at QAction.Run(SLProtocolExt protocol, Object contextObject)
From the implementation, it appears the failure occurs because the response is null, which is unexpected:
I’ve verified that the same logic works on a staging environment running DataMiner version 10.5.7, although this was not tested against the same device.
Could you please advise whether this might be a connection related issue, or if there have been any changes or deprecations affecting NT_SNMP_GET in version 10.6.5.0-17061?
Hi,
Could you modify the object[] request to have the same structure with the agentId included as documented here
As there is no agentId included, it means that it is not DELT compatible.
Does the element config SNMP type match? e.g. the element itself is not configured as SNMPv3 while the QAction passes the as if it is SNMPv1/v2?
Regards,
Hi Laurens, I can confirm that issue is resolved when I added DMA ID in request, thanks.
Thank you for confirming that the issue is resolved. Glad to hear that it is now working.
Hi Dario,
To rule out a device-related issue, would it be possible to use a packet capture tool (e.g. Wireshark) to inspects SNMP get request sent by the DMA? You could then compare the request from both environments to confirm that the connector is sending the same request.
Hope it helps.