Home

Forums

Stories

Knowledge Base

Business Community > WiFi > EAP225 v1 & EAP245 v1 disconnected after Omoda controller upgrade from 3.2.4 to 3.2.10 (linux)

< WiFi

EAP225 v1 & EAP245 v1 disconnected after Omoda controller upgrade from 3.2.4 to 3.2.10 (linux)

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

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

2020-05-29 14:13:23

Posts: 11

Helpful: 3

Solutions: 0

Stories: 0

Registered: 2020-04-04

EAP225 v1 & EAP245 v1 disconnected after Omoda controller upgrade from 3.2.4 to 3.2.10 (linux)

2020-05-29 14:13:23

Dear All,

I have Omada Controller on a Centos Linux VM.

I just upgraded from version 3.2.4 to 3.2.10 and after upgrade I've lost all EAPs (all are in DISCONNECT state), with the exception of all EAP245 V3.

I have a mix of EAP245 v1.0 (EU) and EAP225 v1 (EU, outdoor).

All EAPs were at the latest available firmware before I upgraded the controller.

All EAP's are reachable via network. I did reboot one for test, but remains offline.

Anyone had this issue before?

Thanks,

1 Reply

LV1

2020-05-29 18:57:25

Posts: 11

Helpful: 3

Solutions: 0

Stories: 0

Registered: 2020-04-04

Re:EAP225 v1 & EAP245 v1 disconnected after Omoda controller upgrade from 3.2.4 to 3.2.10 (linux)

2020-05-29 18:57:25

Ended-up being an issue with the POE switches (TP-Link T1600G) - no idea why but somehow related with the upgrade.

The one EAP245 that kept working was on connected on one of the core switches (no POE).

I had to restart all switches to get everything working again.