Ad Widget

Collapse

Autodiscover Override

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • acosta353
    Junior Member
    • May 2023
    • 3

    #1

    Autodiscover Override

    Hello,

    I need some help to understand how can I configure, and if it's possible, Autodiscover override for a specific host.

    In one of the examples, for you to understand better what I want, I have 5 switches which I'm monitoring using the "Juniper by SNMP" template.

    With this template, the "Network Interfaces Discovery" prototype has some triggers associated, where all of the "Link Down" trigger have average severity. However, there are some ports that are not average, are just warning, and some of them are even information level because those ports don't have important devices connected.

    Of course these ports are different across the switches, for example, in the "Switch1" I want port 10 with "information" severity level, but on "Switch 2" port 10 is really important, etc...

    I know that this severity can be changed using the override, but I can't find how can I configure the override to associate a specific pairing host-port. For example, create an override where host name "Switch 1" and "Port 10" will have the severity changed to information, but it will keep "Port 10" of "Switch 2" on average level.

    Is this possible to do without duplicate the template for each switch I have, is there any recognizable Macro that I can use to specify the host or something?

    Thank's in advance,
    Best Regards.
  • Hamardaban
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2019
    • 2713

    #2
    In owerride, you can use LLD macros which returns the LLD rule.
    For example, when using the interface discovery via snmp, you can get a description of the interfaces and change the severity of triggers depending on them.

    Comment

    • acosta353
      Junior Member
      • May 2023
      • 3

      #3
      Hello,

      Yes, I understand that, and I can effectively use the description, but is there any kind of macro to define those filters using the hostname?

      Thank you

      Comment

      • acosta353
        Junior Member
        • May 2023
        • 3

        #4
        Hello,

        Let me give an update about this situation.

        I tried to change the severity of some triggers using overrides by configuring regex match with the "IFALIAS" macro, that is being returned on the snmp request.

        However, I am not able to do it successfully and I'm a bit confused. I'll try to explain bellow why, and hope you may help me with some insights:

        So, as I told before, I'm trying to use the template "SNMP by Juniper" to do this. In the "Network interfaces discovery" the request is the following: "discovery[{#IFOPERSTATUS},1.3.6.1.2.1.2.2.1.8,{#IFADMINSTATU S},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.31.1.1.1.1,{#IFDESCR },1.3.6.1.2.1.2.2.1.2,{#IFTYPE},1.3.6.1.2.1.2.2.1. 3]"

        If I test this on the host, I can obtain all the data with success, but I think that the "IFALIAS" is not working well although it is being return in the discovery query.

        When I go to triggers prototypes on this discovery, I can see the following prototype: "Interface {#IFNAME}({#IFALIAS}): Link down". However, when I access the trigger after the host has been discovered, the "IFALIAS" part is always empty, so I get the normal name and then "():Link down", so the alias that should be used in the trigger name is empty...

        Maybe because of this situation, I cannot get the regex working to change the severity, apparently because the alias is not being successfully recognized (let me just remember that when I test the autodiscover, the ifalias is returning successfully with all the port alias actually defined on switch).

        So, I am a little lost here, do I need to map this variable anywhere? How could I do that? Did anyone already have a similar problem?

        Thank's in advance,
        Best Regards.

        Comment

        Working...