Hi everyone
I'm working on a connector that has a SNMP table where some sets do not work.
I see on the Stream Viewer that the set is being done on the correct OID and with the correct value and the "Succeeded" is returned.
However, when the table is polled again I see that the value wasn't set on the device.
I created a standalone parameter, just to make sure that the table wasn't the issue. Did not work either. I also changed the snmpSetAndGet to only snmpSet. No luck.
Keep in mind that I can perform the sets on the Mib browser. Any ideas on how to proceed next?
In addition to the previous response by Laurens:
Some devices require you to confirm the sets. In that case, you can set multiple parameters using SNMP in the front-end SNMP table. After all parameters are set you have to enable the changes (most commonly done by setting another SNMP parameter to a certain value). The device then pushes these to the back-end.
Vendors tend to use this when they block of certain setting-combinations.
For example, a device where setting A can't be 1 if setting B is 2, and vice versa. In this case, you have to set both A and B at the same time using that front-end SNMP table, otherwise, each set will be blocked. While filling in that front-end table you won't see the changes until they are pushed.
Hi,
A possibility is that some devices take some time to actually process the value so if you poll the get too fast after the set then you might end up with the old value.
Things that could be checked:
-What happens when you wait a few seconds before getting the value after the set?
-Is it possible to compare via Wireshark the communication between DataMiner and the device and the communication between the mib browser and the device when executing the set? This way you could see where it might be going wrong in the background
