ER605 v2.0 - Consistantly becoming Unresponsive
ER605 v2.0 - Consistantly becoming Unresponsive
I know there are various other posts in this community about ER605 v2.0 (and even ER605 v1.0) talking about Disconnecting messages, and also the unit becoming unresponsive.
I've been having a very similar issue, where randomly throughout the night my whole network becomes unresponsive. I cannot plug in directly into the device and obtain an IP address anymore, the logs don't indicate any issues, other than when the disconnect happens, the log fills with client disconnect messages, followed by "Router is down". That it. If I look at the CPU/Memory load for the downtime period its blank as if the whole device is unresponsive. I've tried the following:
- I setup a nightly reboot at 3am everyday, this doesnt help
- I changed my DHCP range from 192.x to 10.x
- I've verified that my ISPs internet connection is working
I have the following hardware:
- TP-Link ER605 v2
- TP-Link Omada Hardware Controller
- 3x TP-Link EAP610 Ultra-Slim
During the time, all clients no longer are able to talk to each other, the WiFi stops responding, the network is broken. If I power cycle the router only, the whole network will begin working after it reboots.
Do I have a defective unit? I've never had such a hard time with a simple router/switch/DHCP situation. What should I do?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Giang97 How to do this?
- Copy Link
- Report Inappropriate Content
I would configure the Router to a SysLog server to see what errors are being spit out before the lock up.
You could have a chatty NIC on a device that is blowing up the error logs and blowing up the memory on the router. Maybe some type of Multicast storm. Which impart will fire off RSTP. I dont even know if the router supports spanning tree, it could be blasting your router regardless.
- Copy Link
- Report Inappropriate Content
It dropped again last night for no reason, I have all the logging sent to zabbix and there are no errors reported, just the unit stops working. Even if this was a bad device causing grief on the network (which i dont think it is), isnt this a business class unit that should be able to handle such a situation. I had no such problems with the google home device that was previously running the network for almost 6 years.
- Copy Link
- Report Inappropriate Content
Still having issues with my device, again it becomes unresponsive randomly during the night. Why doesnt the controller reboot it? Why is there no logging? Why is there no errors reported in the UI?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2328
Replies: 14
Voters 0
No one has voted for it yet.