i like both of those ideas. try to reconnect on last AP channel, if that fails then run thru a scan
and a button in the scan list to "turn off all 2.5 center freq" would be nice also. (needs to be an snmp odi too) 2 cents On Mon, Nov 17, 2014 at 12:58 PM, Rajesh Vijayakumar via Af <af@afmug.com> wrote: > Ken, > If we know about this issue before release and documented it in the > release notes, it could have been spun as a "feature", but that opportunity > is gone now :) > > The concern is how long it takes the SM to scan for the AP on each boot > up, right? How about a flag that tell that SM that when it is rebooted, it > should first try to connect with the AP it was connected to prior to > reboot, and to initiate the scan only if that fails? Or do you need a > button that says "turn off all 2.5 center frequencies"? > > Not promising to make any enhancements as we try to make a bugfix release > for the 13.2 issues, but definitely looking for feedback on the best way(s) > to reduce the scan time. > > Rajesh Vijayakumar > Cambium Networks > > On Mon, Nov 17, 2014 at 11:59 AM, Ken Hohhof via Af <af@afmug.com> wrote: > >> I viewed it as a feature, since it’s a pain unchecking all those >> frequencies. I remembered this happening on the first release that >> introduced the 2.5 frequencies but looking at some older SMs, I guess >> that’s not true. >> >> If you’re taking this “feature” out, I hope you’re giving us an easy way >> to accomplish the same thing. >> >> >> *From:* Rajesh Vijayakumar via Af <af@afmug.com> >> *Sent:* Monday, November 17, 2014 11:41 AM >> *To:* af@afmug.com >> *Subject:* Re: [AFMUG] System Release 13.2 is Official >> >> Here is what we know till now. >> If you have not modified your scan list on the SM and it is still at the >> factory default setting, and you upgrade to 13.2, the 2.5MHz center >> frequencies will be deselected after the upgrade. This will happen with >> 2.4Hz, 5.4GHz and 5.7GHz. If the AP is configured to use the 2.5Mhz center >> frequency, the SMs will not reconnect. This issue was present on all the >> open beta builds. >> >> If your sector is using 2.5 center frequency and the SMs have the default >> scan list, DO NOT use 13.2. You can change the SM scan list to be something >> non-default, but we are working on releasing a fix for this urgently, so it >> may be easier to wait for that. >> >> Rajesh Vijayakumar >> Cambium Networks >> >> >> >> On Fri, Nov 14, 2014 at 6:51 PM, George Skorup (Cyber Broadcasting) via >> Af <af@afmug.com> wrote: >> >>> Well, then the scenario I just gave (brand-new SMs upgraded out of the >>> box) did not get the 2.5 centers selected upon upgrade. I have some more >>> 2.4's coming next week and I'll see what they do when upgraded to 13.2. My >>> guess is they are coming with 12.2.2 from the factory at this point though. >>> >>> On 11/14/2014 3:46 PM, Aaron Schneider via Af wrote: >>> >>> There was a decision made when we added 2.5 center channels that on >>> upgrade we wouldn’t automatically check the 2.5 centers unless the scan >>> list was in a default (all checked) state. We didn’t want to add a ton of >>> new scan options on an upgrade which increased the scanning time. When >>> setting a unit that is on a load that supports 2.5M centers to default, >>> then all (including 2.5 centers) should be selected. >>> >>> >>> >>> We are still investigating, but likely this has something to do with >>> what Ryan was seeing when others weren’t seeing the same behavior. >>> >>> >>> >>> -Aaron >>> >>> >>> >>> *From:* Af [mailto:af-boun...@afmug.com <af-boun...@afmug.com>] *On >>> Behalf Of *George Skorup (Cyber Broadcasting) via Af >>> *Sent:* Friday, November 14, 2014 12:58 PM >>> *To:* af@afmug.com >>> *Subject:* Re: [AFMUG] System Release 13.2 is Official >>> >>> >>> >>> I'm trying to remember.. did the 2.4 450 have 2.5 centers from day one? >>> I think the last time I got some new SMs in, they had either 12.0.x or >>> 12.1.x on them and none of the 2.5 centers were checked after updating to >>> 13.x. So maybe the safest approach from now on is to enable everything in >>> the scan list automatically during/after update? Then tell everyone in the >>> release notes about it. You'd be surprised at how many of us fully read the >>> release notes now. OK, at least I do. >>> >>> On 11/14/2014 11:28 AM, Rajesh Vijayakumar via Af wrote: >>> >>> Its good to get confirmation of multiple successful upgrades with 2.4 >>> GHz. >>> >>> We have not been able to recreate the problem yet. The test team is >>> trying a number of combinations of upgrade/downgrade. >>> >>> --Rajesh Vijayakumar >>> >>> Cambium Networks >>> >>> >>> >>> On Fri, Nov 14, 2014 at 11:01 AM, Eric Muehleisen via Af <af@afmug.com> >>> wrote: >>> >>> Any changes/improvements in the Rate Adapt? >>> >>> >>> >>> On Fri, Nov 14, 2014 at 10:54 AM, Bill Prince via Af <af@afmug.com> >>> wrote: >>> >>> As mentioned in another thread, we upgraded a bunch of PMP430 >>> installations last night. Something that I wasn't expecting was an >>> immediate improvement in the SNR (typical example below). This was pretty >>> much across the board excepting installations that already had really good >>> SNR. >>> >>> Thanks Cambium! >>> >>> >>> >>> bp >>> >>> <part-15@SkylineBroadbandService> >>> >>> >>> >>> On 11/13/2014 5:12 AM, Matt Mangriotis via Af wrote: >>> >>> It is here! >>> >>> >>> >>> We released 13.2 this morning officially. Come to our forum to discuss >>> anything about it. >>> >>> >>> >>> >>> http://community.cambiumnetworks.com/t5/PMP-450/System-Release-13-2-Now-Avaialable/m-p/36254/thread-id/278 >>> >>> >>> >>> Download the software from the usual place on our support site: >>> >>> >>> >>> https://support.cambiumnetworks.com/files/pmp450/ >>> >>> >>> >>> *Thanks* to all of you that Beta tested this software with us, and >>> helped to make it stronger and better than ever. Now that this is here, >>> we’re hard at work on delivering the next round of enhancements (code name >>> 13.3 (pretty original, huh?)) which are right around the corner. >>> >>> >>> >>> The momentum is building on the PMP 450 platform. >>> >>> >>> >>> Thanks again, >>> >>> >>> >>> Matt >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> > >
