Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Video Library
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
    • Books We Like
    • >> Go to DataMiner Docs
  • DevOps Professional Program
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
  • Downloads
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
  • More
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • >> Go to dataminer.services

SNMP – Wrong type when using options=”snmpSet” parameter

Solved61 views2 days agoSNMP Connector XML
2
Benjamin Hodžić [SLC] [DevOps Advocate]1.21K 5 days ago 1 Comment

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?

Benjamin Hodžić [SLC] [DevOps Advocate] Selected answer as best 2 days ago
José Silva [SLC] [DevOps Catalyst] commented 2 days ago

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?

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
Dario Sarkanovic [SLC] [DevOps Advocate]911 Posted 2 days ago 1 Comment

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>

Benjamin Hodžić [SLC] [DevOps Advocate] Selected answer as best 2 days ago
Benjamin Hodžić [SLC] [DevOps Advocate] commented 2 days ago

Thanks Dario! It worked

You are viewing 1 out of 1 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin