CISCO-OBMI-MIB
AI MIB Summary
The CISCO-OBMI-MIB monitors the operational status and transport layer performance of the On-Board Management Interface (OBMI) on Cisco space-rated hardware, specifically tracking command and telemetry message framing and physical layer transmission counts over satellite telemetry buses like the m500. This module provides critical visibility into the out-of-band management channel's success and failure metrics, enabling ground control to verify device connectivity and data integrity independent of the spacecraft's primary software state.
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
Main OID:
ciscoObmiMIB.1.3.6.1.4.1.9.9.698
58
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
58 total| Object Name |
|---|
ciscoObmiMIBThe 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 MODULE-IDENTITY .1.3.6.1.4.1.9.9.698 |
ciscoObmiMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.698.0 |
ciscoObmiMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.698.1 |
cObmiTransportTableThis table provides the statistics, in the form
of counters associated with the transport of
OBMI over one or more busses. At startup, all entries in
this table are set up by the OBMI subsystem. SEQUENCE OF CObmiTransportEntry .1.3.6.1.4.1.9.9.698.1.2 |
cObmiTransportEntryEach entry represents a row in cObmiTransportTable
and corresponds to the statistics for a particular
transport bus. CObmiTransportEntry .1.3.6.1.4.1.9.9.698.1.2.1 |
cObmiBusIDThis object uniquely indentifies a particular
OBMI transport bus. Unsigned32 .1.3.6.1.4.1.9.9.698.1.2.1.1 |
cObmiBusNameThis object indicates the name of the OBMI transport bus.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.2.1.2 |
cObmiCommandRxThis object indicates the total number of commands
received by the OBMI subsystem.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.3 |
cObmiCommandProcessedTotalThis object indicates the total number of commands
successfully processed by the OBMI subsystem.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.4 |
cObmiCommandGetsThis object indicates the total number of 'get' commands
processed by the OBMI subsystem. A 'get'
command requests information from the device that
the OBMI subsystem resides on and is different
from an SNMP 'get'.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.5 |
cObmiCommandSetsThis object indicates the total number of 'set' commands
processed by the OBMI subsystem. A 'set'
command changes information ON the device that the
OBMI subsystem resides on and is different from
and SNMP 'set'.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.6 |
cObmiCommandProcessedInvalidThis object indicates the total number of commands that
the OBMI subsystem interpreted as not fully conforming to the
formatting requirements and therefore considered invalid.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.7 |
cObmiCommandPendingThis object indicates the total number of commands that
are awaiting processing by the OBMI subsystem.ro Gauge32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.8 |
cObmiCommandDroppedThis object indicates the total number of commands that
the OBMI subsystem did not recognize and therefore
dropped.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.9 |
cObmiTelemetrySentThis object indicates the total count of telemetry messages
that were sent by the OBMI subsystem.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.10 |
cObmiTelemetryDemandSentThis object indicates the total count of telemetry messages
that were sent by the OBMI subsystem, but only upon
commanded 'gets' to the OBMI subsystem. This number excludes
telemetry messages that were automatically sent by heartbeats.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.11 |
cObmiTelemetryPendingThis object indicates the total number of of telemetry messages
waiting to be sent to the ground from the OBMI subsystem.ro Gauge32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.2.1.12 |
cObmiTransportHeartBeatTableThis table lists the number of heartbeats sent and
the number pending by the OBMI subsystem by port
number for a particular bus. At startup, all entries in this
table are set up by the OBMI subsystem. SEQUENCE OF CObmiTransportHeartBeatEntry .1.3.6.1.4.1.9.9.698.1.3 |
cObmiTransportHeartBeatEntryEach entry represents a row in
cObmiTransportHearBeatTable and identifies heartbeat-
related statistics. CObmiTransportHeartBeatEntry .1.3.6.1.4.1.9.9.698.1.3.1 |
cObmiHeartBeatPortThis object, along with cObmiBusID uniquely
identifies heartbeat-related statistics. Unsigned32 .1.3.6.1.4.1.9.9.698.1.3.1.1 |
cObmiHeartBeatSentThis object indicates the total number of hearbeats sent.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.3.1.2 |
cObmiHeartBeatPendingThis object indicates the total number of heartbeats waiting
in the queue ready to be sent.ro Gauge32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.3.1.3 |
cObmiM500FramingTableThis table lists the statistics associated with the
'framing-layer' of logical organization for the
m500 bus used to transport OBMI. The frame size for
m500 is 32 bits. At startup, all entries in this table are
set up by the OBMI subsystem. SEQUENCE OF CObmiM500FramingEntry .1.3.6.1.4.1.9.9.698.1.4 |
cObmiM500FramingEntryEach entry represents an entry in the
cObmiM500FramingTable and corresponds to the
statistics associated with the framing for an
'm500' bus used to transport OBMI. CObmiM500FramingEntry .1.3.6.1.4.1.9.9.698.1.4.1 |
cObmiM500RxFramesThis object indicates the total number of m500
frames received.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.1 |
cObmiM500RxBytesThis object indicates the total number of m500
bytes received.ro Counter32 UNITS "Bytes" .1.3.6.1.4.1.9.9.698.1.4.1.2 |
cObmiM500RxAbortFramesThis object indicates the total number of
received m500 frames aborted.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.3 |
cObmiM500RxEchoFramesThis object indicates the total number of m500
echo frames received.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.4 |
cObmiM500RxResetFramesThis object indicates the total number of m500
reset frames received.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.5 |
cObmiM500RxTransportErrFramesThis object indicates the total number of errored
m500 transport frames received.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.6 |
cObmiM500RxUnknownOpFramesThis object indicates the total number of m500
frames with unknown operation codes received.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.7 |
cObmiM500TxFramesThis object indicates the total number of
m500 frames transmitted.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.8 |
cObmiM500TxBytesThis object indicates the total number of
m500 bytes transmitted.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.9 |
cObmiM500TxAbortFramesThis object indicates the total number of aborted
m500 frames transmitted.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.10 |
cObmiM500TxEchoFramesThis object indicates the total number of m500
echo frames transmitted.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.11 |
cObmiM500TxTransportErrFramesThis object indicates the total number of m500 transport
frames transmitted with error.ro Counter32 UNITS "Frames" .1.3.6.1.4.1.9.9.698.1.4.1.12 |
cObmiM500RxQOverRunThis object indicates the total number of control queue
overruns transmitted.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.4.1.13 |
cObmiM500TxQ0UnderRunThis object indicates the total number of underruns
transmitted from queue number 0.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.4.1.14 |
cObmiM500TxQ1UnderRunThis object indicates the total number of underruns
transmitted from queue number 1.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.4.1.15 |
cObmiM500TxCtlQOverRunThis object indicates the total number of transmit control
queue overruns.ro Counter32 UNITS "Messages" .1.3.6.1.4.1.9.9.698.1.4.1.16 |
cObmiM500PhyTableThis table lists the statistics associated with the
'physical-layer' of logical organization for the
m500 bus used to transport OBMI. At startup, all entries
in this table are set up by the OBMI subsystem. SEQUENCE OF CObmiM500PhyEntry .1.3.6.1.4.1.9.9.698.1.5 |
cObmiM500PhyEntryEach entry represents an entry in the
cObmiM500PhyTable and corresponds to the statistics
associated with the physical layer for an 'm500' bus
used to transport OBMI. The size of a 'Word' for
the m500 bus is 32-bits. CObmiM500PhyEntry .1.3.6.1.4.1.9.9.698.1.5.1 |
cObmiM500BusALOSThis object indicates whether or not there is a
loss of signal on m500 bus A.
True : Loss of Signal on m500 bus A.
False : No Loss of Signal on m500 bus A.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.1 |
cObmiM500BusBLOSThis object indicates whether or not there is a
loss of signal on m500 bus B.
True : Loss of Signal on m500 bus B.
False : No Loss of Signal on m500 bus B.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.2 |
cObmiM500LastActiveBusThis object indicates which bus was last active:
a : m500 bus A was last active
b : m500 bus B was last activero Bits .1.3.6.1.4.1.9.9.698.1.5.1.3 |
cObmiM500CommandsRcvdThis object indicates the total number of m500 command
words received.ro Counter32 UNITS "Words" .1.3.6.1.4.1.9.9.698.1.5.1.4 |
cObmiM500TelemetrySentThis object indicates the total number of m500 telemetry
words sent.ro Counter32 UNITS "Words" .1.3.6.1.4.1.9.9.698.1.5.1.5 |
cObmiM500TelemetryErrsThis object indicates the total number of m500 telemetry
words with errors.ro Counter32 UNITS "Words" .1.3.6.1.4.1.9.9.698.1.5.1.6 |
cObmiM500CommandErrsThis object indicates the total number of m500 command
words with errors.ro Counter32 UNITS "Words" .1.3.6.1.4.1.9.9.698.1.5.1.7 |
cObmiM500CommandOverWrtsThis object indicates the total number of m500 command
words that were overwritten.ro Counter32 UNITS "Words" .1.3.6.1.4.1.9.9.698.1.5.1.8 |
cObmiM500HWParityErrThis object indicates whether or not there was
a hardwired parity error in the LAST command word
received.
True : Parity error occurred.
False : No parity error occurred.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.9 |
cObmiM500TelemetryReqParityErrThis object indicates whether or not there was
a parity error in the LAST telemetry request
word received.
True : Parity error occurred.
False : No parity error occurred.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.10 |
cObmiM500CommandParityErrThis object indicates whether or not there was
a parity error in the LAST command word
received.
True : Parity error occurred.
False : No parity error occurred.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.11 |
cObmiM500CommandTimeoutThis object indicates whether or not there was
a timeout in receiving the LAST command word:
True : Timeout occurred.
False : Timeout did NOT occur.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.12 |
cObmiM500CommandOverWrtThis object indicates whether or not the
last command received was overwritten:
True : Command received was overwritten.
False : Command received was NOT overwritten.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.698.1.5.1.13 |
ciscoObmiMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.698.2 |
ciscoObmiMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.698.2.1 |
ciscoObmiMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.698.2.2 |