What Should I Do if Omada Software Controller/OC200 Cannot Adopt Omada EAP
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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.
- 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-29813. 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-29813 in the anti-virus/firewalls (since Omada Software Controller communicate with Omada EAP via TCP/UDP port 29810-29813)
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.
Hello thanks for the guide.
However I faced problem not seeing any of those messages when adoption failed.
Here are the context. I have previously set up an older version of Omada Controller and it works fine. I can adopt, accept, and manage the EAPs.
Some time later, my boss want use the newer omada version with mesh capability. So I am trying to set up a new controller and test it out. My discovery runs on a different subnet as my new controller.
Problem faced:
The new controller shares the same setting as my old controller:
- Same network
- Same router firewall rule
- Same local inbound and outbound rule
Difference:
- Old controller Window 7; New controller Window 10
- New controller uses version with mesh capability
I have verified both falls in the same router firewall rule by testing both controllers on port reachability e.g. ping. So i determine somehow the fault lies in the computer my new controller resides.
Below are my screenshot and snippets of the log generated by EAP Discovery. Some help would be appreciated.
I have reviewed the logs generated by the discovery, below are the part of it,
2020-04-29 11:56:13 [defaultEventExecutorGroup-8-1] [INFO]-[SourceFile:156] - Adopting device failed for mac: 50-D4-F7-6A-DD-9A, adoptResult is 1.
2020-04-29 11:56:38 [defaultEventExecutorGroup-8-2] [INFO]-[SourceFile:156] - Adopting device failed for mac: 50-D4-F7-6A-DD-9A, adoptResult is 1.
2020-04-29 11:57:02 [defaultEventExecutorGroup-8-3] [INFO]-[SourceFile:156] - Adopting device failed for mac: 50-D4-F7-6A-DD-9A, adoptResult is 1.
2020-04-29 11:57:07 [defaultEventExecutorGroup-8-1] [INFO]-[SourceFile:156] - Adopting device failed for mac: 50-D4-F7-6A-DD-9A, adoptResult is 1.
2020-04-29 11:57:56 [main] [INFO]-[SourceFile:85] - success to load configuration device.properties
2020-04-29 11:57:56 [main] [INFO]-[SourceFile:85] - success to load configuration netty.properties
2020-04-29 11:57:56 [main] [WARN]-[SourceFile:108] - can't get resolve value for key: eap.add.firewall.command
2020-04-29 11:57:56 [main] [WARN]-[SourceFile:108] - can't get resolve value for key: discover.add.firewall.command
