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

Supermicro chassis intrusion alert inverted and VBAT missing

Details

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

    Description

      This is related to OBS-3187 and OBS-3664

      Since the fix of Supermicro detection in OBS-3664 everything is detected and working as expected, however Chassis Intrusion value is the exact opposite of reality. If Chassis Intru is "OK", then it is shown as "Alert" and the other way around. 

      If have read through OBS-3187 and it seems like from my understanding I can confirm that for discrete values $state instead of the $current data should be used. That should cover my scenario and those in OBS-3187 correctly - meaning in case of Intrusion 0x0000 is healthy and 0x0100 is not healthy. 

      Beside that VBAT status is not showing up in Observium. 

      Thanks a lot!

      I have added the following logs: 

      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
      		 
       
      		 
      ./poller.php -d <host> > poller.log

      Attachments

        Issue Links

          mentions

          Bug - A problem which impairs or prevents the functions of the product. OBS-3187 IPMI chassis en power supply support

          • Major - Major loss of function.
          • Closed

          Add New Device / OS - User wants to add support for currently unsupported device or OS. OBS-3664 Supermicro X11 series server showing as generic Linux device

          • Major - Major loss of function.
          • Closed

          Activity

            [OBS-3670] Supermicro chassis intrusion alert inverted and VBAT missing
            landy Mike Stupalov added a comment -

            Should be fixed in r11077.

            landy Mike Stupalov added a comment - Should be fixed in r11077.
            diamondweaver Rafael Wilms added a comment -

            Logs are already added. 

            diamondweaver Rafael Wilms added a comment - Logs are already added. 
            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
              diamondweaver Rafael Wilms
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: