EAP620 Adoption times out
EAP620 Adoption times out
I am running a software controller on Windows Server and everytime I try to adopt my EAP620 the adption times out
I can see that the adoption request hits the AP but then the AP simply does not respond. I have tried factory resetting it several times without success
The controller server can ping the AP and I have tried disabling the firewall on the server but it makes no difference
I am running 5.0.30 of the controller
Logs below.
01-24-2022 00:27:02.688 INFO [https-jsse-nio-8043-exec-1] [] c.t.s.o.m.d.d.m.a.a(199): start watching adopt result of OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) DeviceMac(10-27-F5-33-7B-80), BusinessId(topic=smb_omada_business_1b2b6755-9170-45d6-86fb-fdba4d0d96d2, id=13c96033-902a-4236-bc45-62a16727a0e9)
01-24-2022 00:27:06.726 INFO [server-comm-pool-3] [] c.t.s.e.s.a.a.a(140): handle adopt fail response for 10-27-F5-33-7B-80, errcode = 1
01-24-2022 00:27:06.728 INFO [async-business-pool-0] [] c.t.s.o.m.d.d.m.a.a(164): receive adopt watch result of OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) DeviceMac(10-27-F5-33-7B-80) BusinessId(topic=smb_omada_business_1b2b6755-9170-45d6-86fb-fdba4d0d96d2, id=13c96033-902a-4236-bc45-62a16727a0e9), response:5
01-24-2022 00:27:06.728 WARN [adopt-work-group-2] [] c.t.s.o.m.d.d.m.a.a(597): Adopt device OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) DeviceMac(10-27-F5-33-7B-80) failed, errorCode 5
01-24-2022 00:27:23.111 INFO [https-jsse-nio-8043-exec-8] [] c.t.s.o.m.d.d.m.a.a(199): start watching adopt result of OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) DeviceMac(10-27-F5-33-7B-80), BusinessId(topic=smb_omada_business_1b2b6755-9170-45d6-86fb-fdba4d0d96d2, id=c3fc0fe1-cb99-49a9-80a9-a5ef4bd5ab78)
01-24-2022 00:27:23.149 INFO [async-business-pool-1] [] c.t.s.o.m.d.d.m.a.a(164): receive adopt watch result of OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) DeviceMac(10-27-F5-33-7B-80) BusinessId(topic=smb_omada_business_1b2b6755-9170-45d6-86fb-fdba4d0d96d2, id=c3fc0fe1-cb99-49a9-80a9-a5ef4bd5ab78), response:0
01-24-2022 00:27:23.189 INFO [adopt-work-group-6] [] c.t.s.o.m.d.d.m.a.c(154): send mini setting to OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) DeviceMac(10-27-F5-33-7B-80)
01-24-2022 00:28:17.205 INFO [discovery-work-group-13] [] c.t.s.o.m.d.d.m.f.b(92): start forget OmadacId(75fe8908f43e75ded0b7a3c1b36c0504) SiteId(61ed492dce4e0c681c9f392e) DeviceMac(10-27-F5-33-7B-80)
01-24-2022 00:28:17.208 WARN [discovery-work-group-13] [] c.t.s.o.m.d.d.m.f.a(110): device[omadacId=OmadacId(75fe8908f43e75ded0b7a3c1b36c0504),mac=DeviceMac(10-27-F5-33-7B-80)] is not online, skip send forget msg
01-24-2022 00:28:17.214 INFO [discovery-work-group-13] [] c.t.s.o.m.d.d.m.a.a(293): NO_MANAGED Device 10-27-F5-33-7B-80 on omadac 75fe8908f43e75ded0b7a3c1b36c0504 is discoveried.
01-24-2022 00:28:17.244 INFO [discovery-work-group-14] [] c.t.s.o.m.d.d.m.a.a(293): NO_MANAGED Device 10-27-F5-33-7B-80 on omadac 75fe8908f43e75ded0b7a3c1b36c0504 is discoveried.
01-24-2022 00:28:35.210 INFO [server-comm-pool-0] [] c.t.s.e.s.c.h.c(394): device of status ADOPT_SUCCESS time out for 10-27-F5-33-7B-80
01-24-2022 00:28:35.211 INFO [manage-work-group-6] [] c.t.s.o.m.d.p.t.c(145): Device: <10-27-F5-33-7B-80 75fe8908f43e75ded0b7a3c1b36c0504> is AdoptSuccessTimeout.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Ok, I think we have gone through the checklist, there are communication problems, then the firewall and java client are left, I would stop the controller and install java again, check that java has access to private networks on EAP controller. if it does not work then it is a support case for tp-link
- Copy Link
- Report Inappropriate Content
Dear @dddny,
Was the EAP Adoption issue resolved finally?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1670
Replies: 13
Voters 0
No one has voted for it yet.