Is there a way to script a reboot on the R700?s like a cronjob that resets them at a given time, or every 24 hours, i find the double in performance after a reboot. I have 8 R700's on a zone director 3000 and one standalone (elsewhere)
thanks
thanks
Posted 4 years ago
Michael Brado, Official Rep
Michael Brado, Official Rep
Sean, we have a ZD feature request pending to allow AP commands to an AP-Group rather than single AP or all connected APs (FR-1094). If you determine the IP address of the APs you wish to reboot by whatever scripting method, the AP CLI command to do so is 'reboot'.
rkscli: reboot
Rebooting... please wait.
I have a RuckusZD3000 controller, from the controller is there a way to reboot multiple AP's at the same time and schedule the reboot for off hours?
Also with the devices requirement of needing to know what to login as BEFORE the login credentials how can any of this be scripted?
Also with the devices requirement of needing to know what to login as BEFORE the login credentials how can any of this be scripted?
(Edited)
Hi Michael,
Any news about running commands to an AP-Group rather than a single AP or all connected APs?
Bill Burns, AlphaDog
Bill Burns, AlphaDog
If you look at the ruckusconf script here:
https://github.com/bot779/ruckusconf/blob/master/ruckusconf
You'll see a few examples embedded in the "source" of the script itself.
If you're specifically looking for an example of rebooting an individual AP though the controller, here it is:
./ruckusconf --debug --command 'rksap_cli -a 24:c9:a1:29:47:a0 "reboot"' 192.168.3.180
In this example, the IP refers to your controller and the MAC address refers to your AP.
The commandline would be very different if you wanted to use ruckusconf to contact the AP directly. (as opposed to going through the controller)
That (I believe) would be:
./ruckusconf --ap --command "reboot" 192.168.3.99
where the IP refers to the AP and not the controller.
Also, I've got some new code that allows me to schedule commands on the controller without using cron, so I don't have to embed passwords into a cron job.
If there's interest in that, I could post it as well.
https://github.com/bot779/ruckusconf/blob/master/ruckusconf
You'll see a few examples embedded in the "source" of the script itself.
If you're specifically looking for an example of rebooting an individual AP though the controller, here it is:
./ruckusconf --debug --command 'rksap_cli -a 24:c9:a1:29:47:a0 "reboot"' 192.168.3.180
In this example, the IP refers to your controller and the MAC address refers to your AP.
The commandline would be very different if you wanted to use ruckusconf to contact the AP directly. (as opposed to going through the controller)
That (I believe) would be:
./ruckusconf --ap --command "reboot" 192.168.3.99
where the IP refers to the AP and not the controller.
Also, I've got some new code that allows me to schedule commands on the controller without using cron, so I don't have to embed passwords into a cron job.
If there's interest in that, I could post it as well.
Sorry, can you give me more detail? I am not a coder so some stuff is not easy for me to understand.
Outside of Writing a Script, I will usually Reboot All of the Connected APs through the ZoneDirector Controller's CLI (via Telnet or Putty).
1.) Log into your ZoneDirector Controller, via Telnet or SSH.
2.) Type "enable" to escalate your Privileges.
3.) Type "debug" to enter Debug Mode.
4.) Use the "remote_ap_cli" Command to send a Reboot Command to All of the Connected APs, exactly as follows.
remote_ap_cli -A "reboot"
A Script would more or less mirror the aforementioned process, by outputting these Commands on your behalf.
1.) Log into your ZoneDirector Controller, via Telnet or SSH.
2.) Type "enable" to escalate your Privileges.
3.) Type "debug" to enter Debug Mode.
4.) Use the "remote_ap_cli" Command to send a Reboot Command to All of the Connected APs, exactly as follows.
remote_ap_cli -A "reboot"
A Script would more or less mirror the aforementioned process, by outputting these Commands on your behalf.
Thank you for the script I usually use it but need reboot by schedule for that reason I ask the usage of the script above. Still do not know how to integrate the script to the zonedirector. I hope get answer soon :)
You wouldn't necessarily integrate the script into ZoneDirector, itself. You would have to write the script (or have someone else write it on your behalf), then you would use a Scheduling Service, like Cron/CronTab in Unix/Linux and Task Manager in Windows to Automatically run the Script on Schedule, etc.
Thank you very much, I will try to do :)
Bill Burns, AlphaDog
Here is the scheduled AP reboot script.
https://github.com/bot779/ruckusconf/blob/master/rebootat3am
It requires the latest version of the ruckusconf script.
https://github.com/bot779/ruckusconf/blob/master/ruckusconf
"rebootat3am" should prompt you for your ruckus password, test the password by logging into your controller, wait 'till 3:30am the next day and then run the "reboot" command.
WARNING:
It is intended to reboot all of the APs connected to your controller.
This will disrupt your wifi connectivity.
Test it at a non-critical time.
In order for it to work, you will have to change the hard-coded IP address (at the end of the script) to the IP of your controller.
If you want the reboot to be scheduled at a different time, that will require editing the script.
You will need to leave this script running in a window 'till the scheduled time.
If you have any questions, let me know.
https://github.com/bot779/ruckusconf/blob/master/rebootat3am
It requires the latest version of the ruckusconf script.
https://github.com/bot779/ruckusconf/blob/master/ruckusconf
"rebootat3am" should prompt you for your ruckus password, test the password by logging into your controller, wait 'till 3:30am the next day and then run the "reboot" command.
WARNING:
It is intended to reboot all of the APs connected to your controller.
This will disrupt your wifi connectivity.
Test it at a non-critical time.
In order for it to work, you will have to change the hard-coded IP address (at the end of the script) to the IP of your controller.
If you want the reboot to be scheduled at a different time, that will require editing the script.
You will need to leave this script running in a window 'till the scheduled time.
If you have any questions, let me know.
Michael Brado, Official Rep
Thanks for sharing Bill.
Thanks Bill!
Bill Burns, AlphaDog
Let me know if that worked for you.
Unfortunately I am not a Linux guy, so my bumbling through trying to get these to work is a real headache. But I do appreciate your help and sharing your code.
Bill Burns, AlphaDog
If you want me to walk you through it, go to:
http://webchat.freenode.net/
and join the "ruckus" channel.
http://webchat.freenode.net/
and join the "ruckus" channel.
I know that I'm a couple years late on this. But, in case someone comes looking for this or similar information in the future...
In reference to the "ruckusconf" scripts (https://github.com/bot779/ruckusconf), if you prefer to use a "Windows" based system, you have a few options since the "ruckusconf" scripts appear to be written using a combination of "Linux Shell" (sh) Commands ("rebootat3am" & "buildclientos" files) and TCL (Tool Command Language) Scripts w/ the "Expect" Automation Module ("ruckusconf" file), etc.
1.) Use "Cygwin" to run the Linux based scripts (https://cygwin.com), which comes w/ the "Linux Shell" (sh). You will also need to install the "TCL", "Expect" & "SSH Client" Packages/Components, using the "Cygwin Package Manager".
In reference to the "ruckusconf" scripts (https://github.com/bot779/ruckusconf), if you prefer to use a "Windows" based system, you have a few options since the "ruckusconf" scripts appear to be written using a combination of "Linux Shell" (sh) Commands ("rebootat3am" & "buildclientos" files) and TCL (Tool Command Language) Scripts w/ the "Expect" Automation Module ("ruckusconf" file), etc.
1.) Use "Cygwin" to run the Linux based scripts (https://cygwin.com), which comes w/ the "Linux Shell" (sh). You will also need to install the "TCL", "Expect" & "SSH Client" Packages/Components, using the "Cygwin Package Manager".
(Edited)
2.) Use the "Active TCL" (https://www.activestate.com/activetcl) and the included "Teapot" (TCL Package Manager) to install the "Expect" Module, via the Command Line Interface (cmd).
You will also need an "SSH Client" to Remotely Connect to your "Ruckus" Device. a couple options are "OpenSSH" (http://www.mls-software.com/opensshd.html) and/or the "Putty" SSH/Telnet Client Suite (http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). Download the "Putty" .zip file, which contains all of the "Putty" applications, as you're going to need "Plink" to Automate the SSH Connection.
You can then replace the "Linux Shell" (sh) Commands w/ "Windows/DOS" Commands or use a Scripting Language, such as the previously installed "TCL" or perhaps "Perl/Python". Both "Perl" & "Python" have their own variations of the "Expect" Module (Expect, WinExpect, wExpect, pExpect, etc).
In my opinion, the simplest route is likely to go w/ option #1 (Cygwin), since everything can be installed using the "Cygwin Package Manager" (TCL, Expect, SSH, etc). However, I personally use option #2 (TCL w/ Expect Module, OpenSSH & Putty/Plink, along w/ cmd/vbscript & occasionally Python/pExpect or Perl/Expect).
Hope I was able to offer some additional insight!
You will also need an "SSH Client" to Remotely Connect to your "Ruckus" Device. a couple options are "OpenSSH" (http://www.mls-software.com/opensshd.html) and/or the "Putty" SSH/Telnet Client Suite (http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). Download the "Putty" .zip file, which contains all of the "Putty" applications, as you're going to need "Plink" to Automate the SSH Connection.
You can then replace the "Linux Shell" (sh) Commands w/ "Windows/DOS" Commands or use a Scripting Language, such as the previously installed "TCL" or perhaps "Perl/Python". Both "Perl" & "Python" have their own variations of the "Expect" Module (Expect, WinExpect, wExpect, pExpect, etc).
In my opinion, the simplest route is likely to go w/ option #1 (Cygwin), since everything can be installed using the "Cygwin Package Manager" (TCL, Expect, SSH, etc). However, I personally use option #2 (TCL w/ Expect Module, OpenSSH & Putty/Plink, along w/ cmd/vbscript & occasionally Python/pExpect or Perl/Expect).
Hope I was able to offer some additional insight!
(Edited)
Anyways, if I have some time, I might just re-write the "ruckusconf" scripts for Windows usage, myself.
If I get to it, I'll be sure to create a Repository on Github and to post a URL/Link here.
If I get to it, I'll be sure to create a Repository on Github and to post a URL/Link here.
