What should I do if Omada Software Controller OC200 cannot adopt Omada EAP

OC200
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
Omada Software Controller/OC200 is used to centrally manage Omada EAP products. When the Omada EAP is first discovered by the controller, it will show in the Pending List of Omada Controller/OC200 first. Then we can click Adopt button to adopt the Omada EAP.
Here are some common errors and fixed solutions when Omada Software Controller/OC200 fails to adopt Omada EAPs. And the computer with controller software installed is suggested to be connected to Router/Modem via cable, since wireless connection is not stable, it may cause some management issues.
1. Error: The Username or Password is incorrect
The default Username/Password of Omada EAP is admin/admin.
1) If the EAP worked in the standalone mode before, then the Username/Password will be the login account of web management page.
2) If the EAP was managed by Omada Software Controller/OC200 before, the Username/Password will be the device account of Omada Software Controller/OC200. (You can check the device account at Site Settings->Device Account on Omada Software Controller/OC200.)
If these solutions do not work, you can reset the EAP (the username/password will be default) and try to adopt it again.
2. Error: Failed to send adopt command to the AP
It means that the communication between EAP and Omada Software Controller/OC200 is blocked.
1) To make sure the Omada EAP is accessible, please ping the IP address of EAP on the PC that the Omada Software Controller is installed.
2) If you have VLAN settings in your network, please make sure the EAP and Omada Software Controller/OC200 belong to the same VLAN.
3) Omada Software Controller/OC200 communicates with Omada EAP via TCP/UDP port 29810-29814. Some anti-virus program or firewalls may block this kind of packets. You can disable the anti-virus or firewalls (on the PC that the Omada Software Controller is installed) in your network first for checking. And you need to open TCP/UDP port 29810-29814 in the anti-virus/firewalls (since Omada Software Controller communicate with Omada EAP via TCP/UDP port 29810-29814)
3. Error: AP to be adopted doesn’t exist
1) Web page may be aging. Please refresh the management page of Omada Software Controller/OC200 and try again.
2) There may be some compatibility problems between the browser and Controller. Try to upgrade the web browser or change another browser for checking.
Finden Sie diese FAQ hilfreich?
Mit Ihrer Rückmeldung tragen Sie dazu bei, dass wir unsere Webpräsenz verbessern.
Was ist Ihr Bedenken bei diesem Artikel?
- Mit Produkt unzufrieden
- Zu kompliziert
- Irreführende Titel
- Betrifft mich nicht
- Zu ungenau
- Was anderes
Vielen Dank.
Vielen Dank für Ihr Feedback.
Recommend Products
Von United States?
Erhalten Sie Produkte, Events und Leistungen speziell für Ihre Region
Diese Webseite verwendet Cookies, um die Websitenavigation zu verbessern, Online-Aktivitäten zu analysieren und die bestmögliche Nutzererfahrung auf unseren Webseiten zu haben. Sie können der Verwendung von Cookies jederzeit Widersprechen. Nähere Informationen finden Sie in unseren Datenschutzhinweisen.
Diese Webseite verwendet Cookies, um die Websitenavigation zu verbessern, Online-Aktivitäten zu analysieren und die bestmögliche Nutzererfahrung auf unseren Webseiten zu haben. Sie können der Verwendung von Cookies jederzeit Widersprechen. Nähere Informationen finden Sie in unseren Datenschutzhinweisen.
Notwendige Cookies
Diese Cookies sind zur Funktion der Website erforderlich und können in Ihren Systemen nicht deaktiviert werden.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analyse- und Marketing-Cookies
Analyse-Cookies ermöglichen es uns, Ihre Aktivitäten auf unserer Website zu analysieren, um die Funktionsweise unserer Website zu verbessern und anzupassen.
Die Marketing-Cookies können über unsere Website von unseren Werbepartnern gesetzt werden, um ein Profil Ihrer Interessen zu erstellen und Ihnen relevante Anzeigen auf anderen Websites zu zeigen.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au