EAP265 HD Recovery from Recent Firmware Upgrade
I upgraded both of my EAP265 HD's recently through the controller's interface and both stopped responding to the controller. Everything else in my network is up to date and I can both SSH and login to the Web UI to see the message that they are managed by a controller. So I detached them from my controller but cannot add either back still.
EVen after using tftp to reflash the units both are still not connecting to the network.
Any advice how to reset these units? If it's possible through SSH or something else would be great.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Here is the command to reset EAP via SSH:
cliclientd reset
Or you can factory reset the EAP via its reset button:
Press and hold the button for around 8 seconds.
- Copy Link
- Report Inappropriate Content
Thanks that will be helpful for next time. It seems I have the same problem as [1] below. After upgrading to 5.2.0 neither EAP265 HD v1 US will attach to the controller at all. I had to downgrade to 5.0.5.
I tested upgrading to 5.1.0 which broke WiFi with many settings showing no option on my Omada controller, and 5.2.0 wouldn’t even give me the option to adopt it.
Worst part of it all is that I was running 5.1.0 without any problems until I tried to upgrade to 5.2.0.
All hardware is running the latest firmware including my OC300 Omada controller. [1] https://community.tp-link.com/en/business/forum/topic/765592
- Copy Link
- Report Inappropriate Content
Hi @FreeBSD
Thanks for the feedback.
Each firmware release undergoes rigorous testing before publication. This issue might be related to your specific usage scenario.
Did you configure VLAN settings for the network?
Would you please share a screenshot of the topology, including the EAP and the controller?
FreeBSD wrote
Thanks that will be helpful for next time. It seems I have the same problem as [1] below. After upgrading to 5.2.0 neither EAP265 HD v1 US will attach to the controller at all. I had to downgrade to 5.0.5.
I tested upgrading to 5.1.0 which broke WiFi with many settings showing no option on my Omada controller, and 5.2.0 wouldn’t even give me the option to adopt it.
Worst part of it all is that I was running 5.1.0 without any problems until I tried to upgrade to 5.2.0.
All hardware is running the latest firmware including my OC300 Omada controller. [1] https://community.tp-link.com/en/business/forum/topic/765592
- Copy Link
- Report Inappropriate Content
Hi @FreeBSD
We are very concerned about your feedback. Has the issue been resolved?
In the meantime, I had created a support email to follow up on this case more efficiently. The case ID is TKID250758671.
Please check your email inbox. Thanks.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 176
Replies: 4
Voters 0
No one has voted for it yet.