By using the MIB compiler you can compile text MIB files into a binary format that Network Monitor can read. Compiling MIB files requires understanding about how MIB files work as well as a general understanding of SNMP and MIB objects. A number of different RFC documents outline the fundamental base that all other MIB files are based on.
Note: The community name, SNMP version, and port used used by Network Monitor to connect to an SNMP asset is set on the Authentication tab of an asset node. The asset node may inherit this setting from a parent node. See the Installation Checklist.
As an example, this is the compile order of a CISCO ® product MIB.
SNMPv2-SMI.mib
SNMPv2-TC.mib
SNMPv2-MIB.mib
RFC1213-MIB.mib
IF-MIB.mib
CISCO-SMI.mib
CISCO-PRODUCTS-MIB.mib
CISCO-TC.mib
The first 5 files in this example are common for most product MIB files, and are included in the default
binary MIB file. knm.mib
Warning: All of these files must be compiled at the same time, otherwise the MIB compiler fails due to unresolved symbols.
Contents of the default KNM MIB file
The default
file included in the installation contains the following base OIDs (object identifiers).knm.mib
iso.org.dod.internet.directory
iso.org.dod.internet.mgmt
iso.org.dod.internet.experimental
iso.org.dod.internet.private
iso.org.dod.internet.security
The file is located in the
directory.\<Kaseya_Installation_Directory>\KNM\mibs
Download and Run the MIB Compiler
Compiling a MIB file
<Kaseya_Installation_Directory>\knm\mibcompiler.exe
.*.mib
files.knm.mib
file in the KNM\mibs
folder of the Network Monitor host machine and double click it to select it.*.mib
files you want to include for compiling.*.dat
file. *.dat
file that was just compiled. An interactive MIB tree displays in the main window. You can use it to navigate through the different OIDs.*.dat
file to the KNM\mibs
folder.