AIMesh System Reboot via ssh?

[jplw]

With stock 388 firmware, is it possible to login to an AIMesh router and issue a command to do an AIMesh system reboot? In other words, reboot both the Router and nodes. The "reboot" command reboots only the router. I know one can ssh into each node and reboot them, but since the GUI has AIMesh->System Settings->System Reboot, I am wondering whether there is an SSH command that does the same thing.

 

[drabisan]

If you schedule a reboot from router's web interface reboots the node(s). From SSH you can't simply reboot everything in one shot. You can write a small script that SSH into each node, reboot and at the end reboot the router.

 

[jplw]

While it is true that a scheduled roboot reboots the router and nodes, it is NOT the same thing as an AIMesh "system reboot". After a scheduled reboot, my guest network is not emitted properly from the node--which is the only reason I use AIMesh. A system reboot always fixes this.

 

[L&LD]

A scheduled reboot shouldn't be used to fix a (real or potential) issue. The root cause (if there is one) should be fixed instead.

 

[jplw]

I could not agree more...but Asus has not fixed the 3.0.0.4.388_22525 firmware on my RT-AX3000 router. It throws "Could not allocate requested buffers" errors then stops working, 2-30 days after reboot. I reported the problem to them within days of the firmware coming out. I even replaced the router under warantee but the problem persists. What choice to I have other thsn to reboot periodically?

 

[drinkingbird]

I could not agree more...but Asus has not fixed the 3.0.0.4.388_22525 firmware on my RT-AX3000 router. It throws "Could not allocate requested buffers" errors then stops working, 2-30 days after reboot. I reported the problem to them within days of the firmware coming out. I even replaced the router under warantee but the problem persists. What choice to I have other thsn to reboot periodically?

Try just rebooting the nodes followed by rebooting the main router. Not exactly sure what the "system reboot" does but seems like that would be the same thing?

 

[L&LD]

Did you do a full reset without using a saved backup config file? And without plugging in a USB drive that was previously used for amtm and/or other scripts?

Did you use a saved backup config file between different routers?

Did you try a complete reset without configuring anything, and seeing if the issue is still there? Keep good notes on your progress during setup to see where it actually fails.

You can also only reboot manually, when needed.

Another choice you have is to use older firmware, but that is the last thing I would ever do.

 

[jplw]

Try just rebooting the nodes followed by rebooting the main router. Not exactly sure what the "system reboot" does but seems like that would be the same thing?

That is what the scheduled reboot did...it rebooted the node then rebooted the router...but the Guest network on the node did not work after that.

 

[jplw]

Did you do a full reset without using a saved backup config file? And without plugging in a USB drive that was previously used for amtm and/or other scripts?

Did you use a saved backup config file between different routers?

Did you try a complete reset without configuring anything, and seeing if the issue is still there? Keep good notes on your progress during setup to see where it actually fails.

You can also only reboot manually, when needed.

Another choice you have is to use older firmware, but that is the last thing I would ever do.

With my first router, the problem occurred with the previous 388 firmware as well, which is what led to the warantee replaacement. I have tried only the current firmware on the new router. I never ever reload configuration files. I configured from scratch when I got it, factory resetting after updating to the current firmware. I have to run it for at least several days for the problem to recur, which I cannot do because it will not work for me without configuration. I have provideded ASUS with a complete log of the 30 days from first run until the problem occured on my new router. I have my own syslog server so I have captured all logs from both the router and the node.

 

[drinkingbird]

That is what the scheduled reboot did...it rebooted the node then rebooted the router...but the Guest network on the node did not work after that.

Guess you'll have to try and find out what that "system reboot" does. Not sure why it would be any different but there must be something. Maybe it is just the timing, you need the router to reload before the nodes come back online maybe, so it has to happen fast/almost at the same time? Try having 3 SSH windows open and the command ready to go, hit enter on all 3 in rapid sequence with the router being last.

 

[jplw]

After the scheduled reboot, I checked the uptimes of the node and the router (vi ssh). The node uptimes was 1 minute longer, suggesting to me that the node was rebooted first, then the router. After an AiMesh Syastem Reboot, the uptimes are identical. My guess is that the System Reboot propogates some data to the node, whereas just rebooting each does not. I found 2 problems with the node after the schduled reboot. 1) a Fire TV stick could not connect to it at 5GHz, but could connect at 2.4. A security camera that normally connects to the node, connected (pooorly because it is far away) to the Router instead and could not be bound to the node. After the System Reboot, everything connected and worked properly. I have asked Asus about this. I will report back if they answer.

 

[drinkingbird]

After the scheduled reboot, I checked the uptimes of the node and the router (vi ssh). The node uptimes was 1 minute longer, suggesting to me that the node was rebooted first, then the router. After an AiMesh Syastem Reboot, the uptimes are identical. My guess is that the System Reboot propogates some data to the node, whereas just rebooting each does not. I found 2 problems with the node after the schduled reboot. 1) a Fire TV stick could not connect to it at 5GHz, but could connect at 2.4. A security camera that normally connects to the node, connected (pooorly because it is far away) to the Router instead and could not be bound to the node. After the System Reboot, everything connected and worked properly. I have asked Asus about this. I will report back if they answer.

So that goes along with my theory that rebooting all 3 at the same time is what you need to do. The nodes may be coming back up while the router is still shutting down and something is getting confused/stuck. Try the reboot of all 3 at the same time via 3 SSH windows and see if it is ok, at least then you know that the only difference is timing.

 

[jplw]

Great thought. I have keys setup so I do not need to enter a password to ssh. "ssh admin@192.168.1.1 reboot" works to reboot the Router. However, the same command for the Node times out. I then opened an ssh window to the node and typed reboot...thus, it rebooted second. All was well after that. So I would say you are right...the timing matters. The router needs to be functioning when the node reboots. The scheduled reboot does node first. So I will just have to maually reboot in the right order. Thanks.!