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

Ubiquiti LTU range not correctly detected

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Minor
    • None
    • Professional Edition
    • Discovery
    • LTU Rocket
      LTU Lite

    Description

      Ubiquiti LTU Rocket and LTU lite Devices identified with OS 'linux', and no device specific checks seem to exist for the radios on these (although that might be down to the fact that Ubiquiti might have written a new set of family specific MIBs for these).

       

      SNMP MIBs as provided by ubiquiti and discovery/poller/snmpwalk outputs of examples of each of these devices provided.

      Attachments

        1. lturocket-1.discovery
          125 kB
        2. lturocket.poller
          113 kB
        3. ltulite-1.poller
          110 kB
        4. ltulite-1.discovery
          113 kB

        Issue Links

          is duplicated by

          Add New Device / OS - User wants to add support for currently unsupported device or OS. OBS-3849 Ubiquiti product LTU Rocket and LTU Lite , is marked as server instead of Wireless devices

          • Major - Major loss of function.
          • Closed

          Activity

            [OBS-3843] Ubiquiti LTU range not correctly detected
            landy Mike Stupalov added a comment -

            Basic support added in r11523.
            Currently only detect os and hardware/version.

            landy Mike Stupalov added a comment - Basic support added in r11523. Currently only detect os and hardware/version.
            robmblake Rob M-B added a comment -

            (SNMP walks/discovery already added, commenting to change workflow status)

            robmblake Rob M-B added a comment - (SNMP walks/discovery already added, commenting to change workflow status)
            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
              robmblake Rob M-B
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: