Hi,
I've created successfully two custom snmp sensors with an lookup file (.ovl) on my testing system, which has PRTG v15.1.15.2021 installed.
Now I've migrated these sensors (oidlib and ovl files) to a new server with PRTG v15.3.19.4028.
When I try to add an OID of my sensor which has a lookup (i.e. temperature range; all OIDs without lookups are working fine) to the ovl file, I'll the following error message:
--------------------------- Error (Bad Request) Internal Error: Invalid pointer operation Error details Version: 15.3.19.4028 Server: x.x.x.x URL: addsensor5.htm?name=Base+Sensor&parenttags_=&tags_=snmplibrarysensor&priority_=3&library_=C:\Program+Files+(x86)\PRTG+Network+Monitor\snmplibs\snmp_hwg-ste_v1.oidlib&selectionname=&interfacenumber_=1&interfacenumber_=1&interfacenumber__check=1.3.6.1.4.1.21796.4.1.3.1.4.1|HWg-STE|Sensor:+1|Temperature|°|0|0|Temperature|2|1|0|1|The+string+representation+of+sensor+value.|0|0|0|-1|prtg.standardlookups.hwgste.temperature|&unit=#&factorm=1&factord=1&monitorchange_=0&intervalgroup=0&intervalgroup=1&interval_=60|60+seconds&errorintervalsdown_=1&inherittriggers=1&id=2078&sensortype=snmplibrary Time: 11:4:20 ---------------------------
Content of the oidlib-file:
<?xml version="1.0" encoding="UTF-8"?> <oidlist> <system> <version> 2 </version> </system> <list> <entry> <name> HWg-STE|Device Information|MAC-Address </name> <oid> 1.3.6.1.4.1.21796.4.1.70.1.0 </oid> <type> vmString </type> <kind> mkDirect </kind> <unittype> sutCustom </unittype> <units> # </units> <indicator> MAC-Address </indicator> <scale> 1 </scale> <multiply> no </multiply> <max> 0 </max> <usegetnext> no </usegetnext> <is64bit> no </is64bit> <isunsigned> no </isunsigned> <isfloat> no </isfloat> <description> MAC address in text form. It is here to distinguish devices in trap messages. </description> </entry> <entry> <name> HWg-STE|Sensor: #[1.3.6.1.4.1.21796.4.1.3.1.1]|Sensor Name </name> <oid> 1.3.6.1.4.1.21796.4.1.3.1.2 </oid> <type> vmString </type> <kind> mkTable </kind> <unittype> sutCustom </unittype> <units> # </units> <indicator> Sensor Name </indicator> <scale> 1 </scale> <multiply> no </multiply> <max> 0 </max> <usegetnext> no </usegetnext> <is64bit> no </is64bit> <isunsigned> no </isunsigned> <isfloat> no </isfloat> <description> The sensor name. </description> </entry> <entry> <name> HWg-STE|Sensor: #[1.3.6.1.4.1.21796.4.1.3.1.1]|Sensor State </name> <lookupname> prtg.standardlookups.hwgste.sensorstate </lookupname> <oid> 1.3.6.1.4.1.21796.4.1.3.1.3 </oid> <type> vmAbsolute </type> <kind> mkTable </kind> <unittype> sutCustom </unittype> <units> # </units> <indicator> Sensor State </indicator> <scale> 1 </scale> <multiply> no </multiply> <max> 0 </max> <usegetnext> no </usegetnext> <is64bit> no </is64bit> <isunsigned> no </isunsigned> <isfloat> no </isfloat> <description> The sensor state. </description> </entry> <entry> <name> HWg-STE|Sensor: #[1.3.6.1.4.1.21796.4.1.3.1.1]|Temperature </name> <lookupname> prtg.standardlookups.hwgste.temperature </lookupname> <oid> 1.3.6.1.4.1.21796.4.1.3.1.4 </oid> <type> vmAbsolute </type> <kind> mkTable </kind> <unittype> sutCustom </unittype> <units> ° </units> <indicator> Temperature </indicator> <scale> 1 </scale> <multiply> no </multiply> <max> 0 </max> <usegetnext> no </usegetnext> <is64bit> no </is64bit> <isunsigned> no </isunsigned> <isfloat> yes </isfloat> <description> The string representation of sensor value. </description> </entry> <entry> <name> HWg-STE|Sensor: #[1.3.6.1.4.1.21796.4.1.3.1.1]|Serial Number </name> <oid> 1.3.6.1.4.1.21796.4.1.3.1.6 </oid> <type> vmString </type> <kind> mkTable </kind> <unittype> sutCustom </unittype> <units> # </units> <indicator> Serial Number </indicator> <scale> 1 </scale> <multiply> no </multiply> <max> 0 </max> <usegetnext> no </usegetnext> <is64bit> no </is64bit> <isunsigned> no </isunsigned> <isfloat> no </isfloat> <description> The sensor Serial number. </description> </entry> </list> <lookups> <prtg.standardlookups.hwgste.sensorstate> <cell row="0" col="0"> 1 </cell> <cell row="0" col="1"> Good </cell> <cell row="1" col="0"> 5 </cell> <cell row="1" col="1"> Error </cell> </prtg.standardlookups.hwgste.sensorstate> <prtg.standardlookups.hwgste.temperature> <cell row="0" col="0"> 1 </cell> <cell row="0" col="1"> Warning </cell> <cell row="1" col="0"> 2 </cell> <cell row="1" col="1"> Excellent </cell> <cell row="2" col="0"> 3 </cell> <cell row="2" col="1"> Good </cell> <cell row="3" col="0"> 4 </cell> <cell row="3" col="1"> Warning </cell> <cell row="4" col="0"> 5 </cell> <cell row="4" col="1"> Error </cell> </prtg.standardlookups.hwgste.temperature> </lookups> </oidlist>
Content of the ovl-files:
File 1:
<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="prtg.standardlookups.hwgste.sensorstate" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
<Lookups>
<SingleInt state="Ok" value="1">
Good
</SingleInt>
<SingleInt state="Error" value="5">
Error
</SingleInt>
</Lookups>
</ValueLookup>
File 2:
<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="prtg.standardlookups.hwgste.temperature" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
<Lookups>
<Range state="Warning" from="1" to="15">
Warning
</Range>
<Range state="Ok" from="16" to="22">
Excellent
</Range>
<Range state="Ok" from="23" to="26">
Good
</Range>
<Range state="Warning" from="27" to="29">
Warning
</Range>
<Range state="Error" from="30" to="120">
Error
</Range>
</Lookups>
</ValueLookup>
When I remove the lookup-section at the end of my oidlib-file, the OIDs can be added, but then the custom messages instead of the values are not shown. As I already described, it's working fine with the old release.
Best regards,
Christian
Add comment