TP-Link EAP
Monitor Omada EAP connected clients and required uplinks over SNMP, with firmware prerequisites and verification guidance.
The TP-Link EAP check monitors an Omada access point's SNMP availability, connected-client count, and selected uplinks. It runs every 5 minutes by default on an octoja agent with Windows, Linux, or macOS, on x64 or ARM64. It does not monitor radio health, CPU, memory, or controller adoption.
Prerequisites
- An online octoja agent that can reach the access point's management address on UDP 161, or your configured SNMP port.
- SNMP enabled on the access point, read-only v1, v2c or v3 credentials, and access allowed from the executing agent. Match the version supported by the device firmware; query the access point, not the Omada controller.
- A verified, working client-count scalar on your exact model, hardware revision, and firmware. The check uses
1.3.6.1.4.1.11863.10.1.1.1.0from EAP-CLIENT-MIB. Check TP-Link's MIB downloads and verify the live value before relying on client-load alerts.
EAP610 v3 firmware caveat: TP-Link's support thread records client-count problems on firmware 1.3.2 and zero readings despite connected clients on a 1.4.0 beta. Users reported a fix with the support-provided build EAP610v3_1.3.90_[20230821-rel62568]_up_signed. This is not a general minimum-version rule, a recommendation to install that historical build, or a compatibility guarantee for other models. Obtain suitable current firmware for your hardware revision from TP-Link and verify the count afterward.
The check cannot distinguish a firmware-generated false zero from a genuinely empty access point and does not automatically check firmware compatibility. A zero value can therefore produce OK on affected firmware. Do not rely on client-load alerts until the verification below passes.
Prefer authenticated, encrypted SNMPv3 where supported. A v1/v2c community travels unencrypted; replace the public default on the device and in octoja.
Steps
- Open the executing device under Devices, then Checks → Add Check, and select TP-Link EAP. See Activate your first check for the assignment workflow.
- Enter the access point's management address under Host / IP and matching SNMP credentials.
- Set Client count warning and Client count critical for your site's intended load. Optionally enter exact IF-MIB
ifDescrnames orifIndexvalues under Required links. - Click Add Check, then verify the first result before relying on alerts.
You can instead register the access point as an agentless network device with a monitoring asset. Add the check to the access point's Checks tab. Its own IP address is used automatically; when SNMP is configured on the network device, its connection settings override check-level SNMP fields. Client thresholds and required links remain check settings.
Verify the client count
- Compare Connected clients in the check result with the current count in the access point or Omada controller while you know clients are connected.
- Connect or disconnect a test Wi-Fi client and compare again after the next check run. Allow for the difference in polling times; confirm that the count changes plausibly, rather than requiring identical snapshots.
- If the scalar stays at zero despite connected clients, treat client-load monitoring as unavailable. Check firmware compatibility with TP-Link, apply a suitable fix, and repeat verification. A successful SNMP connection test or a green result alone is not sufficient.
- Repeat this verification after firmware changes. Do not attempt to fix a false zero by lowering thresholds or treating every zero as a fault: an empty access point is a legitimate state.
Settings
Thresholds are inclusive. If warning exceeds critical, the check orders the pair from lower to higher. Selecting None for authentication disables encryption and hides privacy fields. MD5 and DES are not offered.
Results
The highest severity determines the overall result. SNMP uptime is displayed in days.
FAQ
Does an unavailable client count mean no clients are connected?
Does an unavailable client count mean no clients are connected?
Was this helpful?
More in Network
3CX Phone SystemBandwidthDNS ResolutionDNS Blacklist (RBL)Still need help? Ask the team