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

Override of ifSpeed on a port does not stay overridden

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Alerting, Poller, Ports
    • None

    Description

      I overrode the ifSpeed on a tunnel interface from detected speed of 100 Kbps to 400 Mbps.

      It stayed that way for a bit, i manually discovered and polled the device, the ifSpeed override stayed there.

      Then about 2 hours later it got wiped and set back to 100 Kbps.

      Vendor/Hardware Cisco ASR1001-X
      Operating system Cisco IOS-XE 03.16.02.S.155-3.S2-ext (UNIVERSALK9)

      Attachments

        1. housekeeping_delete.log
          26 kB
          Gunnar Guðvarðarson
        2. Screenshot from 2021-05-19 09-10-33.png
          27 kB
          Gunnar Guðvarðarson
        3. Screenshot from 2021-05-19 09-11-31.png
          48 kB
          Gunnar Guðvarðarson

        Activity

          [OBS-3750] Override of ifSpeed on a port does not stay overridden

          Fixed in r11330.

          Trouble was in incorrect save port attribs.

          landy Mike Stupalov added a comment - Fixed in r11330. Trouble was in incorrect save port attribs.

          Confirmed fixed in r11330.

          gunnarg Gunnar Guðvarðarson added a comment - Confirmed fixed in r11330.

          Housekeeping with -b is the cause, we run housekeeping every 2 hours and if i run it manually with -b i get:

          1 entity entries in tables 'entity_attribs' for non-existing devices will be deleted [y/N]:

          I assure you the device exists.

          gunnarg Gunnar Guðvarðarson added a comment - Housekeeping with -b is the cause, we run housekeeping every 2 hours and if i run it manually with -b i get: 1 entity entries in tables 'entity_attribs' for non-existing devices will be deleted [y/N] : I assure you the device exists.

          snmpwalk not required, we discussed in discord

          landy Mike Stupalov added a comment - snmpwalk not required, we discussed in discord

          I am not able to provide a full snmpwalk of the device since it contains customer information. Please provide more specific snmpwalks that i can do without exposing the entire device config.

          gunnarg Gunnar Guðvarðarson added a comment - I am not able to provide a full snmpwalk of the device since it contains customer information. Please provide more specific snmpwalks that i can do without exposing the entire device config.

          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
            gunnarg Gunnar Guðvarðarson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: