Failing to register and popping in and out of session quickly. Yeah....
That happens on the 450 too. SMs on 12.x are screwy when talking to APs
on 13.x. I know this for a fact because we got some new 5GHz SMs in once
and the guys took them out to the field before I got a chance to upgrade
and put our defaults in. There was a point where they'd actually crash
the AP.
I think you should downgrade the APs to whatever the last 12.x release
was for the 430. The SMs already upgraded should be fine. Get all of the
SMs up to 13.whatever you want, and then upgrade the APs again.
On 6/20/2016 6:21 PM, Ken Hohhof wrote:
Yeah, I opened a support ticket, and they want remote access. Well,
duh, the problem is I lose remote access to the SMs after upgrade.
And unfortunately it is not reproducible, any given SM can exhibit a
variety of symptoms from working fine but prompting for a reboot to
unreachable until the customer power cycles it. And I don’t see any
rhyme or reason to it.
I was hoping they would tell me I was doing something wrong, like I
needed an older version of CNUT, or I should have left the APs at 12.1
until upgrading the SMs instead of taking them to 13.2. Or that it
was a known bug with 12.1 that was fixed in 12.1.2.
*From:* George Skorup <mailto:[email protected]>
*Sent:* Monday, June 20, 2016 6:02 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [AFMUG] 430 FW upgrade path (for 450 transition)
If they're successfully upgraded to 12.1 or 12.1.2, then obviously
they're taking the reboot command from CNUT. This sounds like a
problem you can reproduce over and over. I'd ask Cambium for help and
see if they could figure it out in the lab. I wouldn't want to have to
call 100+ customers and have them reboot their radios either.
On 6/20/2016 4:41 PM, Ken Hohhof wrote:
Cambium support came back that you can go from 11.2 to 12.1.2.
But that doesn’t seem to solve my problem, and the problem does not
seem to be unchecked frequencies. Rather, the SMs are not rebooting
after the upgrade, they are wanting a manual reboot. Sure enough,
you log into them, they say they are on 12.1 FW, but prompt you for a
reboot.
But some of them won’t register properly until you reboot them. If
they constantly rereg and only register fleetingly, sometimes I’m
able to log in long enough to do the reboot. I’ve had at least one
that I had to have the customer power cycle the SM. I was scared to
do this, but it worked.
I don’t want to upgrade hundreds of SMs and randomly have some that I
need to have the customer power cycle them, and others that I try and
try until I catch it registered long enough to log in and reboot.
FWIW, the next step to 13.4.1 has gone without a hitch. It’s getting
to 12.1 or 12.1.2 where the auto reboot fails. Oh, the APs did this
also, but it seemed cosmetic, it seemed they actually did reboot and
worked fine.
*From:* George Skorup <mailto:[email protected]>
*Sent:* Monday, June 20, 2016 11:54 AM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [AFMUG] 430 FW upgrade path (for 450 transition)
What Ken is worried about (because I've chatted off-list with him) is
that release (or series of releases) where some frequencies get
unchecked from the SM scan list.
Here you go Ken. 12.1.1 was the bad one. The only thing I don't
remember is if you have to hit 12.2.2 first because of the interop
stuff. But it sounds like no. So as Sean says, I think you'll be fine
getting to 12.1 first and then whatever release you want after that.
From 12.1.2 release notes:
Starting in 12.1.1, if the PMP430 SM is configured with a Radio Scan
List containing frequencies which are invalid for the configured
Region Code, then loading the Configuration -> Radio page could cause
some of the valid frequency selections to be lost on the next radio
reboot. This has been fixed in 12.1.2 and it is recommended to
upgrade to 12.1.2 and to always click “Save Changes” when viewing the
Configuration -> Radio page on radios running 12.1.1.
I don't remember having "invalid for the configured region code"
frequencies. It just randomly lost frequencies. But whatever.
And I don't remember which release(s) it was that stored the bad
frequency offset in the 450 SMs. But it sucked.
On 6/20/2016 11:07 AM, Sean Heskett wrote:
You can just go to 12.1 and then 13.4.1
If the 450 is going to be on 14.1.x then use sm auto update to bring
the 430 sm up to 14.1.x (I'd recommend 14.1.2beta 17 rather than
14.1.1 even tho it's stil "beta" 14.1.2beta 17 is WAY more stable
than 14.1.1)
And then same thing if you are going to use 14.2 (which is still beta)
-Sean
On Monday, June 20, 2016, Ken Hohhof <[email protected]> wrote:
When Cambium says to first upgrade to 12.1, do they literally
mean 12.1, or 12.1.2?
