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


Interpreting bitmask values

Votes:

0

Your Vote:

Up

Down

Pre-fix This is not specifically PRTG related, but I am curious as if to anyone has worked with bit-masked SNMP values inside of PRTG.

I apologize for my lack of understand of bit-masks, but I am trying to create a Custom SNMP sensor to pull a summary of alarms from a device. These alarms send an integer value instead of text strings. (ex: 201327542) I have a brief understanding of how lookup files work, but am unsure of how to make use of the values sent from the device. Inside of the device's MIB file, the description states the alarm status bits are 'or'ed.

Can someone please explain this to me?

Here's the description of Summary alarm OID:

  • Bit-mask which shows alarms of the device
  • The device and its band alarm status is interrogated, the alarm status bits are 'or'ed'. The bit flags are defined in the device field *another OID field*.

And in the description of the device that has this bit flags:

  • Bit-mask which shows alarms pending on device
    • 0: PowerSourceVoltage
    • 1:Fan 2 Failure
    • 2: Fan 1 Failure
    • ..etc

Any information would be very helpful in understanding how I could use this in PRTG.

bitmask custom-lookup prtg snmp

Created on Mar 15, 2018 5:03:58 PM by  piqle (0) 1

Last change on Mar 19, 2018 7:32:46 AM by  Luciano Lingnau [Paessler Support]



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello there,
thank you for your KB-Post.

PRTG's Lookups do indeed implement the necessary groundwork for Bitmasks. Please have a look here for an example:

If your device returns only a bit single int, this is the "ideal" scenario for us. If the value was hex-encoded or a big string, this wouldn't work. But a large integer will work just fine. May I ask what device/model and MIB you're working with?

Essentially, if it's base 2 you can simply modify the lookup shared in the KB-Post shared above and adjust it to your requirements and messages/states ("Power Source Voltage Issue", "Fan 2 Failure", "Fan 1 Failure", ...

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Mar 19, 2018 7:37:05 AM by  Luciano Lingnau [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.