<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;random canopy SM hang until AP reboot.&#x27; in forum &#x27;Wireless Service Providers&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/random-canopy-SM-hang-until-AP-reboot-28006005</link>
<description></description>
<language>en</language>
<pubDate>Mon, 20 May 2013 01:05:51 EDT</pubDate>
<lastBuildDate>Mon, 20 May 2013 01:05:51 EDT</lastBuildDate>

<item>
<title>Re: random canopy SM hang until AP reboot.</title>
<link>http://www.dslreports.com/forum/Re-random-canopy-SM-hang-until-AP-reboot-28008522</link>
<description><![CDATA[wirelessdog posted : Funny, I had this issue until I upgraded to 10.5 lol]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-random-canopy-SM-hang-until-AP-reboot-28008522</guid>
<pubDate>Wed, 13 Feb 2013 20:57:16 EDT</pubDate>
</item>

<item>
<title>random canopy SM hang until AP reboot.</title>
<link>http://www.dslreports.com/forum/random-canopy-SM-hang-until-AP-reboot-28006005</link>
<description><![CDATA[mindthefz posted : Hello!,<br><br>I recently acquired a WISP which is running only on Motorola (Cambium) Canopy. The installed equipment (SM's and AP's) are a mix of old and "new" hardware (P8,P9,P10). <br><br>Most of the hardware scheduled equipment, in this case the AP's, were running firmware version 8.2.4. <br><br>In order to keep things current I decided to upgrade to the latest available FW around the web. (the best I could find was 10.5).<br><br>I followed the recommended upgrade path for both the AP and the SM's. <br><br>Everything worked fine until one day a client called complaining of lack of service. When I verified in the sessions list in the AP, the SM was registered and without a single re-reg.<br><br>I tried to access the SM over management IP and directly from the session list and it didn't let me access the SM. <br><br>The client told me he tried rebooting the SM on his side but it didn't solve the problem. <br><br>Then we proceeded to reboot the AP and then the client's SM was reachable again over management IP and the sessions url.<br><br>This behavior only happens with the AP's which were upgraded. It doesn't matter if the hardware platform is P9 or P10 on the SM or the AP. <br><br>Its kind of recurrent as well. It does happen at least once or twice a month on random intervals. <br><br>Also I have to mention that Ive tried downgrading to other FW such as (10.3, 10.2, 9.5, 9.3)  etc. and the problem still persists.<br><br>So if anyone have experienced this problem or I'm missing something please do advice how to solve it.<br><br>Thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/random-canopy-SM-hang-until-AP-reboot-28006005</guid>
<pubDate>Wed, 13 Feb 2013 09:03:49 EDT</pubDate>
</item>

</channel>
</rss>
