Hi Dojo;
I have a protocol where SNMP sets in a table are done through a write parameter which has a options="snmpSet" attribute.
The device is returning failed set message with WRONG TYPE reason. But my write parameter holds the same Interprete/Measurement type and the same SNMP.Type values.
Parameter holding the SNMP Set value with a reference to the partial OID param (PID 32):
<Param id="49158" options="snmpSet">
<Name>mtsMtpTxUdpRemoteInetPort_SNMPSET</Name>
<Description>Remote Inet Port SNMPSET(MTS MTP Tx UDP Table)</Description>
<Type>write</Type>
<Interprete>
<RawType>numeric text</RawType>
<Type>double</Type>
<LengthType>next param</LengthType>
</Interprete>
<SNMP>
<Enabled>true</Enabled>
<OID type="complete" id="32">1.3.6.1.4.1.2928.2.8.2.6.1.8.*</OID>
<Type>uinteger32</Type>
</SNMP>
<Display>
<RTDisplay>true</RTDisplay>
</Display>
<Measurement>
<Type>number</Type>
</Measurement>
</Param>
The value to set is read from the write column corresponding to the read parameter below. The write parameter also has the same Interprete/Measurement type combination.
Initial read parameter XML:
<Param id="49008" trending="false">
<Name>mtsMtpTxUdpRemoteInetPort</Name>
<Description>Remote Inet Port (MTS MTP Tx UDP Table)</Description>
<Information>
<Subtext>
<![CDATA[The UDP port at the remote host that shall receive the
stream.]]>
</Subtext>
</Information>
<Type>read</Type>
<Interprete>
<RawType>numeric text</RawType>
<Type>double</Type>
<LengthType>next param</LengthType>
</Interprete>
<SNMP>
<Enabled>true</Enabled>
<OID type="complete">1.3.6.1.4.1.2928.2.8.2.6.1.8</OID>
<Type>uinteger32</Type>
</SNMP>
<!-- SuppressValidator 2.5.1 Depend on the use case. -->
<Alarm>
<Monitored>true</Monitored>
</Alarm>
<!-- /SuppressValidator 2.5.1 -->
<!-- SuppressValidator 2.9.7 A port number does not have a unit. -->
<Display>
<RTDisplay>true</RTDisplay>
<Range>
<Low>0</Low>
</Range>
</Display>
<!-- /SuppressValidator 2.9.7 -->
<Measurement>
<Type>number</Type>
</Measurement>
</Param>
Any idea how to resolve this?

Hi Benjamin,
I encountered a similar issue with one of the protocols. After some investigation using the MIB Browser (where the set operations were successful) and analyzing the traffic in Wireshark, I discovered that the issue was due to the SNMP type.
Instead of using uinteger32 (listed in MIBs), the device expects the SNMP type gauge32.
Updating the SNMP type for both the read and write parameters resolved the issue.
Example:
<SNMP>
<Enabled>true</Enabled>
<OID type="complete">[parameter OID]</OID>
<Type>gauge32</Type>
</SNMP>
Thanks Dario! It worked
Hi,
I see the oid from the read parameter is different from the write parameter.
Read: <OID type="complete" id="32">1.3.6.1.4.1.2928.2.8.2.6.1.8.*</OID>
Write: <OID type="complete">1.3.6.1.4.1.2928.2.8.2.6.1.8</OID>
Could you double check this?