Home

Forums

Stories

Knowledge Base

Business Community > All Threads > Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

< All Threads

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Mike1972

2022-01-23 11:18:23 - last edited 2022-01-23 16:16:45

Posts: 3

Helpful: 2

Solutions: 0

Stories: 0

Registered: 2021-02-05

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

2022-01-23 11:18:23 - last edited 2022-01-23 16:16:45

Model: EAP245

Hardware Version: V3

Firmware Version: 5.0.4.

Hi All,

just today upgraded my Controller from 5.0.29 to 5.0.30.

After that my three EAP245(EU)V3 APs are no longer adopted.

Even Factory resetted the APs and forgot them in the controler.

Can see them with discovery tool then direct them to the controller, where they show up in pending state.

Trying to adopt them fails with:

01-23-2022 12:11:29.320 WARN [async-business-timeout-pool-0] [] c.t.s.o.m.d.d.m.a.a(176): timeout wait adopt watch result of OmadacId(e2ea8f6090678de6dae26e4a9b941931) DeviceMac(B0-95-75-7C-2A-04) BusinessId(topic=smb_omada_business_223cfd44-6db7-4f03-bf8b-1c4821dd83df, id=a138e841-de78-43d7-a43a-ba081d94e7f6), response:OperationResponse(errorCode=-39002, msg=Device adoption failed because the device does not respond to adopt commands

My EAP115V4 (5.0.2 FW) works like a charm.

Any ideas ? Help would be appreciated.

Thx

Mike

1 Accepted Solution

MR.S

LV5

2022-01-23 14:27:02 - last edited 2022-01-23 16:16:45

Posts: 2128

Helpful: 770

Solutions: 271

Stories: 0

Registered: 2018-08-17

Re:Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30 -Solution

2022-01-23 14:27:02 - last edited 2022-01-23 16:16:45

@Mike1972

a little bit of information so I have to guess a little.
it's probably your firewall that blocks port TCP 29814 and I'm guessing you upgraded EAP245 to the latest version as well,
v5.0.4 requires the new port
so if you have a remote controller or controller on another VLAN check that the TCP 29814 is open.

Information

Helpful: 0

Replies: 2

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

Adoption of EAP245v3 fails after Upgrade Controller to 5.0.30

Information

Voters 0

Tags