CISCO-OBMI-MIB: View SNMP OID List / Download 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

This 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.

Each entry represents a row in cObmiTransportTable and corresponds to the statistics for a particular transport bus.

This object uniquely indentifies a particular OBMI transport bus.

This object indicates the name of the OBMI transport bus.

This object indicates the total number of commands received by the OBMI subsystem.

This object indicates the total number of commands successfully processed by the OBMI subsystem.

This 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'.

This 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'.

This object indicates the total number of commands that the OBMI subsystem interpreted as not fully conforming to the formatting requirements and therefore considered invalid.

This object indicates the total number of commands that are awaiting processing by the OBMI subsystem.

This object indicates the total number of commands that the OBMI subsystem did not recognize and therefore dropped.

This object indicates the total count of telemetry messages that were sent by the OBMI subsystem.

This 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.

This object indicates the total number of of telemetry messages waiting to be sent to the ground from the OBMI subsystem.

This 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.

Each entry represents a row in cObmiTransportHearBeatTable and identifies heartbeat- related statistics.

This object, along with cObmiBusID uniquely identifies heartbeat-related statistics.

This object indicates the total number of hearbeats sent.

This object indicates the total number of heartbeats waiting in the queue ready to be sent.

This 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.

Each entry represents an entry in the cObmiM500FramingTable and corresponds to the statistics associated with the framing for an 'm500' bus used to transport OBMI.

This object indicates the total number of m500 frames received.

This object indicates the total number of m500 bytes received.

This object indicates the total number of received m500 frames aborted.

This object indicates the total number of m500 echo frames received.

This object indicates the total number of m500 reset frames received.

This object indicates the total number of errored m500 transport frames received.

This object indicates the total number of m500 frames with unknown operation codes received.

This object indicates the total number of m500 frames transmitted.

This object indicates the total number of m500 bytes transmitted.

This object indicates the total number of aborted m500 frames transmitted.

This object indicates the total number of m500 echo frames transmitted.

This object indicates the total number of m500 transport frames transmitted with error.

This object indicates the total number of control queue overruns transmitted.

This object indicates the total number of underruns transmitted from queue number 0.

This object indicates the total number of underruns transmitted from queue number 1.

This object indicates the total number of transmit control queue overruns.

This 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.

Each 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.

This 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.

This 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.

This object indicates which bus was last active: a : m500 bus A was last active b : m500 bus B was last active Bits: 'a': 0, 'b': 1.

This object indicates the total number of m500 command words received.

This object indicates the total number of m500 telemetry words sent.

This object indicates the total number of m500 telemetry words with errors.

This object indicates the total number of m500 command words with errors.

This object indicates the total number of m500 command words that were overwritten.

This 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.

This 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.

This 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.

This object indicates whether or not there was a timeout in receiving the LAST command word: True : Timeout occurred. False : Timeout did NOT occur.

This object indicates whether or not the last command received was overwritten: True : Command received was overwritten. False : Command received was NOT overwritten.

This is a default module-compliance containing default object groups.

This is the list of objects required for OBMI.

This is the list of objects required for m500.