<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Need a way to reboot 7982 APs after hours every two weeks. in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15631#M4100</link>
    <description>1. 3.6.0.0.709&lt;BR /&gt;2. Controller reports the APs are offline, can ping the AP sometimes, APs will for a time show up on the controller off and on, sometimes I can "catch" an AP and get it to reboot from the controller interface, If I wait too long I have to reboot them manually. Sometimes I can SSH into and AP, if I can get TOP to come up the load average is usually over 8.&lt;BR /&gt;3. I am on a routed(10 sites) network, running a Virtual SmartZone controller(3.6.0.0.510), I am currently running&amp;nbsp; 181 APs, a mixture of 7982s and 710s.&lt;BR /&gt;4. No the clients can't use the AP when it becomes unresponsive.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;This started happening about a month after I upgraded from 3.2.1.0.659-&amp;gt;3.5.1.0.419 and has persisted through 3.5.1.0.419-&amp;gt;3.5.1.0.1010 and 3.5.1.0.1010-&amp;gt;3.6.0.0.709.&lt;BR /&gt;&lt;BR /&gt;See Case 00562204 for the failed attempt by support to fix the problem.</description>
    <pubDate>Tue, 16 Jan 2018 15:35:52 GMT</pubDate>
    <dc:creator>douglas_hall_ik</dc:creator>
    <dc:date>2018-01-16T15:35:52Z</dc:date>
    <item>
      <title>Need a way to reboot 7982 APs after hours every two weeks.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15629#M4098</link>
      <description>After about 3 weeks of operation my 7982s are becoming unresponsive and I have to reboot them to get them operational again(yes I have contacted support, after 3 weeks of BS and two rev updates I am still no farther along). I see there are script capabilities for the APs, can I use this functionality to reboot my 7982s after hours every two weeks or so?</description>
      <pubDate>Fri, 12 Jan 2018 23:21:11 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15629#M4098</guid>
      <dc:creator>douglas_hall_ik</dc:creator>
      <dc:date>2018-01-12T23:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: Need a way to reboot 7982 APs after hours every two weeks.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15630#M4099</link>
      <description>Hi Douglas,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; What code/version are you running on your APs, and what do you mean by "unresponsive"?&lt;BR /&gt;Are you on a flat LAN with a couple standalone or ZD/SZ managed APs?&amp;nbsp; Can you still ping&lt;BR /&gt;your APs from the LAN when they appear to be in a problem state?&amp;nbsp; I'm curious, as I haven't&lt;BR /&gt;heard of this behavior.&amp;nbsp; Does it seem that clients can still use the WLANs, whether you can&lt;BR /&gt;talk to the APs?</description>
      <pubDate>Fri, 12 Jan 2018 23:45:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15630#M4099</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-01-12T23:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Need a way to reboot 7982 APs after hours every two weeks.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15631#M4100</link>
      <description>1. 3.6.0.0.709&lt;BR /&gt;2. Controller reports the APs are offline, can ping the AP sometimes, APs will for a time show up on the controller off and on, sometimes I can "catch" an AP and get it to reboot from the controller interface, If I wait too long I have to reboot them manually. Sometimes I can SSH into and AP, if I can get TOP to come up the load average is usually over 8.&lt;BR /&gt;3. I am on a routed(10 sites) network, running a Virtual SmartZone controller(3.6.0.0.510), I am currently running&amp;nbsp; 181 APs, a mixture of 7982s and 710s.&lt;BR /&gt;4. No the clients can't use the AP when it becomes unresponsive.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;This started happening about a month after I upgraded from 3.2.1.0.659-&amp;gt;3.5.1.0.419 and has persisted through 3.5.1.0.419-&amp;gt;3.5.1.0.1010 and 3.5.1.0.1010-&amp;gt;3.6.0.0.709.&lt;BR /&gt;&lt;BR /&gt;See Case 00562204 for the failed attempt by support to fix the problem.</description>
      <pubDate>Tue, 16 Jan 2018 15:35:52 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15631#M4100</guid>
      <dc:creator>douglas_hall_ik</dc:creator>
      <dc:date>2018-01-16T15:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: Need a way to reboot 7982 APs after hours every two weeks.</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15632#M4101</link>
      <description>Anybody have any ideas or any other forums that might help?</description>
      <pubDate>Wed, 17 Jan 2018 22:58:46 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Need-a-way-to-reboot-7982-APs-after-hours-every-two-weeks/m-p/15632#M4101</guid>
      <dc:creator>douglas_hall_ik</dc:creator>
      <dc:date>2018-01-17T22:58:46Z</dc:date>
    </item>
  </channel>
</rss>

