CISCO-OBMI-MIB

        The On-Board Management Interface (OBMI) provides an
out-of-band communications channel (in Cisco terms: 
a console port), that is capable of running on various
low-speed to high-speed satellite telemetry busses,
such as the m500 bus.
        
OBMI is similar to SNMP in principle and function, in 
that it allows 'getting' data from or 'setting' 
configurations in a device, however, OBMI is functional
regardless of the software state of the device.  It
must be so, because OBMI is the primary control mechanism
for a device operating in the harsh environment of space.
        
OBMI transports command messages that originate from the
ground to a device in space and transports telemetry 
messages that originate from that device in space to the
ground.
        
The OBMI application is divided into three conceptual layers:
1.  The OBMI application layer which concerns operating system
    subsystems and their associated command and telemetry
    messages.
2.  A FRAMING layer which formats the OBMI messages into
    frames that are suitable for transport over a specific
    spacecraft bus.
3.  The PHY (physical) layer which handles sending and 
    receiving the frames over the physical media.
        
Counts associated with the success or failure of these
various transport layers are reported by this MIB.
        
         GLOSSARY
        
command   :  data that goes from the ground to the device 
             in space
frame     :  OBMI messages are broken into frames to be
             sent by the physical bus or reassembled from
             the bus to be sent to the OBMI subsystem
m500      :  A particular space command/telemetry bus
message   :  fully assembled set of frames that make up
             commands or telemetry. The topmost OBMI 
             layer of the OBMI subsystem operates with
             messages
OBMI      :  On-board Management Interface
telemetry :  data that goes from the device in space to the
             ground
word      :  a collection of bits, sized for the particular
             bus
    
Source file
CISCO-OBMI-MIB
Last revised
Identity
ciscoObmiMIB
Base OID
1.3.6.1.4.1.9.9.698
Imported Objects
CISCO-SMI ciscoMgmt
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Gauge32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString TruthValue
Net-SNMP examples using the cisco 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 'CISCO-OBMI-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-OBMI-MIB::ciscoObmiMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-OBMI-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-OBMI-MIB::ciscoObmiMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (58)
.1.3.6.1.4.1.9.9.698
.1.3.6.1.4.1.9.9.698.0
.1.3.6.1.4.1.9.9.698.1
.1.3.6.1.4.1.9.9.698.1.2
.1.3.6.1.4.1.9.9.698.1.2.1
Unsigned32
.1.3.6.1.4.1.9.9.698.1.2.1.1
.1.3.6.1.4.1.9.9.698.1.2.1.10
.1.3.6.1.4.1.9.9.698.1.2.1.11
.1.3.6.1.4.1.9.9.698.1.2.1.12
.1.3.6.1.4.1.9.9.698.1.2.1.2
.1.3.6.1.4.1.9.9.698.1.2.1.3
.1.3.6.1.4.1.9.9.698.1.2.1.4
.1.3.6.1.4.1.9.9.698.1.2.1.5
.1.3.6.1.4.1.9.9.698.1.2.1.6
.1.3.6.1.4.1.9.9.698.1.2.1.7
.1.3.6.1.4.1.9.9.698.1.2.1.8
.1.3.6.1.4.1.9.9.698.1.2.1.9
.1.3.6.1.4.1.9.9.698.1.3
.1.3.6.1.4.1.9.9.698.1.3.1
Unsigned32
.1.3.6.1.4.1.9.9.698.1.3.1.1
.1.3.6.1.4.1.9.9.698.1.3.1.2
.1.3.6.1.4.1.9.9.698.1.3.1.3
.1.3.6.1.4.1.9.9.698.1.4
.1.3.6.1.4.1.9.9.698.1.4.1
.1.3.6.1.4.1.9.9.698.1.4.1.1
.1.3.6.1.4.1.9.9.698.1.4.1.10
.1.3.6.1.4.1.9.9.698.1.4.1.11
.1.3.6.1.4.1.9.9.698.1.4.1.12
.1.3.6.1.4.1.9.9.698.1.4.1.13
.1.3.6.1.4.1.9.9.698.1.4.1.14
.1.3.6.1.4.1.9.9.698.1.4.1.15
.1.3.6.1.4.1.9.9.698.1.4.1.16
.1.3.6.1.4.1.9.9.698.1.4.1.2
.1.3.6.1.4.1.9.9.698.1.4.1.3
.1.3.6.1.4.1.9.9.698.1.4.1.4
.1.3.6.1.4.1.9.9.698.1.4.1.5
.1.3.6.1.4.1.9.9.698.1.4.1.6
.1.3.6.1.4.1.9.9.698.1.4.1.7
.1.3.6.1.4.1.9.9.698.1.4.1.8
.1.3.6.1.4.1.9.9.698.1.4.1.9
.1.3.6.1.4.1.9.9.698.1.5
.1.3.6.1.4.1.9.9.698.1.5.1
.1.3.6.1.4.1.9.9.698.1.5.1.1
.1.3.6.1.4.1.9.9.698.1.5.1.10
.1.3.6.1.4.1.9.9.698.1.5.1.11
.1.3.6.1.4.1.9.9.698.1.5.1.12
.1.3.6.1.4.1.9.9.698.1.5.1.13
.1.3.6.1.4.1.9.9.698.1.5.1.2
Bits
.1.3.6.1.4.1.9.9.698.1.5.1.3
.1.3.6.1.4.1.9.9.698.1.5.1.4
.1.3.6.1.4.1.9.9.698.1.5.1.5
.1.3.6.1.4.1.9.9.698.1.5.1.6
.1.3.6.1.4.1.9.9.698.1.5.1.7
.1.3.6.1.4.1.9.9.698.1.5.1.8
.1.3.6.1.4.1.9.9.698.1.5.1.9
.1.3.6.1.4.1.9.9.698.2
.1.3.6.1.4.1.9.9.698.2.1
.1.3.6.1.4.1.9.9.698.2.2
Dependencies (4) 4 direct 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. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. CISCO-OBMI-MIBciscoselected
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.698.2.1.1
This is a default module-compliance
containing default object groups.
Required groups