Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4027

Problems with ifTrunk in alert

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Alerting
    • None

    Description

      When I create an alert and in the Association ruleset uses the type "Port ifTrunk" and set it to not in "access,dot1q,hybrid" it does not match interfaces that has the value set to null, it only matches interfaces with the value set to "" or routed.

      I have attached two screenshots of port interface data where the ifTrunk is null or "", and it is only "" that is matching.

      Attachments

        1. iftrunk empty.png
          iftrunk empty.png
          214 kB
        2. iftrunk null.png
          iftrunk null.png
          155 kB

        Activity

          [OBS-4027] Problems with ifTrunk in alert
          landy Mike Stupalov added a comment -

          Fixed in r11887.

          landy Mike Stupalov added a comment - Fixed in r11887.
          cliff.ha Mark added a comment -

          As this is not a problem with SNMP walk or discovery but with the Association ruleset I cannot see the data is required.

          cliff.ha Mark added a comment - As this is not a problem with SNMP walk or discovery but with the Association ruleset I cannot see the data is required.
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            cliff.ha Mark
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: