"Solve All Your SNMP MIB Problems With These 5 Expert Tactics..."

Eliminate Hours of Frustrating Troubleshooting...

Is your monitoring disrupted by SNMP MIB problems? Do you know enough about SNMP MIBS to troubleshoot your own equipment? You may have already sacrificed some of your valuable time and money dealing with SNMP problems, and you're still unclear on what MIBs are. Maybe you're ready now to arm yourself with some troubleshooting skills.

What if you could avoid (and even prevent) problems with SNMP MIBs? Imagine how much easier and smoother your operations would flow if you had the answers to the most common SNMP MIB problems? You'd know exactly what to do to solve them quickly.

What Is An SNMP MIB File?

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.

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

With the right know-how, you'll avoid SNMP MIBs disasters even before they start! Eliminate hours of frustrating SNMP troubleshooting from your busy schedule.

Answers To The 5 Most Common SNMP MIBs Problems:

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 NOC.
• Be on the lookout for new software, firmware releases. These upgrades may require a MIB update for your master.
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 NOC, 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. 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 and 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.

Call DPS Telecom today at 1-800-693-0351 or click here for the SNMP Troubleshooting Guide.

Mac Smith

What else do you need to know? Send me your question right now:

My question is:

Where should I send your answer?
Name:		Company Name:
Email:		Phone Number:
State:	**Outside United States Alabama Alaska Arizona Arkansas California Colorado Connecticut Delaware District of Columbia Florida Georgia Hawaii Idaho Illinois Indiana Iowa Kansas Kentucky Louisiana Maine Maryland Massachusetts Michigan Minnesota Mississippi Missouri Montana Nebraska Nevada New Hampshire New Jersey New Mexico New York North Carolina North Dakota Ohio Oklahoma Oregon Pennsylvania Rhode Island South Carolina South Dakota Tennessee Texas Utah Vermont Virginia Washington West Virginia Wisconsin Wyoming