Value lookups in oidlib

Here is an example that might help clarify.

I created a lookup file that looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<ValueLookup id="oid.paessler.dellpowerconnectfanstatus" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
	<Lookups>
		<SingleInt state="Warning" value="0">Fan Not Working 1</SingleInt>
		<SingleInt state="Ok" value="1">Fan Working 1</SingleInt>
	</Lookups>
</ValueLookup>

This lookup file (*.ovl) is primarily for PRTG itself and defining the primary channel and what values are acceptable as well as what should trigger Error States

Some more information about customizing these lookups can be found here: Define Lookups.

Once this lookup is created, you can define the sensor to use this with a particular OID by using the code

<lookupname>oid.paessler.dellpowerconnectfanstatus</lookupname>

But you must also define these parameters in the oidlib itself. I put the following code in the oidlib for this example:

<lookups>
	<oid.paessler.dellpowerconnectfanstatus>
		<cell row="0" col="0">0</cell>
		<cell row="0" col="1">fan not running</cell>
		<cell row="1" col="0">1</cell>
		<cell row="1" col="1">fan running</cell>
	</oid.paessler.dellpowerconnectfanstatus>
</lookups>

This is what will guide the sensor to use the correct language in the sensor as well as which lookup should be used.

Here is the complete oidlib

<?xml version="1.0" encoding="UTF-8"?>
<oidlist>
	<system>
		<version>2</version>
	</system>
	<list>
		<entry>
			<name>Dell-Vendor-MIB|env mon fan status: #[1.3.6.1.4.1.674.10895.3000.1.2.110.7.1.1.1]|env mon fan state</name>
			<lookupname>oid.paessler.dellpowerconnectfanstatus</lookupname>
			<oid>1.3.6.1.4.1.674.10895.3000.1.2.110.7.1.1.3</oid>
			<type>vmAbsolute</type>
			<kind>mkTable</kind>
			<unittype>sutCustom</unittype>
			<units>#</units>
			<indicator>env mon fan 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 mandatory  state of the fan being instrumented.</description>
		</entry>
	</list>
	<lookups>
		<oid.paessler.dellpowerconnectfanstatus>
			<cell row="0" col="0">0</cell>
			<cell row="0" col="1">fan not running</cell>
			<cell row="1" col="0">1</cell>
			<cell row="1" col="1">fan running</cell>
		</oid.paessler.dellpowerconnectfanstatus>
	</lookups>
</oidlist> 

Now, when you add this new sensor from the SNMP sensor library, you should see the values you want, the states can be used to trigger events and the lookup will automatically associate with the sensor.