DPS Telecom's SNMP MIB Library

Need a SNMP MIB file? View our extensive library by vendor. You can view it by device type below. Download your SNMP MIB file today!

Expand DPS MIBs

Expand KDA (grp.1; sub.1)
Expand NetDog v1 (grp.1; sub.2)
Expand NetDog v2 (grp.1; sub.3)
Expand NetGuardian 216 (grp.1; sub.4)
Expand NetGuardian 216T v1 (grp.1; sub.5)
Expand NetGuardian 216T v2 (grp.1; sub.6)
Expand NetGuardian 480 (grp.1; sub.7)
Expand NetGuardian 216F v1 (grp.1; sub.8)
Expand NetGuardian 216F v2 (grp.1; sub.9)
Expand NetGuardian G2 v1 (grp.1; sub.10)
Expand NetGuardian G2 v2 (grp.1; sub.11)
Expand NetGuardian G4 v1 (grp.1; sub.12)
Expand NetGuardian G4 v2 (grp.1; sub.13)
Expand NetGuardian G5 v1 (grp.1; sub.14)
Expand NetGuardian G5 v2 / v3 (grp.1; sub.15)
Expand NetGuardian LT (grp.1; sub.16)
Expand NetMediator v1 (grp.1; sub.17)
Expand NetMediator v2 (grp.1; sub.18)
Expand TempDefender (grp.1; sub.19)
Expand TMon (grp.1; sub.20)
Expand Miscellenous (grp.1; sub.21)

Expand Argus MIBs

Expand Cisco 7609 (grp.2; sub.1)
Expand Cisco 15454 (grp.2; sub.2)
Expand Cisco 3560 (grp.2; sub.3)
Expand Miscelleneous (grp.2; sub.4)

Expand Tripplite MIBs

Tripplite SNMP MIBs

Expand Symmetricom MIBs

Symmetricon SNMP MIBs

Expand RoomAlert MIBs

RoomAlert SNMP MIBs

Expand Proteus MIBs

Proteus SNMP MIBs
Expand Miscellenous (grp.11; sub.1)

Expand Geist MIBs

Expand Miscellenous (grp.18; sub.1)

Expand Dell PowerConnect MIBs

Dell PowerConnect SNMP MIBs

Expand Bird Broadband Power Monitor MIBs

Bird Broadband Power Monitor SNMP MIbs
Expand Miscellenous (grp.24; sub.1)

What is a MIB file?

The MIB lists the unique object identifier (OID) of each managed element in an SNMP network. Your SNMP manager can't monitor your devices unless it has compiled their MIB files. The MIB is also a guide to the capabilities of your SNMP devices. For example, if your device's MIB lists OIDs for Traps but not for GetResponse messages, you know it will report alarms, but will not respond to alarm polls. Learning to read MIBs is difficult, but it's worth the trouble.

When an SNMP manager wants to know the value of an object/characteristic, such as the state of an alarm point, the system name, or the element uptime, it will assemble a GET packet that includes the OID for each object/characteristic of interest. The element receives the request and looks up each OID in its code book (MIB). If the OID is found (the object is managed by the element), a response packet is assembled and sent with the current value of the object / characteristic included. If the OID is not found, a special error response is sent that identifies the unmanaged object.

When an element sends a Trap packet, it can include OID and value information (bindings) to clarify the event. DPS remote units send a comprehensive set of bindings with each Trap to maintain traditional telemetry event visibility. Well-designed SNMP managers can use the bindings to correlate and manage the events. SNMP managers will also generally display the readable labels to facilitate user understanding and decision-making.

Each snmp element manages specific objects with each object having specific characteristics. Each object/characteristic has a unique object identifier (OID) consisting of numbers separated by decimal points (e.g., These object identifiers naturally form a tree as shown in the below illustration. The MIB associates each OID with a readable label (e.g., dpsRTUAState) and various other parameters related to the object. The MIB then serves as a data dictionary or codebook that is used to assemble and interpret SNMP messages.

What is an OID?

You can think of an OID as an address used in SNMP messages to identify devices and their statuses - acting both as the "What is it?" as well as the "Where did it come from?" Want to know the temperature reading coming from a sensor at your mountaintop remote facility? There's an OID for that.

SNMP Object Identifiers (OIDs) point to network objects stored in a database called the Management Information Base, often referred to as the "MIB". A MIB holds the structure of the network alarms being monitored (like a map of the "city"), and it uses the OIDs to keep track of the individual components (like the address to a house or other location). In this example, an SNMP OID is like the address the fire truck would drive to if the fire alarm sounded. What if a fire broke out at your house, and you called the fire department with GPS coordinates (representing the Object ID or OID)? The fire department would have to look that up in its MIB to determine the correct street address.

In telecom, SNMP OIDs describe specific locations in the network. The OID allows the MIB to translate the location of the event into a status description for your network technicians.

Demystifying the MIB by Marshall DenHartog

Understanding MIBs and how they describe SNMP telemetry messaging is critical to maximize your alarm system's capabilities.

One customer recently asked us about monitoring a new device, which was not in the library of SNMP MIBs for their system. They asked "can I reprogram the T/MonLNX to include this new device?" Fortunately, the TMonLNX can integrate SNMP telemetry without needing to load or compile a MIB file or files. For those with T/MonLNX montioring systems, the MIB files can be a helpful reference when deciding how to monitor a new element in your network.

For those with older SNMP Managers that require MIBs to be loaded in order to integrate SNMP messages from new network elements, MIB files are absolutely crtical to understand. In some cases, you may even decide to edit them to improve the messages for your SNMP Manager presentation. This report will help you understand why you absolutely need to be able to work with MIB files when you are using an older SNMP Manager.

In any case, you will learn the essentials of SNMP MIB files and will probably agree that this white paper is a must-read for anyone who works with SNMP.

Learn the SNMP Management Information Base:

Download White Paper

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.

Get a Custom Diagram

Make an Informed Decision

Your network isn't off-the-shelf.

Your monitoring system shouldn't be, either.

Customized monitoring application drawing

We'll walk you through this with a customized monitoring diagram.

Just tell us what you're trying to accomplish with remote monitoring.

Get a Custom Diagram