Custom MIBs and vendor profiles

What it is

A vendor profile is CreaRack’s knowledge card for one manufacturer. It tells the platform how to recognize that vendor’s gear (SNMP sysDescr and sysObjectID patterns, web interface banners), which default SNMP communities to try, which SSH platform and commands to use, and — most importantly here — which MIB modules and OID lists Deep Discovery polls for extended sensors (CPU, memory, VLANs, temperature, wireless data).

When the wizard’s Deep Discovery option is on, CreaRack uses each vendor’s MIBs to pull this extended SNMP data. If your hardware exposes sensors CreaRack does not know out of the box, that manufacturer’s MIB file needs to be uploaded and the right OIDs picked — Deep Discovery then collects them for every device of that vendor.

The vendor catalog is shared across every organization on the platform, so uploading MIBs, deleting them, and applying OIDs are handled by the CreaRack team, not by your organization’s admins. This keeps one organization’s custom upload from ever affecting another’s devices.

What your organization’s admins can do

Organization admins can still view the vendor catalog: open Vendor MIBs next to the Deep Discovery toggle in the Auto-Provision wizard (or Manage MIBs on a discovered device) to see which MIB modules are loaded for each vendor and which OIDs are active. The Upload MIBs, delete and OID-selection actions are not shown to organization admins — CreaRack’s platform team performs them centrally, using the same discovery/probe workflow described below.

If your hardware needs a MIB CreaRack does not have yet, contact the CreaRack team with the manufacturer’s MIB file (.mib, .my, .txt, .asn1, .asn) and, if you know it, which sensors you need (CPU, memory, VLANs, temperature…).

How the MIB catalog is built (for reference)

This is the workflow the CreaRack team runs when adding or extending a vendor profile — useful background if you are reporting a missing sensor.

Upload. A MIB file is compiled and its OIDs extracted. Status per file:

• Compiled — the MIB compiled cleanly.
• Source — compilation failed, but OIDs were still extracted from the ASN.1 text. Usually good enough.
• Failed — nothing usable was found.

Pick OIDs. After uploading a single file, a selector table opens with each OID’s Name, OID, Type (get or walk), Syntax, and a Value column.

1. Choose a Category: custom, hardware, wireless, cpu, memory, vlans, or environment. The category controls where the data appears in the device’s Deep Discovery results.
2. Probe Device tests all OIDs against a real device through a Local Agent on that network. Responding OIDs light up with their live value; the rest fade out.
3. Select Responding keeps only the OIDs that answered.

On a long list, type in the Filter OIDs box (name or OID, not case sensitive) to hide non-matching rows; a counter shows “N of M OIDs”. Filtering only hides rows: OIDs you ticked and then hid stay ticked, and Select All ticks or unticks only the rows you can see. 4. Apply Selected adds them to the vendor profile. The next Deep Discovery run for any organization uses them.

The limit is 200 OIDs per vendor. Enterprise MIBs often define thousands, so responding OIDs are probed first and only what responds is applied.

Deleting a custom MIB also removes the OIDs it contributed from the vendor profile.

CreaRack also ships an AI-powered MIB assistant that classifies extracted OIDs into monitoring and discovery categories and proposes a ready-made mapping. It is an internal, admin-level API feature, without its own screen.

Troubleshooting

• I don’t see “Upload MIBs” or “Manage MIBs” actions — that is expected. The manufacturer catalog is managed by the CreaRack team for the whole platform; your organization’s admins can view it but not change it. Contact CreaRack to add or update a vendor’s MIBs.
• “Could not find ‘MODULE DEFINITIONS ::= BEGIN’” — the file is not a valid MIB. Export the raw ASN.1 MIB from the vendor’s support site, not a PDF or spreadsheet.
• 0 OIDs responded during a probe — check the device IP and its SNMP community. When probing a discovered device, the Agent uses the community stored for that device’s profile.
• “Missing dependency: X. Upload it first.” — the MIB imports another module CreaRack does not have yet. Compilation uses only local sources (uploaded files, the vendor catalog and the standard MIBs bundled with the platform); it never downloads from the internet.
• Deep Discovery still missing data — make sure the relevant OIDs were applied to the vendor profile (uploading alone is not enough) and re-run the scan. See [[crearack—wireless—deep-discovery-troubleshooting]].

Related

• [[crearack—network—auto-provision-wizard]] — where Deep Discovery and Vendor MIBs live
• [[crearack—wireless—deep-discovery-troubleshooting]] — when extended data does not show up
• [[crearack—network—scripts-red]] — automate SSH commands on the devices you discover
• [[crearack—terminal—que-es-terminal]] — the Terminal hub and the Local Agent

Véase también

• [[crearack—network—auto-provision-wizard]]
• [[crearack—network—scripts-red]]
• [[crearack—wireless—deep-discovery-troubleshooting]]
• [[crearack—terminal—que-es-terminal]]