Omada Cloud Controller – EAP Onboarding Quirk
Omada Cloud Controller – EAP Onboarding Quirk
While onboarding a TP-Link EAP via the Omada Cloud-Based Controller, I encountered a confusing dual-state behavior. Here's the full sequence:
-
Initial Connection (No ZTP Preconfiguration):
-
I connected the EAP to the network without first registering its serial number in the cloud controller.
-
As a result, the EAP appeared only in the Client List, categorized as “Other,” with an assigned IP address — but not in the Device List.
-
-
Manual ZTP Registration:
-
I then manually added the EAP via “Add Device” > “Manually Add” > “Add by Serial Number” in the cloud controller.
-
The controller accepted the serial number and marked the device as “Preconfigured”, but it still did not appear in the Device List or offer any adoption options.
-
-
Factory Reset and Reconnection:
-
After performing a hard reset on the EAP and reconnecting it to the network, it finally showed up in the Device List as “Preconfigured”, with correct model and parameters.
-
-
Client List Cleanup Attempt:
-
The EAP still appeared in the Client List with the same MAC address and a frozen uptime counter.
-
I used the “Forget” option in the Client List, which had no visible effect — the entry remained.
-
-
Final Transition to Managed Device:
-
Despite the lingering client entry, the EAP transitioned to “Connected” in the Device List and became fully manageable.
-
WLAN functionality confirmed the device was properly adopted and operational.
-
-
Residual Client Entry:
-
The EAP continues to appear in both the Device and Client Lists.
-
The client entry shows a frozen uptime and cannot be removed via “Forget,” suggesting it’s a stale artifact — likely a UI or backend bug in the cloud controller.
-
🧠 Summary
This behavior appears to be a reproducible edge case in Omada Cloud Controller deployments:
“If an EAP is connected before its serial number is registered via ZTP, it may be misclassified as a client. Even after successful adoption, a stale client entry may persist with a frozen uptime and cannot be removed via the ‘Forget’ option. WLAN and device management remain unaffected.”
