BIANCA-BRICK-MIB

Monitored by Observium
        MIB module for vendor specific box definitions.
Note: bibo stands for BinTec box stemming from the times where
      the company was still called BinTec.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Device identity Polling
Explore Observium network monitoring
Source file
BIANCA-BRICK-MIB
Last revised
Identity
biboMIB
Base OID
0.250
Imported Objects
bibo bintec Date HexValue sys
RFC-1215 TRAP-TYPE (no object page)
SNMPv2-MIB sysDescr sysName
SNMPv2-SMI Counter32 Counter64 enterprises Gauge32 Integer32 IpAddress mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32
SNMPv2-TC DisplayString TimeStamp TruthValue
Net-SNMP examples using the bintec MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'BIANCA-BRICK-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'BIANCA-BRICK-MIB::biboMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'BIANCA-BRICK-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'BIANCA-BRICK-MIB::biboMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (1)
.0.250
Dependencies (5) 4 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. RFC-1215rfc
  2. SNMPv2-SMIrfc
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. SNMPv2-MIBrfc
  6. BIANCA-BRICK-MIBbintecselected