Total Control MP/16, Руководство оператора

Страница: 44 / 182

3-8 Using Total Control MIBs
Table 3-1. MP/16 Entity Index
Slot Entity Entity Index
1 Modems 1–8 1001–1008
2 Modems 9–16 2001–2008
3 Management (NMC) 3000
The indexes to the entity table are the same as the indexes to other
MIB tables for a given entity. As an example, if a modem entity
has an entity index of 2001, then that same entity number is used to
index the modem MIB tables to GET and SET objects in the modem
MIB for that modem. See the section on the chassis MIB for further
details.
NOTE:
If the value of uchasEntityOperStatus is ever failed for
one or more entities, the STATUS light on the bottom row of
LEDS turns red.
The Config Group
Most of the MIB objects in this group are self explanatory. The
exceptions would be uchasFrontPanelLedStates and
uchasFrontPanelLedColor. In general, these objects are bitmaps.
The current design handles up to 12 LEDs per module. Each LED's
information is encoded in a nibble (4 bits); therefore, each module
takes up 6 bytes out of the octet string. The total length of the octet
string is 102 bytes, although the MP/16 only uses the first 18 bytes
for slots 1–3. It is the responsibility of the management station to
know how many LEDs each module has on the front panel of the
MP/16. The MIB does not identify how many of the 12 nibbles for
each module carry useful information.
In addition to LED state and color, a few of the bits in these objects
are used for additional information. The bit definition for these
three objects is shown below.