Specifications

index label data remarks
2 A2
2.1 B21 3.4 5 bytes, ASCII, base-10, decimal point allowed
2.2 C22
2.2.1 D221 PRR 3 bytes, ASCII, alphanumeric
2.2.2 E222 7
2 bytes, ASCII, base-10 integer
Figure 1: A MIB fragment, provided as an example only.
MIB labels must consist only of letters (case is significant), integer numbers, and the underscore
character. Spaces are not allowed. The length must be less than or equal to 40 characters.
Data referenced by MIB entries need not be ASCII, and can be raw binary. If raw binary, then
the subsystem ICD must specify whether this is big- or little-endian. An example of the use of raw
binary would be to represent the coefficients for a digital filter. The filter can be represented as a
MIB branch where each entry is the raw bit values for one coefficient, or the entire filter can be repre-
sented as a single entry consisting of all coefficients concatenated into a contiguous sequence of bits.
Each subsystem communicating with MCS using this ICD must specify a MIB as part of a
subsystem-specific ICD. This MIB consists of MCS-required MIB entries, plus additional MIB en-
tries which are subsystem-specific. The MCS-required MIB entries are specified below.
1. MCS-RESERVED
1.1. SUMMARY [7 bytes, ASCII/Alphanumeric]. Summary state of subsystem. Valid values
are as follows:
∗ NORMAL
∗ WARNING (issue(s) found, but still fully operational)
∗ ERROR (problems found which limit or prevent proper operation)
∗ BOOTING (initializing system; not yet fully operational)
∗ SHUTDWN (shutting down system; not ready for operation)
1.2. INFO [maximum 256 bytes, ASCII]. When MIB entry 1.1 is WARNING or ERROR, this
entry should begin with a list of MIB lab els, separated by single spaces, and terminated
by the character “!” (exclaimation mark). The MIB labels should be those containing
values indicating the problem condition. A human-readable text string which further
explains WARNING and ERROR values may be included following the character “!”.
Any unused bytes at the end of the INFO string should be spaces. Use of this MIB entry
when 1.1 is not WARNING or ERROR is subsystem-specific.
1.3. LASTLOG [maximum 256 bytes, ASCII]. Last internal log message. Human-readable
text string, with format specified in the subsystem-specific ICD. A timestamp of some
form should be included near the beginning of the string. Any unused bytes at the end
of the string should be spaces.
1.4. SUBSYSTEM [3 bytes, ASCII/Alphanumeric]. 3 character string identifying the subsys-
tem; e.g., “DP ”, ”ASP”. All strings beginnning with the characters “MC” are reserved.
Other strings are assigned by the LWA Systems Engineer.
3
1.5. SERIALNO [maximum 5 bytes, ASCII]. A string identifying the specific subsystem hard-
ware “serial number”. This string is assigned by the subsystem manufacturer in coordi-
nation with the LWA Systems Engineer.
3
One possible use of this entry is to facilitate subsystem discovery; e.g., MCS can send a RPT command message
to “ALL” requesting MIB entry 1.4, and see who responds.
3