Asus AI Mesh Network Reset By Itself Today! Did This Happen to Anyone Else?

scso1502

New Around Here
Today several of my AI Mesh nodes (2x RT-AC68U and 2x AC-1900) lost connectivity to the Main GT-AC5300 network. I restarted the entire network including the Verizon LTE modem they attach to and they upon doing so, I found the main GT-AC5300 had been reset to factory defaults. I never did this! Has anyone else had this happen to them today? Was their an update that did this?

I don't understand the log entries but I do have them in case something weird happens like this. Maybe someone with a brain can interpret the below info and tell me if something happened to cause this.

May 24 02:06:49 rc_service: ntp 1640:notify_rc restart_diskmon
May 24 02:06:49 disk_monitor: Finish
May 24 02:06:49 disk monitor: be idle
May 24 02:07:18 crond[1289]: time disparity of 2131021 minutes detected
May 24 02:08:38 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7642)]periodic_check AM 4:38
May 24 02:08:38 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7681)]do webs_update
May 24 02:08:51 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7699)]retrieve firmware information
May 24 02:08:51 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7708)]default status
May 24 02:09:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7681)]do webs_update
May 24 02:09:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7699)]retrieve firmware information
May 24 02:09:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7708)]default status
May 24 02:09:51 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7681)]do webs_update
May 24 02:09:51 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7699)]retrieve firmware information
May 24 02:09:51 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7708)]default status
May 24 02:20:21 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
May 24 02:20:23 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 10 mbps half duplex
May 24 02:20:44 acsd: selected channel spec: 0x1806 (4l)
May 24 02:20:44 acsd: Adjusted channel spec: 0x1806 (4l)
May 24 02:20:44 acsd: selected channel spec: 0x1806 (4l)
May 24 02:20:44 acsd: acs_set_chspec: 0x1806 (4l) for reason APCS_CSTIMER
May 24 02:20:45 acsd: selected channel spec: 0xe22a (44/80)
May 24 02:20:45 acsd: Adjusted channel spec: 0xe22a (44/80)
May 24 02:20:45 acsd: selected channel spec: 0xe22a (44/80)
May 24 02:20:46 acsd: selected channel spec: 0xe29b (157/80)
May 24 02:20:46 acsd: Adjusted channel spec: 0xe29b (157/80)
May 24 02:20:46 acsd: selected channel spec: 0xe29b (157/80)
May 24 02:30:41 acsd: eth6: NONACSD channel switching to channel spec: 0x1806 (4l)
May 24 02:35:47 acsd: selected channel spec: 0xe22a (44/80)
May 24 02:35:47 acsd: Adjusted channel spec: 0xe22a (44/80)
May 24 02:35:47 acsd: selected channel spec: 0xe22a (44/80)
May 24 02:35:47 acsd: selected channel spec: 0xe29b (157/80)
May 24 02:35:47 acsd: Adjusted channel spec: 0xe29b (157/80)
May 24 02:35:47 acsd: selected channel spec: 0xe29b (157/80)
May 24 02:45:44 acsd: selected channel spec: 0x1906 (8u)
May 24 02:45:44 acsd: Adjusted channel spec: 0x1906 (8u)
May 24 02:45:44 acsd: selected channel spec: 0x1906 (8u)
May 24 02:45:44 acsd: acs_set_chspec: 0x1906 (8u) for reason APCS_CSTIMER
May 24 02:50:48 acsd: selected channel spec: 0xe22a (44/80)
May 24 02:50:48 acsd: Adjusted channel spec: 0xe22a (44/80)
May 24 02:50:48 acsd: selected channel spec: 0xe22a (44/80)
May 24 02:50:49 acsd: selected channel spec: 0xe29b (157/80)
May 24 02:50:49 acsd: Adjusted channel spec: 0xe29b (157/80)
May 24 02:50:49 acsd: selected channel spec: 0xe29b (157/80)
May 24 03:00:45 acsd: selected channel spec: 0x1906 (8u)
May 24 03:00:45 acsd: Adjusted channel spec: 0x1906 (8u)
May 24 03:00:45 acsd: selected channel spec: 0x1906 (8u)
May 24 03:00:45 acsd: acs_set_chspec: 0x1906 (8u) for reason APCS_CSTIMER
May 24 03:05:50 acsd: selected channel spec: 0xe22a (44/80)
May 24 03:05:50 acsd: Adjusted channel spec: 0xe22a (44/80)
May 24 03:05:50 acsd: selected channel spec: 0xe22a (44/80)
May 24 03:05:51 acsd: selected channel spec: 0xe29b (157/80)
May 24 03:05:51 acsd: Adjusted channel spec: 0xe29b (157/80)
May 24 03:05:51 acsd: selected channel spec: 0xe29b (157/80)
May 24 03:15:49 acsd: selected channel spec: 0x1906 (8u)
May 24 03:15:49 acsd: Adjusted channel spec: 0x1906 (8u)
May 24 03:15:49 acsd: selected channel spec: 0x1906 (8u)
May 24 03:15:49 acsd: acs_set_chspec: 0x1906 (8u) for reason APCS_CSTIMER
May 24 03:18:10 wlceventd: wlceventd_proc_event(527): eth7: Auth E6:ED:CB:31:40:1A, status: Successful (0), rssi:0
May 24 03:18:10 wlceventd: wlceventd_proc_event(556): eth7: Assoc E6:ED:CB:31:40:1A, status: Successful (0), rssi:0
May 24 03:18:37 wlceventd: wlceventd_proc_event(527): eth6: Auth 14:F6:D8:A1:31:A5, status: Successful (0), rssi:0
May 24 03:18:37 wlceventd: wlceventd_proc_event(556): eth6: Assoc 14:F6:D8:A1:31:A5, status: Successful (0), rssi:0
May 24 03:19:12 rc_service: httpd 1292:notify_rc start_autodet
May 24 03:19:14 rc_service: httpd 1292:notify_rc start_webs_update
May 24 03:19:29 rc_service: httpd 1292:notify_rc start_autodet
May 24 03:19:31 rc_service: httpd 1292:notify_rc start_webs_update
May 24 03:20:47 rc_service: httpd 1292:notify_rc chpass;restart_time;restart_upnp;restart_usb_idle;restart_bhblock;restart_ftpsamba;
May 24 03:20:47 kernel: klogd started: BusyBox v1.24.1 (2022-03-28 09:24:25 CST)
May 24 03:20:48 miniupnpd[1656]: shutting down MiniUPnPd
May 24 03:20:48 hour monitor: daemon is starting
May 24 03:20:48 hour monitor: daemon terminates
May 24 03:20:48 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
May 24 03:20:48 FTP Server: daemon is stopped
May 24 03:20:48 miniupnpd[17514]: HTTP listening on port 45227
May 24 03:20:48 Samba Server: smb daemon is stoped
May 24 03:20:48 miniupnpd[17514]: Listening for NAT-PMP/PCP traffic on port 5351
May 24 03:20:48 rc_service: httpd 1292:notify_rc restart_firewall
May 24 03:20:49 lldpd[17579]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May 24 03:20:49 lldpd[17579]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
May 24 03:20:50 rc_service: httpd 1292:notify_rc chpass;restart_time;restart_wireless;restart_cfgsync
May 23 21:20:51 kernel: klogd started: BusyBox v1.24.1 (2022-03-28 09:24:25 CST)
May 23 21:20:51 rc_service: watchdog 1302:notify_rc start_cfgsync
May 23 21:20:51 rc_service: waitting "chpass;restart_time;restart_wireless;restart_cfgsync" via httpd ...
May 23 21:20:51 hour monitor: daemon is starting
May 23 21:20:51 hour monitor: daemon terminates
May 23 21:20:52 kernel: Bonding Port enabled mask 0x000c
May 23 21:20:52 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1 --> 5 ] [ 2, 3, 7 --> 8 ]
May 23 21:20:54 wlceventd: main(961): wlceventd Start...
May 23 21:20:55 acsd: selected channel spec: 0x1008 (8)
May 23 21:20:55 acsd: Adjusted channel spec: 0x1008 (8)
May 23 21:20:55 acsd: selected channel spec: 0x1008 (8)
May 23 21:20:55 acsd: acs_set_chspec: 0x1008 (8) for reason APCS_INIT
May 23 21:20:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 84:20:96:33:43:C1, status: Successful (0), rssi:0
May 23 21:20:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 84:20:96:33:43:C1, status: Successful (0), rssi:0
May 23 21:20:55 acsd: selected channel spec: 0xe22a (44/80)
May 23 21:20:55 acsd: Adjusted channel spec: 0xe22a (44/80)
May 23 21:20:55 acsd: selected channel spec: 0xe22a (44/80)
May 23 21:20:55 acsd: acs_set_chspec: 0xe22a (44/80) for reason APCS_INIT
May 23 21:20:56 acsd: selected channel spec: 0xe29b (157/80)
May 23 21:20:56 acsd: Adjusted channel spec: 0xe29b (157/80)
May 23 21:20:56 acsd: selected channel spec: 0xe29b (157/80)
May 23 21:20:56 acsd: acs_set_chspec: 0xe29b (157/80) for reason APCS_INIT
May 23 21:20:57 wlceventd: wlceventd_proc_event(527): eth6: Auth 14:F6:D8:A1:31:A5, status: Successful (0), rssi:0
May 23 21:20:57 wlceventd: wlceventd_proc_event(556): eth6: Assoc 14:F6:D8:A1:31:A5, status: Successful (0), rssi:0
May 23 21:21:06 roamast: ROAMING Start...
May 23 21:21:23 wlceventd: wlceventd_proc_event(527): eth6: Auth 3A:D1:02:BB:47:51, status: Successful (0), rssi:0
May 23 21:21:23 wlceventd: wlceventd_proc_event(556): eth6: Assoc 3A:D1:02:BB:47:51, status: Successful (0), rssi:0
May 23 21:23:46 rc_service: cfg_server 17754:notify_rc restart_obd_monitor

I'm setting everything up again from scratch, but this is a time waster after a long day of work and I'd like to know what caused it.

I hope everyone is doing well and thanks in advance to anyone willing to look.
 

L&LD

Part of the Furniture
I hope you did a full reset yourself after flashing the latest firmware onto the router before setting it up again (even if it is the same firmware version available, flash/upgrade it again).

The GT-AC5300 may be showing hardware issues, consider a replacement if a fully reset router/network doesn't fix this issue permanently.

If you're using 5-8 of the LAN ports, you may want to try using the router without using those ports.
 

scso1502

New Around Here
Thanks for the tips. Judging by the lack of responses here, I can only assume this issue was isolated to me. I'm am currently only using 3 of the router's ethernet ports, but that could change. I've used up to 7 at one time previously before moving and never noted any problems. I see others had issues with the ports of their GT-5300 but the issues appear to be isolated and not wide-spread, though I didn't thorough research this. Is there something I need to be aware of if using too many of the ports?

Take care...
 

L&LD

Part of the Furniture
If using port 5-8 work well well in your setup, then there is nothing to be concerned about, of course.

However, I haven't seen an Asus 8 Port (LAN) router that remains stable for its lifetime. The main issue is that the 8 ports are really two separate switches, and the way they are connected together, they are not the most robust configuration possible.

A $10 or $20 5 or 8 Port switch plugged into ports 1-4 solves that issue.

Also, note that the router's power supply may be going south on you. It may be worthwhile to test with a new or known/good power adaptor (same plug, Voltage, and equal or higher Amperage specifications).

Knowing what I know though (performance difference between AC and AX routers), I would be more inclined to consider a new AX class router instead.

Current Order of Recommended Routers Late 2021
 

scso1502

New Around Here
Many thanks L&LD, I really appreciate that additional info. I'm a huge fan of Asus routers. Been using and installing them for well over 10 years after testing most other brands and finding they suck compared to Asus. I'll take that advice and check on the power supply. I like this router and it's been good to me for the past 3 or so years. Hoping it will last.

Have a good week and thanks again,
Mike
 

Luboslav

New Around Here
I have aimesh with main RT-AC68U and 2 RT-AC68U nodes + 2 Zen Wifi CD6 (ac1500) nodes. Few days ago I noticed, that one CD6 node lost connectivity and didnt work even after reboot. I have tried it several times without success, so I had to reset it and re-join aimesh. Then I realized, that at the time it happened, I have used my welding machine very intensively for a few hours and it was connected to the same power line (same phase and fuse) as my node. I believe, that this was the reason for reseting my node. I am mentioning it because sometimes we don't think about external influences only trying to find the reason inside HW/SW in our box.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top