Scripting an AP reboot via SSH / CLI

dcolpittsdcolpitts
in WiFi - Cloud Managed

We are experiencing an issue with the current AP330 firmware where the APs appear to stop passing traffic after a while (as in weeks of uptime as opposed to hours or days). Our solution thus far has been to log into WG cloud and reboot them, but since I have over 100 of them that needed rebooted, I decided I'd like to just build a script, add to Windows Task Scheduler, and have them rebooted once a week since WG does not provide a provision to do a scheduled reboot. I've tried a couple of different things including plink and posh-ssh. In both cases, once the script is connected and issues the "reboot" command, I get an error back that says "Not support for admin account." (this is not a typo on my part, that is the actual output).

Using plink, this is the command that should work:

"C:\Program Files\PuTTY\Plink.exe" -v -ssh 192.168.145.229 -l admin -pw "clear_text_pass" -batch reboot

Using Posh-SSH, it should be this:

$User = "admin"
$PWord = ConvertTo-SecureString -String "clear_text_pass" -AsPlainText -Force
$UserCredential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $User, $PWord
New-SSHSession -ComputerName 192.168.145.229 -Credential $UserCredential -Verbose
Invoke-SSHCommand -SessionId 0 reboot
Remove-SSHSession -SessionId 0

But neither work and exit with "Not support for admin account."

Has anyone been successful yet in scripting a reboot?

dcc

Comments

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @dcolpitts
    There is a feature request to allow scheduled/recurring reboots via WatchGuard Cloud -- that is feature request AP-1277.

    If you'd like to follow this request so that you're updated of any changes or a release, please create a support case and mention AP-1277.

    -James Carson
    WatchGuard Customer Support

  • bfife4bfife4

    dcolpitts, plase know you are not alone in asking for a scheduled reboot of AP units. We've been asking for this since July 2024 because SOME units will just stop passing traffic until rebooted. We have 400 units deployed (more to come) so a couple of my staff are tasked with rebooting them on a scheduled basis.

  • dcolpittsdcolpitts

    I don't know if you are using POE Injectors vs POE switches, but if decent managed POE switches with a cli that accepts scripts, you can probably just toggle off and on the POE on all the ports once a week to cause a mass reboot. Not ideal, but effective.

    dcc

Sign In to comment.