Archer AX20 - doesn't complete boot cycle with configured "Reboot Schedule"
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi Community specialists,
I have purchased an Archer AX20 (AX1800) router not too long ago.
I have configured "Reboot Schedule" feature to reboot the router once a week (to clear the cache, DHCP leases, etc.).
The router does reboot on schedule, but it only powers off and doesn't complete the boot cycle. There is no WiFi available, and no LEDs are lighting. The router remains powered off until I manually power cycle it (by the Power On/Off button).
The NTP is configured and shows correct time.
The latest firmware is installed.
It happened twice already and looks fairly easy to reproduce (just set "Reboot Schedule" and play around with the system time).
It looks like a bug to me, maybe just a wrong command used for the reboot upon schedule.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
To anyone who will find this thread in the future - the issue was resolved by disabling the "Reboot Schedule" setting, saving and then re-enabling the setting again.
The issue was with initially saving the "Reboot Schedule" configuration and it prevented proper functionality. It was confirmed by TP-Link support team (over email):
It seems that when you set the Reboot Schedule, some errors occurred while writing to the cache on the router, so when you rewrite the Reboot Schedule, this issue was resolved.
So simply disabling, saving and then re-enabling again has rewritten the corrupt configuration. I assume the same can occur with other settings too.
Everything works fine now.
- Copy Link
- Report Inappropriate Content
Hello,
Do you mean when your AX20 reboots at 07:00 am, the router is actually off with no lights at all and you need to manually press the Power ON/OFF button to turn it on?
How long have you been testing this Auto-Reboot feature and reproduces twice now?
Have you tried to reset the router and reconfigure it from scratch to confirm again, leave other advanced settings by default? Just ensure there are no other features in your network that might have a conflict with it.
Thanks a lot~
- Copy Link
- Report Inappropriate Content
Do you mean when your AX20 reboots at 07:00 am, the router is actually off with no lights at all and you need to manually press the Power ON/OFF button to turn it on?
At the scheduled time (07:00 AM) the router turns off, that is correct. To restore functionality I need to power cycle it. It means I have to manually press the Power button twice - first press powers the router off, second press powers the router on. After that the router boots correctly.
How long have you been testing this Auto-Reboot feature and reproduces twice now?
I have the router for a bit over two weeks, so the issue happened 2 out of 2 times the router was scheduled to reboot. 100% reproduction rate.
Have you tried to reset the router and reconfigure it from scratch to confirm again, leave other advanced settings by default? Just ensure there are no other features in your network that might have a conflict with it.
I'm unable to conduct such tests, as multiple users relay on the network, including working from home.
I can share my router configuration for your review and disable certain features if you see fit. I also can't think of any "feature" that can cause such behaviour. The router is rebooted fine if I trigger this action manually, only the scheduled reboot doesn't work.
- Copy Link
- Report Inappropriate Content
Thanks a lot for your detailed information then.
We will contact you and test this feature on our side, please check your email box and respond.
Good days.
- Copy Link
- Report Inappropriate Content
To anyone who will find this thread in the future - the issue was resolved by disabling the "Reboot Schedule" setting, saving and then re-enabling the setting again.
The issue was with initially saving the "Reboot Schedule" configuration and it prevented proper functionality. It was confirmed by TP-Link support team (over email):
It seems that when you set the Reboot Schedule, some errors occurred while writing to the cache on the router, so when you rewrite the Reboot Schedule, this issue was resolved.
So simply disabling, saving and then re-enabling again has rewritten the corrupt configuration. I assume the same can occur with other settings too.
Everything works fine now.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1239
Replies: 4
Voters 0
No one has voted for it yet.