SNMP Queries Using Paessler SNMP Tester
This chapter explains how to perform SNMP queries to an anynode system using the Paessler SNMP Tester. This software is a free Windows tool from Paessler AG and can be downloaded from SNMP Tester. It is particularly useful for verifying connectivity, OID availability, and SNMP responses before integrating with monitoring systems like PRTG. .
Prerequisites
Before proceeding, make sure you have:
-
Downloaded and installed the Paessler SNMP Tester. Please uninstall the previous versions before you install a new one.
-
The target device's IP address (here:
10.1.11.9). -
SNMP is enabled on the target anynode instance.
-
The community string (e.g., "
public"). -
Knowledge of the OID(s) you want to query (or MIB-to-OID mapping tools if needed).
-
Configure SNMP Service to Accept Packets from Specific Hosts as described in the Windows Services list with SNMP Service. chapter.
Open the Services console:
-
Press
Windows + R, typeservices.msc, and press Enter.
Locate and double-click the service named:
SNMP Service
Switch to the Security tab.
In the Accepted community names section:
In the "Accept SNMP packets from these hosts" section:
Select: Accept SNMP packets from these hosts
Click , then enter the IP address of your anynode instance, in our example this is:
10.1.11.9
Click on .
Configuration in SNMP Tester (localhost)
Launch Paessler SNMP Tester.
Under the Set SNMP Settings section, enter the following:
-
IP-Address / DNS Name: The IP address of your anynode instance, in our example 10.1.11.9(IPv4 address)
-
SNMP Version: v2c
-
Port: 161
-
Community String: public
-
Timeout: default value
In the Select Request Type section:
-
Select Custom OID
-
Enter the OID you want to test.
Example: .1.3.6.1.4.1.42303.2.1.3.0
At Run Test, click to execute the query.
This output confirms that the SNMP agent at 10.1.11.9 responded successfully with a string value "4.13.96"—likely
the current software version of the anynode instance.
Converting the anynode MIB to OIDLIB Using Paessler MIB Importer
This chapter explains how to convert the anynode MIB file into an .oidlib file
using the Paessler
MIB Importer. This is free Windows software and can be downloaded at Paessler Website.
The .oidlib file format is required by PRTG Network Monitor and Paessler
SNMP Tester to visualize, query, and manage SNMP data more efficiently
Prerequisites
Before starting the conversion process, ensure you have:
-
The official anynode MIB file (usually provided by TE-SYSTEMS). On Windows, the MIB file is located in the directory
C:\Program Files\TE-SYSTEMS\anynode monitor\res -
The latest version of the Paessler MIB Importer installed on your Windows system
-
A basic understanding of OIDs and SNMP trees.
Step-by-Step: Convert MIB to OIDLIB
Launch Paessler MIB Importer
Start the application from the Start menu or desktop shortcut.
Load the MIB File
Click “File” > “Import MIB File”
Browse to the location of your anynode.mib file.
C:\Program Files\TE-SYSTEMS\anynode monitor\res
Click .
View Parsed OIDs
The tool will parse the MIB and display a tree structure of all available OIDs
You can expand branches to explore sub-elements.
Save as OIDLIB File
Once the MIB is successfully parsed, click:
File > Save Complete OIDLib.
Choose a location and filename, e.g., anynode.oidlib
Click
Save for PRTG Network Monitor
If you have PRTG Network Monitor already installed:
Once the MIB is successfully parsed, click:
File > Save for PRTG Network Monitor
This will save the anynode.oid.lib in the correct PRTG SNMPLIBS folder.
C:\Program Files (x86)\PRTG Network Monitor\snmplibs
Choose a filename, e.g., anynode.oidlib
Click .
Result
You now have a compiled .oidlib file, which:
-
Can be loaded into PRTG to create custom SNMP sensors.
-
Can be used with Paessler SNMP Tester for manual OID browsing and testing. Open the file with Scan OIDLIB
-
Offers faster access to the most relevant anynode OIDs in a structured format.
Recommendations for Managing anynode OID Libraries
-
Versioning: Keep track of which anynode version the MIB refers to. MIBs can change across software releases.
-
Naming Convention: Use clear file names, e.g.,
anynode_v4.13.96.oidlib. -
Documentation: Note any non-standard or custom OIDs that are especially relevant for your monitoring setup (e.g., SIP channel usage, license status, etc.).