OpManager

Hi,



I am trying to read the data from Opmanager, but Opmanager seem to recognize Serverscheck as "unknown". Because of this I can not assign a monitor.



Anyone have any ideas ?

We are not familiar with Opmanager but like with any monitoring tool you would need to create a SNMP check and then use the correct OID that you wish to monitor of the sensor.

Hi, it seems I am on the right track at least.



What are the OIDs for the sensors (to read humidity and int/ext temperature data) ?

You can get those from a MIB Browser - see page 18 of the user manual



.1.3.6.1.4.1.17095.3.2.0 - built-in temperature sensor

.1.3.6.1.4.1.17095.3.6.0 - external temperature probe

.1.3.6.1.4.1.17095.3.10.0 - external humidity probe

When I try to load the sensorgateway.mib into the OpManager system it is giving a generic message:





Error parsing MIB:sensorgateway.mib

Exception while loading MIB:Could not parse the file C:/PROGRA~1/MANAGE~1/OPMANA~1/./mibs/1sensorgateway.mib. Couldn't resolve these TC constructs : { IP_ADDRESS }

Check with Opmanager for error messages on their system

OK. OpManager modified the original sensorgateway.mib file and it seems to be working now.



For future use, I can send the file (or copy the below text to txt file and rename it to opmsensgw.mib





-- SensorGateway control MIB.

--

-- Author Date Comment

-- ==================================================================

--



Serverscheck DEFINITIONS ::= BEGIN



IMPORTS

enterprises, IpAddress, Gauge, TimeTicks FROM RFC1155-SMI

DisplayString FROM RFC1213-MIB

OBJECT-TYPE FROM RFC-1212

TRAP-TYPE FROM RFC-1215;



serverscheck OBJECT IDENTIFIER ::= { enterprises 17095 }



product OBJECT IDENTIFIER ::= { serverscheck 1 }

setup OBJECT IDENTIFIER ::= { serverscheck 2 }

control OBJECT IDENTIFIER ::= { serverscheck 3 }



productname OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Name of product. e.g. SensorGateway etc."

::= { product 1 }





productversion OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Version of product. e.g. 1.0 etc"

::= { product 2 }



productdate OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Build date of product. e.g. Apr 2010 etc"

::= { product 3 }



productusername OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"User give name of product. e.g. ABCD etc"

::= { product 4 }



productuserloc OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Usage loaction of product. e.g. Data center etc"

::= { product 5 }



productnetip OBJECT-TYPE

SYNTAX IpAddress

ACCESS read-only

STATUS mandatory

DESCRIPTION

"IP Address of product"

::= { product 6 }



productnetgateway OBJECT-TYPE

SYNTAX IpAddress

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Gateway of product"

::= { product 7 }



productnetpridns OBJECT-TYPE

SYNTAX IpAddress

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Primary DNS of product"

::= { product 8 }



productnetsecdns OBJECT-TYPE

SYNTAX IpAddress

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Secondary DNS of product"

::= { product 9 }



sensor1name OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Type of Sensor"

::= { control 1 }



sensor1Value OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Value of Sensor"

::= { control 2 }



sensor1LastErrMsg OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Last error message of Sensor"

::= { control 3 }



sensor1LastErrTime OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Last error time of Sensor"

::= { control 4 }



sensor2name OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Type of Sensor"

::= { control 5 }



sensor2Value OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Value of Sensor"

::= { control 6 }



sensor2LastErrMsg OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Last error message of Sensor"

::= { control 7 }



sensor2LastErrTime OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Last error time of Sensor"

::= { control 8 }



sensor3name OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Type of Sensor"

::= { control 9 }



sensor3Value OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Value of Sensor"

::= { control 10 }



sensor3LastErrMsg OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Last error message of Sensor"

::= { control 11 }



sensor3LastErrTime OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-only

STATUS mandatory

DESCRIPTION

"Last error time of Sensor"

::= { control 12 }



traps OBJECT-TYPE

SYNTAX SEQUENCE OF TrapEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION

"Trap table"

::= { setup 1 }



trapEntry OBJECT-TYPE

SYNTAX TrapEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION

"Single trap entry containing trap receiver info."

INDEX { trapReceiverNumber }

::= { traps 1 }



TrapEntry ::=

SEQUENCE {

trapReceiverNumber

INTEGER,

trapEnabled

INTEGER,

trapReceiverIPAddress

IpAddress,

trapCommunity

DisplayString

}



trapReceiverNumber OBJECT-TYPE

SYNTAX INTEGER (0.. 3)

ACCESS not-accessible

STATUS mandatory

DESCRIPTION

"Index of trap receiver"

::= { trapEntry 1 }



trapEnabled OBJECT-TYPE

SYNTAX INTEGER { Yes(1), No(0) }

ACCESS read-write

STATUS mandatory

DESCRIPTION

"Indicates if this trap entry is enabled or not."

::= { trapEntry 2 }





trapReceiverIPAddress OBJECT-TYPE

SYNTAX IpAddress

ACCESS read-write

STATUS mandatory

DESCRIPTION

"Trap receiver IP address"

::= { trapEntry 3 }



trapCommunity OBJECT-TYPE

SYNTAX DisplayString

ACCESS read-write

STATUS mandatory

DESCRIPTION

"Trap community to be used by agent to send trap"

::= { trapEntry 4 }











END

Thanks and happy holidays

Only problem now seems that when the custom mib file is loaded into OpManager, it changes the threshold / alarm settings from >/ < to equal to / Not equal to, which makes the device not function properly (example, if the alarm is set to 25C, when the OpManager system sees a value such as 20.25 C it starts triggering the alarm...) Where as if the value could be set to bigger than or smaller than (> <) then the alarm would be triggered in the right manner.