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

Event VRF updated every hours

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Hi there,

      after migrating to latest version, we noticed that devices with multiple VRFs are generating eventlog every hours that VRF has been added/updated. The eventlog is full of entries like this.

      2020-12-02 11:55:52 pop13-asr VRF: 7 updated.
      2020-12-02 11:06:46 pop13-asr VRF: 7 updated.
      2020-12-02 09:28:40 pop13-asr VRF: 6 added, 1 updated.
      2020-12-02 03:46:13 pop13-asr VRF: 6 added, 1 updated.
      2020-12-01 20:57:22 pop13-asr VRF: 6 added, 1 updated.
      2020-12-01 14:54:03 pop13-asr VRF: 7 added.
      2020-12-01 09:04:16 pop13-asr VRF: 6 added, 1 updated.
      2020-12-01 04:30:38 pop13-asr VRF: 6 added, 1 updated.
      2020-11-30 21:58:05 pop13-asr VRF: 6 added, 1 updated.

       

      Attached I uploaded two discovery debugs. The first was made at 2020-12-02 11:06:46 the second at 2020-12-02 11:55:52. Last one produced antoher eventlog. Maybe you can see something was changed and what caused this log entry?

      Attachments

        Issue Links

          is mentioned by

          Bug - A problem which impairs or prevents the functions of the product. OBS-3600 Duplicate VRF entries

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-3551] Event VRF updated every hours
            dklimek Denis Klimek added a comment -

            I also see that VRF are added multiple times into the device and are not uniqure anymore. See latest screenshot, devices are showing up with hundreds of the same VRF.

            dklimek Denis Klimek added a comment - I also see that VRF are added multiple times into the device and are not uniqure anymore. See latest screenshot, devices are showing up with hundreds of the same VRF.
            dklimek Denis Klimek added a comment -

            I'am sorry, but still not fixed. We continue observing the VRF updates within eventlog

            dklimek Denis Klimek added a comment - I'am sorry, but still not fixed. We continue observing the VRF updates within eventlog
            landy Mike Stupalov added a comment -

            Yah, sorry for delay.
            Try again with r10916.

            landy Mike Stupalov added a comment - Yah, sorry for delay. Try again with r10916.
            dklimek Denis Klimek added a comment -

            Didn't fix the problem :-/ eventlog still reports changes in VRF

            dklimek Denis Klimek added a comment - Didn't fix the problem :-/ eventlog still reports changes in VRF
            landy Mike Stupalov added a comment -

            Try with r10854.

            landy Mike Stupalov added a comment - Try with r10854.
            dklimek Denis Klimek added a comment -

            PS: Wrong priority, it's not a blocker. Misclicked :/

            dklimek Denis Klimek added a comment - PS: Wrong priority, it's not a blocker. Misclicked :/
            bot Observium Bot added a comment -

            Please make and attach additional information about the device:

            • full snmp dump from device: 

              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              		 
              snmpwalk -v2c -c <community>  --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

            Note, this comment is added automatically.

            bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --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 Note, this comment is added automatically.

            People

              landy Mike Stupalov
              dklimek Denis Klimek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: