<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[SNMP enumerations in Object Tool]]></title><description><![CDATA[<p dir="auto">Hello,<br />
I'd like to ask you if there is a way how to display string enumerations from a MIB file instead of an integer value in a SNMP Table Object Tool (or in MIB Explorer)?</p>
<p dir="auto">The snmp integer enumerations are described for example here:<br />
<a href="https://www.webnms.com/snmp/help/snmpapi/snmpv1/using_mibs_in_applns/enumintegers.html" rel="nofollow ugc">https://www.webnms.com/snmp/help/snmpapi/snmpv1/using_mibs_in_applns/enumintegers.html</a><br />
and in the mib file (mymibfile.txt), they can look like this</p>
<pre><code>severity OBJECT-TYPE
	SYNTAX	INTEGER {
				info(0),
				warning(1),
				error(2),
				fatalError(3)
			}
	MAX-ACCESS	read-only
	STATUS		current
	DESCRIPTION	"Severity of the error"
</code></pre>
<p dir="auto">Instead of a number (1), I would like to see the associated string (warning) in the table.</p>
<p dir="auto">I tried to track the enumerations in code, but it seems to me that they don't even get to the netxms.mib file. Does NetXMS read the mib files (with .txt suffix) again or is it necessary to store the enumeration strings in the netxms.mib file? I'm afraid that modifying the netxms.mib file could cause a lot of trouble during parsing.</p>
<p dir="auto">I could try to implement this functionality myself (if it isn't implemented yet), but now I feel a bit lost, so each hint or advice would help me.</p>
<p dir="auto">I'm using NetXMS 2.0-M2 on Ubuntu.</p>
]]></description><link>https://forum.netxms.org/topic/3712/snmp-enumerations-in-object-tool</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:22:54 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/3712.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 18 Apr 2015 13:40:59 GMT</pubDate><ttl>60</ttl></channel></rss>