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 SNMP lookup

Votes:

0

Your Vote:

Up

Down

I want to create custom SNMP sensor for Cisco CUBE device to monitor dial-peer state. For example, OID 1.3.6.1.2.1.2.2.1.7.20 for dial-peer with IfIndex 20. Returning valuse are 1 (state Ok) or 2 (state Out-of-service).

I create file for custom lookup:

<?xml version="1.0" encoding="UTF-8"?>
  <ValueLookup id="prtg.custom.ciscodialpeer.state" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
    <Lookups>
      <SingleInt state="Ok" Value="1">
        1
      </SingleInt>
      <SingleInt state="Error" Value="0">
        2
      </SingleInt>
    </Lookups>
  </ValueLookup>

When dial-peer is Ok, sensor is Ok too. Value is 1, pie chart is in green zone. But when dial-peer is down, I recieve message "Error by lookup value '2' in Value". What' wrong?

cisco-cube-sip custom-lookup snmp-custom-sensor

Created on Jul 21, 2016 10:28:08 AM by  igorrev (0) 1

Last change on Jul 21, 2016 2:14:50 PM by  Torsten Lindner [Paessler Support]



5 Replies

Votes:

0

Your Vote:

Up

Down

FTFY:

<?xml version="1.0" encoding="UTF-8"?>
  <ValueLookup id="prtg.custom.ciscodialpeer.state" desiredValue="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
    <Lookups>
      <SingleInt state="Ok" Value="1">
        Dial-Peer is up.
      </SingleInt>
      <SingleInt state="Error" Value="2">
        Dial-Peer is down.
      </SingleInt>
    </Lookups>
  </ValueLookup>

The actual error value has to be 2, not one :)

Created on Jul 22, 2016 1:35:00 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I don't understand. I think you wrong.

OID 1.3.6.1.2.1.2.2.1.7.20 returns 1 or 2, not "Dial-Peer is up." or "Dial-Peer is down." When I use your XML I reciceve errors at both values.

Created on Jul 26, 2016 3:17:28 PM by  igorrev (0) 1



Votes:

0

Your Vote:

Up

Down

The lookup checks for 1 and 2, "Dial-Peer is [up|down]" is only the message in the channel that is shown. Can you post a screenshot of the sensor?

Created on Jul 27, 2016 6:55:54 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I think I know what happening. I try SNMP Custom Lookup Sensor. It use string values, right? But my OID returns integer. What Custom Sensor I need to use? How to properly setup channel?

Created on Jul 27, 2016 10:37:59 AM by  igorrev (0) 1



Votes:

0

Your Vote:

Up

Down

You need to use the SNMP Custom sensor : )

Created on Jul 27, 2016 11:59:43 AM by  Stephan Linke [Paessler Support]



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.