Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • None
    • Discovery

    Description

      Hi Team,

      We have recently on-boarded 5 AVTECH RoomAlert devices and have found that some of the sensors are not reporting into Observium.

      There are 2 models and each seems to be having slightly different issues.

      I have attached the requested dumps and MIB files as well as some details on the issues we are seeing for each device type.

      These devices are monitoring Medical MRI machines and are very important as if there are any issues with the machines that are not detected - it can be extremely costly $1-3m potentially.

      Please let me if you need anything else, thanks.

      Attachments

        Activity

          [OBS-4963] SONIC - Device Sensors not reporting
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Improved in r13839.

          landy Mike Stupalov added a comment - Improved in r13839.
          landy Mike Stupalov made changes -
          Issue Type Original: Add New Device / OS [ 10002 ] New: Improvement [ 4 ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: In Progress [ 3 ]

          snmpwalk output files attached

          MKozanic Mark Kozanic added a comment - snmpwalk output files attached
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          MKozanic Mark Kozanic made changes -
          Attachment New: 4465.snmpwalk [ 21577 ]
          Attachment New: 4468.snmpwalk [ 21578 ]
          Attachment New: 4469.snmpwalk [ 21579 ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          MKozanic Mark Kozanic created issue -

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            MKozanic Mark Kozanic
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: