This is kind of goofy with how Ubiquiti doesn’t do well at supporting SNMP.  For one thing, they don’t support it through the controller, only directly to each AP.  But, you have to enable it at the controller to have it flip the switch on the APs so they’ll respond.  They really want you to use the API, which is great if you’re a programmer.  I am not.  I’m a router jockey, so I like SNMP.  Anyway, after finding and downloading the MIBs I had a look through them and sorted out a couple of OIDs I was interested in.  Specifically, client count per radio and Eth0 bits in and bits out.  Here’s what I loaded into Telegraf.  You need a separate inputs section for each AP you want to monitor.  Nope, not really an “Enterprise” approach.

[[inputs.snmp]]
agents = [ “192.168.x.x:161” ]  ## The IP of a single AP.
timeout = “5s”
retries = 3
version = 1
community = “RO_Community”
max_repetitions = 10
name = “UnifiWiFiOffice”
[[inputs.snmp.field]]
name = “Bits.Out”
oid = “1.3.6.1.4.1.41112.1.6.2.1.1.12.0”
[[inputs.snmp.field]]
name = “Bits.In”
oid = “1.3.6.1.4.1.41112.1.6.2.1.1.6.0”
[[inputs.snmp.field]]
name = “2.4.Clients”
oid = “1.3.6.1.4.1.41112.1.6.1.2.1.8.0”
[[inputs.snmp.field]]
name = “5.0.Clients”
oid = “1.3.6.1.4.1.41112.1.6.1.2.1.8.3”

Comments (3)

  1. deepy

    Reply

    Does the oids for 2.4/5.0 clients really work for you?
    1.3.6.1.4.1.41112.1.6.1.2.1.8.0 always return 0 for me and
    1.3.6.1.4.1.41112.1.6.1.2.1.8.3 (5.0 clients) returns ng

    • scott

      Reply

      It did for a while, but stopped after an update a couple of months ago. I’m going to get it working again and I’ll post my update when I do.

  2. scott

    Reply

    New OIDs for me are:

    .1.3.6.1.4.1.41112.1.6.1.2.1.8.2
    .1.3.6.1.4.1.41112.1.6.1.2.1.8.4

    Do a walk on .1.3.6.1.4.1.41112.1.6.1.2.1.8 and there should be only two active counters reporting.

Leave a comment

Your email address will not be published. Required fields are marked *