The OID of my writable snmp param is dependend on another value.
For this I am using the id attribute as described in the help.
<OID type="complete" id="50">1.3.6.1.4.1.31210.*.1.1.0</OID>
The value of param 50 is always filled in (there is a default Value)
- When using options="snmpSet", the set is done correctly. It does require me to create extra triggers for every writable param to perform the snmp GET.
- When using snmpSetAndGet="true", the streamviewer indicates: "xx failed : Unable to convert the OID"
Is there a bug in the snmpSetAndGet feature?
I am also confused if I need to use the type wildcard or complete for my use case.
Using wildcard does not solve the problem with the feature:
<OID type="wildcard" id="50">1.3.6.1.4.1.31210.*.1.1.0</OID>
This is indeed known issue.
A task already exists for this but didn't make it through the backlog yet: https://collaboration.dataminer.services/task/75168
Regarding the OID@type attribute, complete is what you should be using.
OID@type="wildcard" only allows to prepend the given OID and doesn't require a whildcard to be added to the OID value.
OID@type="complete" allows to complete the OID anywhere by adding a wildcard where you need to complete it.
So basically you could kind of consider "wildcard" value as obsolete as "complete" value allows to obtain the same result and more.
What version of Dataminer was this issue resovled?