Crystal Vision
VisionWeb
Object Identifiers (OID)
For each variable to be monitored there is an object identifier or OID which can be distinguished
from any other OID within the MIB tree by a unique number sequence coded within the MIB. As
an example, from the FrameMon MIB (see tree below), the front panel status variable
isTempOK
is accessed by the OID
1.3.6.1.4.28681.1.2.1.150.1.4
. The OID will then be accompanied by a
value to indicate its status, in this case, 1=NO, 2=YES. Any status change will cause the
transmitting of a trap to the SNMP manager.
The following grab from a MIB Browser shows the FrameMon MIB tree with its identifying number
sequences:
Partial
tree of FrameMon MIB showing identifiers
The frame variables monitored by the FrameMon MIB are:
Name
Function
Syntax
Value
Slot
Frame’s virtual slot number
INTEGER
0..31
1.1...2.16
isTempOk
Frame temperature OK?
INTEGER
1=NO, 2=TRUE
isPSUFanOk
Frame’s PSU fan OK?
INTEGER
1=NO, 2=TRUE
isFrontFanOk
Frame’s front panel fan
OK?
INTEGER
1=NO, 2=TRUE
isDoor Closed
Frame’s front panel closed?
INTEGER
1=NO, 2=TRUE
detectedFrameType Type of Indigo frame
INTEGER
0=Indigo 1SE, 1=Indigo DTSE,
2=Indigo 4SE, 3=Indigo 2SE,
4=Indigo 1AE, 5=Indigo DTAE,
7=Indigo 2AE
temperature
Frame temperature
INTEGER
0..127
0...1...2...127
configNumPsus
No. of PSUs fitted
INTEGER
Number of PSUs e.g. 1, 2 etc.
UpperPsuState
Condition of upper PSU
INTEGER
0=OK, 1=Alarm, 2=Not present,
3=Configuration error
LowerPsuState
Condition of lower PSU
INTEGER
0=OK, 1=Alarm, 2=Not present,
3=Configuration error
Indigo 2AE and 2SE User Manual R1.17
33
27 February 2020
