EAP653 is not adopted after update to 1.3.3
EAP653 is not adopted after update to 1.3.3
Updated the controller to 6.2.0.17 and everything worked well with EAP on firmware 1.1.3
After update of EAP to verion 1.3.3 the EAP will not get adopted.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Found this:
05-07-2026 22:36:16.748 INFO [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.a.a(): receive adopt watch result of OmadacId(ad1e7c6e77b7621b07f0fda4a60f7323) DeviceMac(VPnujNKdTJVHVRgrZ3BozoMEo5EaxpQUcg4yzTD4Htc=) BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7), response:4
05-07-2026 22:36:16.748 WARN [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.a.a(): timeout wait adopt watch result of OmadacId(ad1e7c6e77b7621b07f0fda4a60f7323) DeviceMac(VPnujNKdTJVHVRgrZ3BozoMEo5EaxpQUcg4yzTD4Htc=) BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7), response:OperationResponse(errorCode=-39002, msg=Device adoption failed because the device does not respond to adopt commands., result=AdoptOneDeviceStatusResultVO(mac=34-60-F9-5D-26-6E, status=22, statusCategory=2, specificationNote=null, adoptFailType=-1, waitTime=null, retryChances=null, adoptTip=null), auditLogReturn=null, auditLogReturnList=null)
05-07-2026 22:36:16.749 WARN [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.d.RunTimeAdoptInfo(): errorMsg:null is invalid!
05-07-2026 22:36:16.750 WARN [async-business-timeout-pool-2] [] c.t.s.o.m.d.d.m.a.a(): Adopt device OmadacId(ad1e7c6e77b7621b07f0fda4a60f7323) DeviceMac(VPnujNKdTJVHVRgrZ3BozoMEo5EaxpQUcg4yzTD4Htc=) Timeout, errorCode 7
05-07-2026 22:36:16.752 WARN [async-business-timeout-pool-2] [] c.t.s.o.a.b.a(): DeferredResponse of BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7) is time out, remove from timeout holder
05-07-2026 22:36:16.752 WARN [async-business-timeout-pool-2] [] c.t.s.o.a.b.a(): DeferredResponse of BusinessId(topic=smb_omada_business_e260c969-e15f-457f-940c-491ef16afe2b, id=d4143003-ccb0-4c11-b208-81c551b33af7) is time out, remove from response holder
Can anyone let me know what this means: errorCode=-39002
Thanks,
Mario
- Copy Link
- Report Inappropriate Content
Hi @MarioRuck
Thanks for posting here.
This error code has no specific meaning. What error message did the controller report when the adoption failed?
You may refer to the following guide to do some troubleshooting:
What to do if Omada Device Adoption Failure
In addition, neither the controller nor the EAP is working on the latest firmware version. I recommend updating their firmware first.
https://support.omadanetworks.com/en/product/omada-software-controller/?resourceType=download
https://support.omadanetworks.com/en/product/eap653/v1/?resourceType=download
- Copy Link
- Report Inappropriate Content
Hello Vincent,
thanks for your hints.
I did update the controller and the EAP to the latest versions (6.2.10.17 and 1.3.7). Unfortunately the issue remains unchanged.
The log shows:
"adoption failed because the device does not respond to adopt commands"
Is there a hard change in the firmware of the EAP for access/connectivity to version 5.x?
- Copy Link
- Report Inappropriate Content
@Vincent-TP
Hello Vincent,
did get the EAP adopted. But it seems there are changes in the EAP behavior. My recent configuaration is to run all EAP and also Interswitch connections based on 802.1 Q Tagging. The IP address aquisition for the VLAN has been managed via the PVID. Worked well since years.
Now the EAP seems not to receive an IP address via this setup on the expected VLAN.
I did change the VLAN for the adress aquisition on the port to untagged. Then it works. Can you please check if this is the expected behavior? I think even via a Q-tagged connection the IP address aquisition should work.
Thanks in advance,
Mario
- Copy Link
- Report Inappropriate Content
@Vincent-TP
After a few hours off, the devices on the IP networks with issues have not been able to do the renew of IP addresses. I went back to the 6.2.0.17-controller to check if this does not have the issue. Any feedback on this?
Mario
- Copy Link
- Report Inappropriate Content
Hi @MarioRuck
Thanks for your reply.
To address your VLAN inquiry, we need to combine your overall network topology, specific VLAN configurations, and your requirements to analyze and provide recommendations. Therefore, please provide the following information:
1. A screenshot of the topology page of your controller;
2. A screenshot of the Device page, we need to know the SDN devices and their firmware version, hardware version.
3. Screenshots of the current VLAN config pages;
4. Your requirement to configure these VLANs.
BTW, how did you finally get the EAP adopted?
- Copy Link
- Report Inappropriate Content
Hello Vincent,
with the latest release of the controller I face a lot of issues and cannot run it in my environment. I would suggest we taking this off the community list now and move this to regular support.
Thanks for your support.
Mario
- Copy Link
- Report Inappropriate Content
Hi @MarioRuck
Thanks for posting here.
Do you mean the controller or the EAP? What kind of issue did you encounter?
Currently, we have not received much feedback indicating that a particular firmware has usage-affecting issues requiring removal. Could you please specify your product and the exact problem encountered? This is mostly caused by some specific config. You may start a new thread to discuss separately.
MarioRuck wrote
Hello Vincent,
with the latest release of the controller I face a lot of issues and cannot run it in my environment. I would suggest we taking this off the community list now and move this to regular support.
Thanks for your support.
Mario
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1016
Replies: 18
Voters 0
No one has voted for it yet.