Ad Widget

Collapse

Filter within Discovery

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • simao
    Member
    • Jan 2013
    • 39

    #1

    Filter within Discovery

    Hi, after upgrading to new release on Ubuntu (2.4.7 -> 3.4.12), i getting "No value received for MACRO, screenshots added.
    It was working before and now it's preventing discovery new interfaces and excluding the existing ones, because my hosts are linked to template for control reasons.
    This macro/filter also prevents me to discovery/add interfaces that are administratively down.
    Attached Files
  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #2
    When 2.4 to 3.4, the setting method of the discovery rule of SNMP LLD has been changed.
    Please tell me how you set the current discovery rule.

    Manual:

    Comment

    • simao
      Member
      • Jan 2013
      • 39

      #3
      Originally posted by Atsushi
      When 2.4 to 3.4, the setting method of the discovery rule of SNMP LLD has been changed.
      Please tell me how you set the current discovery rule.

      Manual:
      https://www.zabbix.com/documentation...very/snmp_oids
      Hi Atsushi, i changed from 3.4.7 to 3.4.12, just the release, but let me show you with screenshots attached.
      000010.png - Here is the setup to LLD
      000012.png - Here is how i scan
      000011.png - Here is the filter. If i remove the first filter "#IFADMINSTATUS", it works.

      Also, i use snmp to do this task, not agent.

      The problem is i have created this filter and i need this, since i don't want to add/discover interfaces that my customers or our IT have disabled. So i don't have to walk interface by interface checking what is up and not.

      Thanks !
      Attached Files
      Last edited by simao; 16-08-2018, 14:55.

      Comment


      • Atsushi
        Atsushi commented
        Editing a comment
        Characters of attached images are small and difficult to see.
        It seems to be using the macros of {# IFADMINSTATUS} and {# SNMPVALUE} in the discovery filter.
        And it seems as specified in the SNMP OID of the discovery rule as follows.

        discovery[{#SNMPVALUE},ifDescr]

        In this setting, only macros {# SNMPINDEX} and {# SNMPVALUE} can be used for the discovery process.
        If you want to use {# IFADMINSTATUS}, it is necessary to add a corresponding parameter to the SNMP OID.

        ex. Network Interfaces Discovery rule in "Template Module Interfaces Simple SNMPv2"

        discovery[{#SNMPVALUE},1.3.6.1.2.1.2.2.1.8,{#IFADMINSTATUS}, 1.3.6.1.2.1.2.2.1.7,{#IFALIAS},1.3.6.1.2.1.31.1.1. 1.18,{#IFNAME},1.3.6.1.2.1.2.2.1.2,{#IFDESCR},1.3. 6.1.2.1.2.2.1.2,{#IFTYPE},1.3.6.1.2.1.2.2.1.3]

        Please try changing the SNMP OID of the discovery rule.
    • simao
      Member
      • Jan 2013
      • 39

      #4
      Originally posted by simao

      Hi Atsushi, i changed from 3.4.7 to 3.4.12, just the release, but let me show you with screenshots attached.
      000010.png - Here is the setup to LLD
      000012.png - Here is how i scan
      000011.png - Here is the filter. If i remove the first filter "#IFADMINSTATUS", it works.

      Also, i use snmp to do this task, not agent.

      The problem is i have created this filter and i need this, since i don't want to add/discover interfaces that my customers or our IT have disabled. So i don't have to walk interface by interface checking what is up and not.

      Thanks !
      Thanks.
      What is embarassing me is that it worked previously version.
      I'm going to try.

      Comment

      • cameronw96
        Junior Member
        • Dec 2019
        • 2

        #5
        simao Did you resolve this?

        Comment

        Working...