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

Ubiquiti Wireless (UniFi Devices) showing port errors on front page

Details

    • Bug
    • Resolution: Not A Bug
    • Minor
    • None
    • Professional Edition
    • Alerting
    • None

    Description

      UniFi devices do not appear affected by the fix in OBS-2704, likely due to their primary radio interfaces having wifi* naming convention – so these interfaces fill up front page 'Status Warning' box with (expected\unavoidable) port errors.

      Attachments

        Issue Links

          Activity

            [OBS-4040] Ubiquiti Wireless (UniFi Devices) showing port errors on front page

            Understood – go ahead and close this out please.

            RocklinIT NDA Support added a comment - Understood – go ahead and close this out please.

            At present there's not a lot we can do about this. Wifi interfaces will have lots of errors because of the nature of how they operate. You can ignore the interface, which should remove it from this widget, but also from other alerting areas.

            The widget you're using is an old one, and deprecated, just retained for those who find it useful!

            adama Adam Armstrong added a comment - At present there's not a lot we can do about this. Wifi interfaces will have lots of errors because of the nature of how they operate. You can ignore the interface, which should remove it from this widget, but also from other alerting areas. The widget you're using is an old one, and deprecated, just retained for those who find it useful!

            SNMPWalks for two of the WAPs attached.

            RocklinIT NDA Support added a comment - SNMPWalks for two of the WAPs attached.

            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 -ObentxU <hostname> .1 > myagent.snmpwalk
              snmpwalk -v2c -c <community> -t 3 -Cc --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

            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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

            People

              adama Adam Armstrong
              RocklinIT NDA Support
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: