Skip to content
DeviceQuest DeviceQuest DeviceQuest Docs User Documentation

Documentation

SNMP MIBs

Browse the MIB library that translates SNMP OIDs into names and identifies devices, and upload, re-parse or delete vendor MIBs.

Overview

SNMP scans read numeric object identifiers (OIDs) from your network devices. The MIB library turns those OIDs into readable names and uses each device’s sysObjectID to recognise its vendor and model. DeviceQuest ships with a baseline set of standard and vendor MIBs, marked Built-in. Upload your own vendor MIBs to extend coverage to devices the baseline set does not describe.

Any signed-in user can browse the library. Uploading, re-parsing and deleting MIBs need the admin:manage permission. Open the page from Admin → SNMP MIBs in the sidebar.

Screen tour

  1. Status: filters the library by parse status: All, Parsed, Failed or Pending. Each option shows how many MIBs it holds.
  2. Source: filters by where the MIB came from: All, Built-in (shipped with DeviceQuest) or Uploaded (added by your team).
  3. Upload MIB: opens your file browser so you can add a MIB file to the library.
  4. Search file or module name…: finds MIBs whose file name or module name contains the text you type.
  5. Vendor — Enter: filters by vendor folder, for example cisco or arista. Type the vendor and press Enter.
  6. Column headers: click Name, Module, Vendor, Objects, Size, Source or Status to sort by that column. Click the same header again to reverse the order.
  7. Name: the MIB file name. Click it, or anywhere on the row, to open the detail panel.
  8. Status: Parsed, Failed or Pending. See Statuses.

Each row also shows the Module the file defines, the Vendor folder (standard for MIBs that are not vendor specific), the number of Objects it defines and its file Size. For a MIB that failed to parse, the first part of the parse error appears under the file name.

Below the table, the footer shows Showing 1–100 of N MIBs. Choose 25 per page, 50 per page or 100 per page, and use the arrows to move between pages.

When at least one MIB failed to parse, a notice above the table reads, for example, 1 MIB failed to parse — OIDs from it will not resolve. Click Review failed to show only the failed MIBs.

On narrow screens the column headers are replaced by a Sort menu with a direction button next to it.

Filter and search the library

  1. Under Status, click Parsed, Failed or Pending. Click All to show every status again.
  2. Under Source, click Built-in or Uploaded.
  3. Type part of a file or module name in Search file or module name…. The table updates as you type.
  4. Type a vendor folder name in Vendor — Enter and press Enter, or click outside the field.
  5. To remove every filter at once, click Clear filters in the toolbar. When no MIB matches, the table shows No MIBs match these filters with a Clear all filters button.

Sorting is kept when you clear the filters.

View MIB details

Click a MIB’s name to open its detail panel.

  1. MIB file: the file name of the MIB.
  2. Status banner: the parse status with a short summary, such as 282 objects indexed for a parsed MIB, OIDs from this file will not resolve for a failed one, or Awaiting parsing for a pending one.
  3. File details: Module, Vendor, Source, Objects, File size, Uploaded by (uploaded MIBs only), Created and Updated.
  4. SHA-256: the checksum of the file content. DeviceQuest uses it to detect duplicate uploads.
  5. Close detail panel: closes the panel. You can also press Esc or click outside the panel.

For a MIB that failed to parse, the panel also shows the full Parse error message from the parser, for example a missing import or a syntax error on a specific line.

Upload a MIB

  1. Click Upload MIB.
  2. In your file browser, choose a MIB file. The picker offers files with the extensions .mib, .my, .txt and .mi2.
  3. DeviceQuest stores the file and parses it straight away. While it works, the button reads Uploading….

You can also drag a MIB file from your desktop and drop it anywhere on the library. While you drag, the page shows Drop MIB to upload.

After the upload, a message tells you the result:

  • Uploaded “FILE” (module MODULE, N objects). The MIB parsed and its OIDs resolve from now on.
  • Stored “FILE” but it failed to parse: ERROR The file is in the library with the Failed status. This usually means it imports another MIB that is not in the library yet. Upload the missing MIB, then re-parse this one.
  • This MIB is already in the library (identical content). A file with exactly the same content exists, so nothing was added.

Upload rules:

  • One file per upload. A file can be up to 16 MB.
  • Empty files are rejected.
  • The file name is kept, without any folder path. Uploaded MIBs have no vendor folder, so they show as standard under Vendor.

Re-parse or delete a MIB

Each MIB in the library can be re-parsed or deleted from its detail panel. Re-parse a MIB that failed because one of its imports was missing, after you upload the missing MIB; DeviceQuest parses the stored file again and updates its status. Delete an uploaded MIB you no longer need or want to replace with a corrected version.

Fields

FieldDescriptionRules
NameThe MIB file name.Set from the uploaded file name.
ModuleThe MIB module the file defines, for example IF-MIB.Read from the file when it parses. Empty (—) when parsing failed.
VendorThe vendor folder of a built-in MIB, for example cisco.standard for standard MIBs and for uploaded MIBs.
ObjectsThe number of objects the file defines.Counted from the file content.
Size / File sizeThe size of the file.Up to 16 MB for uploads.
SourceBuilt-in or Uploaded.Set by DeviceQuest.
StatusThe parse status.See Statuses.
Parse errorThe parser’s message for a failed MIB.Shown for Failed MIBs only.
Uploaded byThe user who uploaded the MIB.Uploaded MIBs only.
Created, UpdatedWhen the MIB was added and last changed.Shown in your local time.
SHA-256The checksum of the file content.Unique: two MIBs with identical content cannot both be in the library.

Statuses

StatusMeaningNext possible status
PendingThe file is in the library but has not been parsed yet.Parsed, Failed
ParsedThe file loaded and its OIDs are usable for name translation and device identification.Failed
FailedThe parser rejected the file. Open the row to see the exact error. OIDs from the file do not resolve.Parsed

Keyboard shortcuts

KeyAction
↓ / ↑With focus on a MIB name in the table, move to the next or previous MIB.
Home / EndWith focus on a MIB name, move to the first or last MIB on the page.
← → ↑ ↓In the Status or Source filter, select the previous or next option.
EnterIn the Vendor — Enter field, apply the vendor filter.
EscClose the detail panel.