thanks
- 3 Posts
- 0 Reply Likes
Posted 4 years ago
- 51 Posts
- 12 Reply Likes
- 3 Posts
- 0 Reply Likes
Michael Brado, Official Rep
- 2677 Posts
- 368 Reply Likes
using the icon to the right, with two blue revolving arrows. We have updated bug
fixes and radio performance issues in our 9.8.2.0.15 firmware just posted, to use
for further evaluation.
- 3 Posts
- 0 Reply Likes
- 4 Posts
- 0 Reply Likes
Michael Brado, Official Rep
- 2677 Posts
- 368 Reply Likes
rkscli: reboot
Rebooting... please wait.
- 4 Posts
- 0 Reply Likes
Also with the devices requirement of needing to know what to login as BEFORE the login credentials how can any of this be scripted?
- 3 Posts
- 0 Reply Likes
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
See this link:
https://github.com/bot779/ruckusconf
I don't know who else uses this (if anyone) but it works well for me.
Let me know if/what issues you have once you install it.
- 3 Posts
- 0 Reply Likes
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
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.
- 4 Posts
- 0 Reply Likes
- 3 Posts
- 0 Reply Likes
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
(and a new script that calls it)
So if (for some reason) you want the old version of ruckusconf, you should download that now before I upload new revisions.
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
You mentioned the need to reboot "specific groups" of APs.
I had an issue where some APs (always the same 2 models of AP) would have their 5-Gig radios stop working.
Do you need something that would detect a fault like this and only reboot those APs or did you want to create a static list of APs and always reboot only those APs?
I've got a script called "rebootat3am" that will wait 'till 3:30am the next morning and then reboot all APs.
I only ran that script briefly because it seemed to increase the behavior where the APs would all "guess" the same channel (after the reboot) and then spend time "detecting interference" and jumping between channels.
If "rebootat3am" is what you guys want, I'll upload that.
(but beware of the consequences)
Then (If that works for you) I should be able to tweak things to make it reboot all APs at every 3:30am.
If you want to reboot just a few APs, I should probably modify the script to do that.
- 27 Posts
- 0 Reply Likes
Michael Brado, Official Rep
- 2630 Posts
- 359 Reply Likes
- 27 Posts
- 0 Reply Likes
- 6 Posts
- 1 Reply Like
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.
- 27 Posts
- 0 Reply Likes
- 6 Posts
- 1 Reply Like
- 27 Posts
- 0 Reply Likes
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
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
- 2663 Posts
- 368 Reply Likes
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
- 4 Posts
- 0 Reply Likes
Bill Burns, AlphaDog
- 203 Posts
- 42 Reply Likes
http://webchat.freenode.net/
and join the "ruckus" channel.
- 6 Posts
- 2 Reply Likes
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".
- 6 Posts
- 2 Reply Likes
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!
- 6 Posts
- 2 Reply Likes
If I get to it, I'll be sure to create a Repository on Github and to post a URL/Link here.
Related Categories
-
ZoneDirector
- 2443 Conversations
- 675 Followers
-
Ruckus Indoor APs
- 1562 Conversations
- 641 Followers