It depends on the kind of error you are confronted with:

Missing import module

Explanation:

This means that at least one MIB file containing important definitions for your MIB file can not be found. While MIB Importer is already equipped with a set of generic definition files for import (mainly from the RFCs) it cannot feature all MIB files from every manufacturer.

Solution:

• Simply enter the name of the missing file into Google and add a "MIB" to it. Very probably you'll find a link that leads to the missing file. Or contact the manufacturer of your device and ask for the file.
• Copy the file to the folder where the MIB file you want to import is located.
• If the error still persists, rename the file to the exact module name (with the extension .mib or .my)

Identifier (or something else) expected

Explanantion:

MIB files have to be defined and formatted in a very strict notation (ASN.1). Unfortunately, very often the authors of MIB files are not so strict about it and implement a lot of syntactic errors. The Paessler MIB Importer tries to be tolerant about this but cannot guarantee to solve all these problems.

Solution:

• Unless you're a very advanced user with some experience in the structure of MIB files and try to fix it yourself, you should contact the Paessler support team.

See also

• How can I import my MIB files into PRTG?
• Where can I find MIB files for my device?