[ZBX-25855] "Ubiquiti AirOS by SNMP" template bug with CPU Utilization Created: 2025 Jan 10  Updated: 2025 Mar 20  Resolved: 2025 Mar 18

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.0.37, 7.0.7, 7.2.2
Fix Version/s: 7.0.11rc1, 7.2.5rc1, 7.4.0beta1

Type: Problem report Priority: Major
Reporter: QuasarTI Assignee: Aleksejs Abrosimovs
Resolution: Fixed Votes: 3
Labels: AirOS, SNMP, Ubiquiti
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Load in SSH.png     PNG File Load in Unifi.png     PNG File Load in Zabbix.png     PNG File Monitor configuration.png     PNG File image-2025-02-23-23-59-06-866.png     PNG File image-2025-02-24-00-03-58-145.png     PNG File image-2025-02-24-00-04-42-125.png     PNG File image-2025-02-24-00-05-23-426.png     PNG File image-2025-02-24-00-08-14-993.png     PNG File image-2025-02-24-00-08-45-525.png     PNG File image-2025-02-24-00-09-09-553.png    
Team: Team INT
Sprint: Support backlog
Story Points: 2

 Description   

Steps to reproduce:

  1. I was checking some triggers about CPU Utilization in some Ubiquiti AP's (U6-Lite and UAP-AP-PRO).
  2. My first impression is about the real utilization of the AP, and I check that the AP has 3 connections of som IoT devices, so the utilization should be almost zero.
  3. So, I've checked the CPU in Unifi website, but only shows CPU Load. (And obviuosly is not the same than CPU Utilization)
  4. So I check the template settings of monitors and I see this:
    1. Monitor: system.cpu.util[loadValue.2]
    2. SNMP OID: 1.3.6.1.4.1.10002.1.1.1.4.2.1.3.2
  5. Next, I've check the OID:
    1. snmpwalk -v2c -c {SNMP_COMMUNITY} [IP_ADDRESS_AP] 1.3.6.1.4.1.10002.1.1.1.4.2.1
  6. And the result is equal to load in the Unifi Website.
  7. I can't find any other value and information about CPU Utilization in the OIDs of the APs.
  8. So, the problem is that Load is not the same than Utilization, and the value is not processed in a right way, creating confusion and false positive triggers about this.
  9. Ironically, the description of the monitor says perfectly that the information is CPU Load.

Result:
Wrong data is collected. Load is not the same than CPU Utilization.

I was checking that this bug exists in other forums, but the technicians point to triggers, and sorry but they are wrong to point that, because is not the cause of the issue:

https://support.zabbix.com/si/jira.issueviews:issue-html/ZBX-24098/ZBX-24098.html

If this is corrected, the actual template is not updated:

https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/ubiquiti_airos_snmp/template_net_ubiquiti_airos_snmp.yaml?at=release%2F7.2

Expected:
Is expected that:

  • The information that Zabbix gets should be really a utilization percentage of cycles.
  • Or modify the monitor to indicate that data is about Load (processes) and consecuently correcting the triggers related to.

 Comments   
Comment by Aleksejs Abrosimovs [ 2025 Feb 17 ]

Hello, QuasarTI 

 

Thank you for pointing out at the problem.

Although, information you had provided is excellent and sufficient, can we ask you for more, please?

Can you, please, make synchronous screenshots of:

1) snmpwalk -v2c -c {SNMP_COMMUNITY} [IP_ADDRESS_AP] 1.3.6.1.4.1.10002.1.1.1.4.2.1

2) CPU load in web GUI

3) {{top }}command inside the device (if I recall, UniFi access points devices can be accessed via ssh, and they should have some kind of Linux)

 

It would be more than perfect if you would make such screenshots for two devices from different generations. But it not so crucial.

 

Thank you.

 

Comment by Olaff [ 2025 Feb 24 ]

Hello abrosimovs ,

I have the same issue, if I may update this comment. I have three APs (2xU6-Pro and 1xU6-Wall). Here are their "CPUs" on the default CPU dashboard:

Here is the result of my command, I was using a slightly different one (because I use SNMP v3):

snmpwalk -v3 -c {SNMP_COMMUNITY} -u my_user -X my_pass -A my_pass -l authPriv -a SHA -x AES 192.168.x.y 1.3.6.1.4.1.10002.1.1.1.4.2.1

 

U6-Pro:

SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.2 = INTEGER: 1
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.3 = INTEGER: 2
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.1 = STRING: "1 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.2 = STRING: "5 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.3 = STRING: "15 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.1 = Gauge32: 107
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.2 = Gauge32: 103
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.3 = Gauge32: 100

U6-Wall:

SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.2 = INTEGER: 1
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.3 = INTEGER: 2
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.1 = STRING: "1 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.2 = STRING: "5 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.3 = STRING: "15 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.1 = Gauge32: 111
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.2 = Gauge32: 108
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.3 = Gauge32: 103

Another U6-Pro:

SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.2 = INTEGER: 1
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.1.3 = INTEGER: 2
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.1 = STRING: "1 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.2 = STRING: "5 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.2.3 = STRING: "15 Minute Average"
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.1 = Gauge32: 110
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.2 = Gauge32: 110
SNMPv2-SMI::enterprises.10002.1.1.1.4.2.1.3.3 = Gauge32: 103

I hope my images and info will help you to adjust the template.

Kind regards.

Comment by Aleksejs Abrosimovs [ 2025 Mar 12 ]

Fixed in:

Comment by Olaff [ 2025 Mar 20 ]

Thank you, Aleksejs, I appreciate your help.

Generated at Fri Apr 11 04:36:07 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.