New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Custom String Lookup problem

Votes:

0

Your Vote:

Up

Down

Hello, I'm trying to monitoring a HA Status in a Check Point appliance using the SNMP Custom String Lookup sensor. Here is my file:

<?xml version="1.0" encoding="UTF-8"?> <ValueLookup id="oid.checkpoint-ha-status-v1" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd"> <Lookups> <SingleInt state="Error" value="0"> Down </SingleInt> <SingleInt state="Ok" value="1"> Active </SingleInt> <SingleInt state="Warning" value="2"> Standby </SingleInt> </Lookups> </ValueLookup>

When I disable the HA, it creates a "down" string, which is found by the oid: 1.3.6.1.4.1.2620.1.5.6.0

The problem is that this sensor is not recognizing the down string and gives me the following error: The lookup "oid.checkpoint-ha-state" does not contain a definition for "down"

The other strings works just fine in the sensor. I also double checked using the common Custom Sensor String and the value is returned correctly.

Any tips?

Thanks.

custom-sensor firewall lookups

Created on Apr 1, 2019 8:23:12 PM by  Mariows (0) 2



2 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hi there,

Is the correct lookup selected? I ask because the ID of lookup is "oid.checkpoint-ha-status-v1" however the error message complains about the lookup "oid.checkpoint-ha-state".

Best regards.

Created on Apr 2, 2019 6:42:37 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Dariusz,

Thank you! For some reason PRTG was using an old version of the lookup, that was already deleted. I removed everything, made a reload of the lookups and create the file again. Now it is working!

Created on Apr 3, 2019 5:56:37 PM by  Mariows (0) 2



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.