Solutions To SNMP MIB Problems with Configuration, Compiling, and Reference MIBs

What Is a SNMP (Simple Network Management Protocol) MIB File?

        FROM RFC1213-MIB
        FROM RFC-1212
        FROM RFC1155-SMI;
dpsInc OBJECT IDENTIFIER ::= {enterprises 2682}
dpsAlarmControl OBJECT IDENTIFIER ::= {dpsInc 1}
tmonXM OBJECT IDENTIFIER ::= {dpsAlarmControl 1}
tmonIdent OBJECT IDENTIFIER ::= {tmonXM 1}
tmonIdentManufacturer OBJECT-TYPE
    SYNTAX DisplayString
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION "The TMON/XM Unit manufacturer.""
    ::= {tmonIdent 1}
tmonIdentModel OBJECT-TYPE
    SYNTAX DisplayString
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION "The TMON/XM model designation.""
MIB stands for Management Information Base. A MIB file is a sort of "codebook" that is required to interpret traps sent from your SNMP devices. Your SNMP manager needs MIB files to properly handle incoming traps. For your system to function properly, it is important to have the correct MIB for your system. You can get this from the manufacturer of your SNMP devices.

The manufacturer of your device will supply you with a MIB file (usually a download from their website) that you'll load ("compile") into your SNMP manager (If you've ever installed a device driver on a PC, you understand this concept). Without the MIB for message translation, communication simply won't happen.

Read more about SNMP MIBs.

The Five Most Common SNMP MIB Problems - and How to Fix Them!

With the right know-how, you'll proactively avoid issues before they begin.

  1. Compile MIB To Your SNMP Manager
    Without the appropriate MIB, your SNMP manager will not be able to handle incoming traps from an SNMP device. Remember that MIB files are generally available from your device manufacturer. Go to their website or call their technical support. Any new MIBs should go into your SNMP manager.
    -Some device manufacturers will not provide MIBs for their devices. This is usually an attempt to force you to purchase more equipment. One good way to work around this issue is to use a device that accepts manual input of trap values, such as the T/Mon.
    -Be on the lookout for new software, firmware releases. These upgrades may require a MIB update for your master. Install upgrades in a timely manner to ensure that your gear functions properly at all times.

  2. Use Only Compatible MIBs
    The two most common MIB types are DOS MIBs and UNIX MIBs. DOS MIBs may not work with a UNIX SNMP manager, and vice versa. Check to be sure that you are using MIBs that are compatible with your manager.

  3. Collect Your Missing Reference MIBs
    Most main MIBs require additional reference (RFC) MIBs during compiling. If any of these RFC MIBs are missing, the main MIB will not compile properly. On the T/Mon LNX, an error message is added to the MIB Manager log that indicates which MIB files are missing. Error reporting on other SNMP managers will vary, but you can always get a list of required reference MIBs by reading the main MIB. Make sure that you have all RFC MIBs referenced by your main MIB and compile it again.

  4. Avoid Typos in the MIB
    Bad syntax in a MIB file can create errors when compiling. Computers won't understand the underlying concepts if your syntax is wrong. Exactly how much goes wrong will vary based upon the compiler that your are using. Although typos in the MIB can take many forms, one of the most common is the incorrectly escaped file comment. File comments in MIBs are offset from the rest of the file by double hyphens (--) and generally continue until the end of the line. An important exception is that comments can be ended by a second pair of hyphens on the same line. Any text on the same line after this second pair of hyphens will be parsed by the compiler as if it were normal MIB code, causing an error. Anything outside of the second double hyphen (--) on the same line is considered part of the MIB code during compiling. The compiler will not know how to handle it, and an error will be generated.

  5. Be Wary of Pre-compiled MIBs
    Using these kinds of MIBs is not always the best choice. MIBs that were compiled for a target platform other than your manager can create a range of potential problems. The MIB files you use should be text-readable before you compile them to your manager.

Troubleshoot SNMP MIBS Yourself.

With these five common MIB issues, you can easily Troubleshoot SNMP MIBs yourself. Keep in mind who you are buying your equipment from. Do they provide support? Do they require you to buy extra equipment to access the MIB files? By choosing a manufacturer that provides the MIB files and offers tech support, you will save time and money. Your mission critical gear relies on the comunication of your SNMP equipment. Make sure that you know all the necessary information to keep your network up and to protect your gear.

The T/MON LNX monitors all of your mission-critical gear.

The T/MON LNX Alarm Master Station

The T/Mon LNX Remote Alarm Monitoring System is a multiprotocol, multifunction network alarm manager designed as a single-platform solution for all alarm monitoring applications. T/Mon collects alarm data from lots of different SNMP equipment throughout many manufacturers and protocols. The flagship LNX platform includes a Web 3.0 browser interface (video) and a mobile web interface for smartphones. Use this master station to connect all your mission-critical SNMP gear.

Call DPS Telecom today at 1-800-693-0351

Get a Custom Application Diagram of Your Perfect-Fit Monitoring System

There is no other network on the planet that is exactly like yours. For that reason, you need to build a monitoring system that's the right fit for you.

"Buying more than you need" and "buying less than you need" are real risks. You also have to think about training, tech support, and upgrade availability.

Send me a quick online message about what you're trying to accomplish. I'll work with you to build a custom PDF application diagram that's a perfect fit for your network.