eap653 needs reboot every 3-4 days with v1.0.9 fw - memory leak?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
i've upgraded my 3 EAP653v1(EU) Accesspoints to v1.0.9 firmware few weeks ago. Since this upgrade, i need to reboot the accesspoints with the new firmware every 3 or 4 days, cause they have massive packet loss and are not reachable / manageable anymore.
After reboot, they are working fine again.
I've downgrade one of the EAP653 back to version 1.0.4 and the problem is gone. So it seems to be an issue with the v1.0.9 firmware.
Under statistics, i see that the Accesspoint with firmware v1.0.9 starts with memory of 58% after reboot and after 3-4 days, memory raises up to 67-68% with massiv packetloss and the accesspoint stops working. Seems to be a memory leak or something similar.
Does anyone else have a issue like this after upgrade? Any Ideas?
If needed: Controller version is 5.12.7
Memory last 5 days - 1h resolution (reboot oct 5th, 2:00pm)
Memory today with packet loss - 5min resolution (reboot after 8:45)
Massive Paket loss (ping from wired pc to wired accesspoint):
ssh and top - sort by mem 1 day before the issue:
ssh and top - sort by mem after reboot:
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
A short update:
In the past weeks, i was directly in contact with TP-link Technical Support. The R&D Team provide me a new beta version of the 1.0.9 firmware, where the memory issue is fixed. My Eap653 Accesspoints are now running stable since 2 weeks without reboot.
The fix will be part of the next official firmware release for 653 Accesspoints.
Thanks all for help!
- Copy Link
- Report Inappropriate Content
Hi All,
TP-Link has provide a Beta firmware to fix the issue, please check the following post for details.
EAP653 Becomes Unreachable Or Clients Fail to Connect SSIDs After Upgrading to 1.0.9 Build20230814
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@marcel_ I think your guess is correct, it is recommended that you downgrade the firmware to the previous version to use normally, this v1.0.9 has just been released, and many bugs may have not been found or even dealt with, you can expect this problem to be fixed in the next version.
- Copy Link
- Report Inappropriate Content
Hello @marcel_,
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID231019156, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
I would guess it's related to a mangement function, my unmanaged EAP653 seems fine.
- Copy Link
- Report Inappropriate Content
@Hank21 thanks for your support. i received the mail and i'm in contact with your support engineers.
@DIDADI Unfortunately i can only downgrade 2 of my 3 Accesspoints to 1.0.4. For the last one, i receive an error during downgrade... i dont know why, maybe because this one was the only one, which was delivered with 1.0.6 firmware as factory default.
At the moment i've scheduled a reload of this accesspoint every night as a workaround. But this is not a permanent solution.
@TLnet one of my colleagues also use 4 eap653v1 with 1.0.9 and omada management software. He has no issues and everything works fine. Maybe it is some kind of special configuration which cause this issue. For example i use an external freeradius server for dynamic vlan assignment to the clients... my colleague not.
- Copy Link
- Report Inappropriate Content
Hello @marcel_,
Our senior engineer has received your feedback on the issue via email, they will continue to follow up with your case. If you have any additional information, please feel free to reply to the support email whose case ID is TKID231019156. Many thanks for your cooperation and patience!
Thank you for your valued update on the case.
- Copy Link
- Report Inappropriate Content
A short update:
In the past weeks, i was directly in contact with TP-link Technical Support. The R&D Team provide me a new beta version of the 1.0.9 firmware, where the memory issue is fixed. My Eap653 Accesspoints are now running stable since 2 weeks without reboot.
The fix will be part of the next official firmware release for 653 Accesspoints.
Thanks all for help!
- Copy Link
- Report Inappropriate Content
Hello @marcel_,
Thank you for your valued feedback and updates! Glad to hear that your concern was resolved finally.
Hope you enjoy the Internet with TP-Link products and have a great day!
- Copy Link
- Report Inappropriate Content
Hi All,
TP-Link has provide a Beta firmware to fix the issue, please check the following post for details.
EAP653 Becomes Unreachable Or Clients Fail to Connect SSIDs After Upgrading to 1.0.9 Build20230814
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 1268
Replies: 9
Voters 0
No one has voted for it yet.