Hello,

For our project we need to receive traps in v2c and filter them in three cateogories:

  • hardware traps on the error channel
  • interface traps on the alert channel
  • all other traps on the messages channel

We have chosen the exact Trap OIDs that we need to be alerted about. The enterprise filter did not work for any trap, it seems like it is supported only for SNMPTrap v1. In any case, the received traps do not contain anything in the "Enterprise" column.

We have therefore used the bindings[] filter but we do not fully understand how it works. It seems like the filter accepts many more traps than wanted.

For example:

  • the bindings[snmpTraps.3] filter accepts traps like: "RFC1253-MIB::ospf.16.2.12", "BRIDGE-MIB::topologyChange" and several enterprise OIDs.
  • the bindings[some hardware trap] filter also accepts interface-related traps like snmpTraps.3

Here are our questions:

  • how exactly does the "bindings" filter work? how come it accepts trap messages that do not contain the required text at all?
  • Is it possible with PRTG to have a clear distinction between the traps received with different filters? if yes is it possible with v2c or only in v1?

Thank you very much.

Article Comments

Dear Ado Byes

Thank you for your detailed description. Some screenshots would further help to get into details. Please contact support@paessler.com and include screenshots of one of that trap receiver sensor. We would need a screenshot of

  • the overview tab
  • the logs tab
  • the settings tab (multiple screenshots if necessary to cover all option.)

Please provide screenshots as file attachments. Please capture the complete PRTG user interface in any screenshot.

In addition, please copy and paste the content of these sensor setting fields into the email text:

  • Include Filter
  • Exclude Filter
  • Warning Filter
  • Error Filter

Please also state your questions in that email again.


Jul, 2015 - Permalink