We upgraded a bunch of PMP430s last night from 11.2 to 13.2 (going through 12.1 along the way).

We noticed that all the "half channel" (frequencies on 2.5 MHz centers) were unchecked after the update. Of course, those center frequencies did not even exist in 11.2, so I don't really consider this a bug.

Otherwise everything went swimmingly.

Kind of nice that you can update the list without a reboot.

Also really nice to be able to sort subs by signal quality (SNR/power level, speeds, etc). Really saves time.

bp
<part-15@SkylineBroadbandService>

On 11/13/2014 8:33 PM, Rajesh Vijayakumar via Af wrote:
We are investigating the issue with urgency and I will post an update as soon as we have something. The official 13.2 release build has no additional changes from build 40, so we are also surprised by this.

Rajesh Vijayakumar
Cambium Networks

On Thu, Nov 13, 2014 at 10:15 PM, George Skorup (Cyber Broadcasting) via Af <[email protected] <mailto:[email protected]>> wrote:

    Some info for Cambium on the build 32 thing. I had the SMs on that
    sector locked down to the bandwidth and frequency of the AP. This
    is where I was having a ton of registration issues and the 2+
    minute scan was a PITA. Anyway... when these SMs on 13.2 official
    tried to register to the AP when it was on build 32, ALL of them
    kept watchdog resetting over and over. I tried rebooting the AP
    first and they still did it. Updated the AP to official and they
    are calm now. I did have one SM on the AP scanning everything and
    it did not watchdog reset.

    So the scan list thing. I haven't attempted any 2.4 or 3.6 450's
    yet. Still working my way through 5GHz. I just went through every
    SM that updated and so far looks like every single one lost no 5.4
    freqs and only 5767.5 and 5807.5.

    I'm stopping for tonight because one disaster was narrowly
    averted, I don't need another one.

    Oh, plus about 90% of the APs are booting up using iGPS. But you
    guys already know about that and there's nothing I can do about
    it.. well there is but it sucks.

    On 11/13/2014 9:24 PM, George Skorup (Cyber Broadcasting) via Af
    wrote:
    13.2 on the SM definitely does not jive with build 32 on the AP.
    So.. don't do that. I forgot I still had that AP on build 32
    until it was too late. SMs would pop in session for about 2
    seconds and go down again. Luckily updating the AP to 13.2
    official fixed it.

    I'm also seeing 5GHz SMs losing freqs. But it's funny, like 99%
    of them only lose 5767.5 and 5807.5. I try to avoid the 2.5
    centers whenever I can since I've noticed exactly what you guys
    are seeing here in the past, ALL of the 2.5 centers disappear. I
    don't use 5MHz bandwidth, and I usually lock the scan list on the
    SM down to the band the AP is operating in. So maybe that's why I
    was losing only a couple freqs.

    On 11/13/2014 9:12 PM, Ryan Ray via Af wrote:
    It's crazy. No warning, no release notes about it. How does this
    come out of all the betas and you lose your SM's because a
    frequency isn't checked...

    On Thu, Nov 13, 2014 at 7:09 PM, timothy steele via Af
    <[email protected] <mailto:[email protected]>> wrote:

        Yeah I noticed that same with 5Ghz looks like they unchecked
        the rarely used channels in SM with 13.2 programmer was
        probably thinking he was helping but lots are going to complain

        —
        Sent from Mailbox <https://www.dropbox.com/mailbox>


        On Thu, Nov 13, 2014 at 10:06 PM, Ryan Ray via Af
        <[email protected] <mailto:[email protected]>> wrote:

            Just did a >200 group of SM's and the upgrade has
            removed frequencies that were previously checked. I
            followed the guide and did the SM's first and AP's last.
            Luckily the majority of these can see another AP but
            what the fuck...

            About half of these SM's were on 13.2(34) and the other
            half were on 13.1.3...

            This is what it looks like after an update

            <image.png>


            Pre update they were all

            <image.png>


            URG







Reply via email to