MIB Browser FAQ

iReasoning MIB Browser is a powerful, easy-to-use tool powered by iReasoning SNMP API. It helps engineers manage SNMP-enabled network devices and applications.

MIB Browser can load standard and proprietary MIBs, including some malformed MIBs. It can issue SNMP requests to retrieve data from an agent or change agent values. Its built-in trap receiver can receive SNMP traps and handle trap storms.

The Java Runtime Environment is not installed, or java.exe is not included in the Windows PATH.

You are probably using JRE 1.4 or an earlier release. MIB Browser requires JRE 1.5 or newer.

Because iReasoning MIB Browser is written in Java, it can run on any operating system with a compatible Java Virtual Machine.

Yes. Download and extract the ZIP archive, open the ireasoning/mibbrowser directory, and double-click browser.command or the browser icon.

The Linux edition of the MIB Browser installer does not bundle Sun's JVM. A preinstalled JVM on the computer may not be compatible with Sun's JVM. Install the Linux edition of Sun's JVM before starting MIB Browser.

Open config/mibbrowser.xml, set loggingLevel to DEBUG, and restart MIB Browser. The packets will then appear in the log window, as in this example:

2004-03-29 10:31:56 - SEND data length = 36
2004-03-29 10:31:56 - 30 22 02 01 00 04 06 70 75 62 6C 69 63 A1 15 02    0".....public...
2004-03-29 10:31:56 - 02 78 E6 02 01 00 02 01 00 30 09 30 07 06 03 2B    .x.......0.0...+
2004-03-29 10:31:56 - 06 01 05                                           ...
2004-03-29 10:31:56 - RECV data length = 171
2004-03-29 10:31:56 - 30 81 A8 02 01 00 04 06 70 75 62 6C 69 63 A2 81    0.......public..
2004-03-29 10:31:56 - 9A 02 02 78 E6 02 01 00 02 01 00 30 81 8D 30 81    ...x.......0..0.
2004-03-29 10:31:56 - 8A 06 08 2B 06 01 02 01 01 01 00 04 7E 48 61 72    ...+........~Har
2004-03-29 10:31:56 - 64 77 61 72 65 3A 20 78 38 36 20 46 61 6D 69 6C    dware: x86 Famil
2004-03-29 10:31:56 - 79 20 36 20 4D 6F 64 65 6C 20 38 20 53 74 65 70    y 6 Model 8 Step
2004-03-29 10:31:56 - 70 69 6E 67 20 33 20 41 54 2F 41 54 20 43 4F 4D    ping 3 AT/AT COM
2004-03-29 10:31:56 - 50 41 54 49 42 4C 45 20 2D 20 53 6F 66 74 77 61    PATIBLE - Softwa
2004-03-29 10:31:56 - 72 65 3A 20 57 69 6E 64 6F 77 73 20 32 30 30 30    re: Windows 2000
2004-03-29 10:31:56 - 20 56 65 72 73 69 6F 6E 20 35 2E 30 20 28 42 75     Version 5.0 (Bu
2004-03-29 10:31:56 - 69 6C 64 20 32 31 39 35 20 55 6E 69 70 72 6F 63    ild 2195 Uniproc
2004-03-29 10:31:56 - 65 73 73 6F 72 20 46 72 65 65 29                   essor Free)

Use a text editor to add mib nodes to config/mibbrowser.xml. For example:

<mib name="C:\mibs\RFC1213-MIB" />
<mib name="C:\mibs\IF-MIB" />

Loading many MIBs requires additional memory. The Java Virtual Machine's default maximum heap size may be 64 MB. Increase it by editing browser.bat. For example, the following command sets the maximum heap to 256 MB:

java -Xmx256m -jar "%BROWSER_HOME%\lib\browser.jar"

Yes. Use a text editor to add a mib node to config/mibbrowser.xml. For example:

<mib name="C:\mibs\RFC1213-MIB" />

MIB Browser will then load C:\mibs\RFC1213-MIB automatically when it starts.

Counter64 is not available in SNMPv1. By default, MIB Browser assumes that the remote device is an SNMPv1 agent. Select Advanced and configure the current agent to use SNMPv2c or SNMPv3.

Another application is already using port 162 and must be stopped before you open the trap receiver. On Windows, the conflicting application is often the SNMP Trap service. You can stop it with:

net stop snmptrap

On Linux, Unix, or Mac OS X, a non-root user who needs to run the trap receiver on privileged UDP port 162 can start MIB Browser with:

sudo browser.sh

Possible causes include:

• The SNMP agent is not running.
• The SNMP community name is incorrect.
• The timeout value is too short.
• The agent does not support the requested OID.

The SNMP write community name may be incorrect. The write community is usually different from the read community.

The target SNMP agent does not support the requested OID.

The polling interval should not be too short. One second is usually insufficient for most SNMP agents to return all rows in a table, and many OID values do not change that frequently.

No. MIB Browser is not affected by CVE-2021-45046, which concerns Apache Log4j 2 Thread Context Lookup Patterns in certain non-default configurations. According to the Apache Log4j security advisory, Log4j 1.x is not affected by this vulnerability. MIB Browser uses Log4j 1.2.8.