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

Ubiquiti Wave Still no discovery

Details

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

    Description

      Sorry for making a new ticket, but I couldn't add the required files to the old ones. 

      I switched to rolling as soon as the change landed, updated Observium, and deleted and re-added the device to speed up discovery, but It's still seeing it as a generic Linux device. Discovery is working on the AF60LR, but not the WAVE gear. If you look at the UBNT-MIB file, line 36 is: "ubntSunMaxGroups OBJECT IDENTIFIER ::= { ubntSnmpInfo 10}" while in the updated file, it's: "uiAF60Groups OBJECT IDENTIFIER ::= { ubntSnmpInfo 10}" and Wave gear is in the AF60 group. I have uploaded a photo, and the output from the discovery debug. Thanks!

      Attachments

        Activity

          [OBS-4749] Ubiquiti Wave Still no discovery
          HamSolo Elijah Zeida added a comment -

          Working great now! Thanks!

          HamSolo Elijah Zeida added a comment - Working great now! Thanks!
          landy Mike Stupalov added a comment -

          Should be improved in r13287.

          landy Mike Stupalov added a comment - Should be improved in r13287.
          landy Mike Stupalov added a comment -

          UBNT-MIB not related with issue, I made manual changes to UI-AF60-MIB. Because Ubiquiti make 2 MIBs with same base identity.

          landy Mike Stupalov added a comment - UBNT-MIB not related with issue, I made manual changes to UI-AF60-MIB. Because Ubiquiti make 2 MIBs with same base identity.
          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.

          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
            HamSolo Elijah Zeida
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: