EAP245 V1 not working again
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
We have several EAP115-wall, EAP225-wal, EAP225, and one EAP245 on a CentOS-Omada-Controller (3.2.1)
After half a year we had the first Problems with the EAP245, TP-Link told us, that there is probably a Hardwareproblem. After a replacement the EAP seamed to work.
Now there are again Problems with this specific EAP.
Just this EAP disconnect periodicaly from the Controller accessing it directly is refused by "System is initializing,...".
After some hours or a restart it connects again to the Controller but is unable to get a proper WiFi-Channel. The Channels for 2.4 GHz and 5 GHz are shown in the Controller as "--" or with a high value.
The "locate" function is also not working, but that's probably caused by the old firmware.
We moved the EAP from the TL-SG2210P to a TL-SG3424PV2 to make sure, that no Powerproblem cause the troubles. We also reset the EAP several times and reinstalled the Omada-Controller in a fresh CentOS without any result. Actually the EAP is directly connected with a 2m CAT7 Cabel to the same Switch, where the Omada-Controller is connected.
Is there anone who has also Problems with the EAP245V1?
Is there anything else we can try to make the EAP work stable?
Sorry for the late reply.
After a reset the EAP can be adopt as usual. (With or without forgetting it in the Controller)
It seams to work, and change the state in Omada from "Pending" to "Provisioning" to "Configuring" and then to "Connected".
No Channels are assigned
After a while it loose the connection to the Omada. That means:
- In the Omada the EAP is listed as Disconnected
- The login at the Webfrontend of the EAP is not blocked anymore (no message that the EAP is managed by Controller on signin)
- The EAP is still present in the network under the given IP-Adress but on the login-page of the EAP (not Omada) the message "System is initializing,..." appears
After just reboot (not reset) the EAP it also reapears in the Controller with the same behavior. "Provisioning" -> "Configure" - > "Connected" -> "Disconnected"
Omada-Software is running on CentOS with Version 3.2.1
The Firmware of the
225-wall: 1.2.0 Build 20190222 Rel. 34350
115-wall: 1.4.0 Build 20190216 Rel. 60523
But the other AP's don't belong to the Problem becaus:
The behaviour of the EAP245 is the same on an seperated VLAN with seperate, fresh installed Omada-Controller.
Another test i just did is resetting the EAP245 again and not adopting it with any Omada.
In stand-alone-mode the EAP245 just shows up settings for 2.4GHZ.
Changing those settings is also not possible because the frontend complaines that the Tx Power(EIRP) should be "dBm (10-0)". Neighter the default value of 19 nor any other Value is accepted.
The default Network "TP-Link_2.4GHz_5002A8" is not b
radcasted.
Trying to reupload the actual firmware is not possible, the frontend replies "The version is the same as the running firmware."