Ad Widget

Collapse

LLD Discovery filter not working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rvanderkooi
    Member
    • May 2019
    • 33

    #1

    LLD Discovery filter not working

    Hello,

    Can anybody help me? Unfortunately I can't figure it out, I've been looking for a while and tried different things.
    I feel like I'm doing so well, but apparently not.

    I would like to monitor the optical modules, but only see which ones are in it. so want to make a filter based on vendor or nu voltage.

    For the voltage I did the following:​

    I have create a template, in this template create a item with snmp walk[oid,oid,oid,oid]
    i create a discovery rule with a depended item and preprocessing: snmpwalk to json with: {#IFVOLTAGE} -> OIDprefix in this rule: .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6
    in this rule i have create a filter with:
    A: {#IFVOLTAGE} matches {$IFVOLTAGE.MATCHES}
    and
    B: {#IFVOLTAGE} does not match {$IFVOLTAGE.NOT_MATCHES}

    a macro in the template with:

    {$IFVOLTAGE.MATCHES} ^.*$
    {$IFVOLTAGE.NOT_MATCHES} -255 (also tryid ^.*-255$ and many more)

    If i test this in https://regex101.com/ i have match the right rules.

    But in my host i get the error: ".Cannot evaluate expression: "Cannot accurately apply filter: no value received for macro "{#IFVOLTAGE}".

    Output of the snmp walk is:

    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67436622 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67436686 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67436750 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67436814 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67436878 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67436942 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437006 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437070 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437134 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437198 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437262 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437326 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437390 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437454 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437518 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437582 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437646 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437710 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437774 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437838 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437902 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67437966 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67438030 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67438094 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67438158 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67438222 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67438286 = INTEGER: -255
    .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6.67438350 = INTEGER: 3294​

    They host create the items, but all the items and not only with a module. can anybody help me? thanks
  • ISiroshtan
    Senior Member
    • Nov 2019
    • 324

    #2
    I've not workerd with SNMP for a few year now, but if I remember correct Zabbix uses OID without leading dot, so do try to remove it (what I mean in snmpwalk to json with replace .1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6 with 1.3.6.1.4.1.2011.5.25.31.1.1.3.1.6)
    Also, I've never used a new type of SNMP discovery. If it still fails you can try fallback on "legacy" snmp discovery.

    Comment

    Working...