Ubiquiti

Ubiquiti is a genuine case where "how do I configure SNMP" has two completely different answers depending on which product line you're on - there's no unified Ubiquiti SNMP configuration method.

EdgeRouter (EdgeOS) - real CLI, standalone device

EdgeRouters run EdgeOS, which has an actual configuration CLI (VyOS-derived) and are configured standalone, without a separate controller:

configure
set service snmp community public authorization ro
set service snmp location "Rack 4, DC1"
set service snmp contact [email protected]
set service snmp trap-target 192.168.1.100
commit
save

To restrict a community to specific clients rather than accepting queries from anywhere:

set service snmp community public client 10.0.0.0/24

UniFi devices (switches, APs, gateways) - controller GUI only

UniFi-managed devices (switches, access points, UniFi gateways) have no standalone SNMP CLI to configure directly - SNMP is enabled and configured entirely through the UniFi Controller/UniFi OS Console, then pushed out to devices during provisioning:

1. In the UniFi Network application, go to Settings (the exact path has moved between UniFi OS versions - look under Advanced Features > Advanced Gateway Settings > SNMP, or on newer versions CyberSecure > Traffic Logging).
2. Enable SNMP v1/v2c (set a community string, default is public - change it) and/or SNMPv3 (username and password).
3. Click Apply Changes - the setting is provisioned out to adopted devices, not configured on them individually.

A real UniFi SNMPv3 limitation worth knowing

The UniFi Controller's SNMPv3 support is deliberately simplified rather than fully configurable: the authentication protocol is hardcoded to SHA and the privacy protocol to AES-128 - there's no option to choose MD5 or DES the way there is on EdgeOS or most other vendors here. The controller also only exposes a single password field, which it uses as both the authentication and privacy password - when configuring a monitoring tool that expects separate auth/priv passwords, use the same value for both.

Model/platform differences worth knowing

• UniFi Dream Machine Pro (UDM-Pro) - Ubiquiti's own documentation states SNMP is not recommended or supported on this specific model, unlike other UniFi gateways.
• USW Flex and USW Ultra switches - do not support SNMP at all, per Ubiquiti's current documentation, unlike the rest of the UniFi switch line.
• UniFi Access Points - have no SNMP agent of their own; AP-level stats are only reachable through the controller, not by polling an AP directly.

Given this split, the first practical question for any Ubiquiti device isn't "what's the SNMP command" but "is this an EdgeRouter or a UniFi-managed device" - the two have nothing in common configuration-wise.

Common OIDs and MIBs

Ubiquiti's own MIB tree lives under enterprises.41112 (1.3.6.1.4.1.41112) - and true to the product-line split running through this whole guide, it's organized into separate sub-MIBs per product family rather than one shared structure, matching the same divide as the configuration methods above.

• EdgeMAX (EdgeRouter/EdgeSwitch) - UBNT-EdgeMAX-MIB (1.3.6.1.4.1.41112.1.5). Beyond the standard IF-MIB/HOST-RESOURCES-MIB data any EdgeOS device also exposes, this adds hardware-specific tables like ubntPsuVoltage, ubntPsuTemperature, and ubntPsuBatteryTimeRemaining for models with monitorable power supplies (relevant on EdgeRouter models with a built-in UPS/battery, not applicable on ones without).
• AirMAX (point-to-point/point-to-multipoint wireless) - UBNT-AirMAX-MIB (1.3.6.1.4.1.41112.1.4). Wireless-link-specific quality metrics that have no equivalent in a standard MIB - ubntStaCcq (Client Connection Quality, as a percentage) is the headline one for judging an AirMax wireless link's actual health, alongside per-station signal and capacity figures. This is specific to standalone AirMax gear (typically WISP-style point-to-point or point-to-multipoint links) - it doesn't apply to UniFi access points, which are a completely different product line with no standalone agent at all, as covered above.
• AirFiber - UBNT-AirFIBER-MIB (1.3.6.1.4.1.41112.1.3) covers Ubiquiti's dedicated point-to-point backhaul radios, structured similarly to AirMAX's own MIB but for that specific product line.

Gotchas and platform-specific nuances

The vendor-specific MIB you need depends entirely on which Ubiquiti product line you're polling - there's no shared "Ubiquiti" MIB that covers all of them. A monitoring template built for AirMax link quality (ubntStaCcq and friends) has nothing useful to say about an EdgeRouter's power supply, and vice versa - each sub-MIB under enterprises.41112 is genuinely specific to its own product family, mirroring the same "which product line is this" question that determines how you'd even configure SNMP on the device in the first place.

AirMax-specific wireless metrics only exist on AirMax gear with an actual SNMP agent to ask. Since UniFi access points have no standalone SNMP agent (as covered above), there's no way to poll UBNT-AirMAX-MIB-style wireless quality data from a UniFi AP directly, even though it's visually similar hardware to Ubiquiti's standalone AirMax line - any wireless client/signal data for UniFi APs has to come from the controller's own API or interface, not from SNMP at all.

Firmware and product-line changes can silently move where a specific metric lives. Given how much this vendor's SNMP support is split by product family and has evolved over successive hardware generations, a specific OID that worked on one firmware version or model isn't guaranteed to carry over to a newer one in the same nominal product line - worth re-verifying with a fresh walk after any firmware upgrade, rather than assuming a previously-working OID will keep reporting the same thing indefinitely.