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

Problem with AKCP securityProbe Sensor Values since Upgrade

Details

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

    Description

      I updated our infrastructure today after a few weeks. After the update and an automatic discovery process, we had sensor alarms on our AKCP SecurityProbe. We then discovered that there must be a problem with the power of ten in the min and max values (now determined via SNMP?). The values now read out are all too large by a factor of 10. See the attached pictures. I think that the problem could have to do with r11409.

      Attachments

        Issue Links

          relates to

          Add New Device / OS - User wants to add support for currently unsupported device or OS. OBS-3759 Add MIB support for AKCP SPX+

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

          Activity

            [OBS-3836] Problem with AKCP securityProbe Sensor Values since Upgrade
            landy Mike Stupalov added a comment -

            Derp AKCP devices, some report limits with 1 scale, some with 0.1, without any additional scale field.

            I think should be fixed detect scale by r11541.

            landy Mike Stupalov added a comment - Derp AKCP devices, some report limits with 1 scale, some with 0.1, without any additional scale field. I think should be fixed detect scale by r11541.
            swfeldkirch Siegfried Gumilar added a comment -

            Any update on this matter? I didn't see any info about it in the recent changlog entries.

            swfeldkirch Siegfried Gumilar added a comment - Any update on this matter? I didn't see any info about it in the recent changlog entries.
            swfeldkirch Siegfried Gumilar added a comment -

            additional information attached

            swfeldkirch Siegfried Gumilar added a comment - additional information attached
            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
              swfeldkirch Siegfried Gumilar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: