I am adding the SMs directly in CNUT. From: George Skorup Sent: Tuesday, June 21, 2016 1:28 AM To: [email protected] Subject: Re: [AFMUG] 430 FW upgrade path (for 450 transition)
That's some of those quirks I mentioned about 11.2. The verification thing was screwed up with CNUT 4.8 too, IIRC. Possibly 4.7 as well, but it's been a while. I really don't think it's a CNUT thing, but I could be wrong. I have updated new (old stock), refurbished and recovered SMs (FSK and 430's) from 11.2 on the bench (directly with CNUT) and they all do that verification failed thing. I don't know what it is with that release, but it's... different. Are you using auto-update for all of the SMs? Have you tried discovering via scan or otherwise adding all SMs directly in CNUT? Is that any different? I guess with 11.2 on the AP and all SMs appearing to update fine... get it done and never look back? 13.4.1 has been stable for me. I really wish they would've built that for the 450 instead of having us wait on 14.x. But that's just my opinion, and I'm sure Cambium doesn't like it. On 6/21/2016 1:06 AM, Ken Hohhof wrote: Once an SM is in the screwed-up state, even taking the AP down to 11.2 didn’t seem to help. Only rebooting it, or getting lucky to have a few second window where you can log in remotely and reboot it. But based on a limited sample, here is what seems to be happening with an AP downgraded to 11.2. Every SM I upgrade to 12.1.2 gets a CNUT verification failure (package SW doesn’t match device SW), but a refresh in CNUT shows it good, and logging in via the web GUI doesn’t have a prompt to reboot. So far I haven’t had any fail to re-register or get stuck in a screwed-up state. So I’m thinking what has changed since I used to be able to upgrade 430 SMs? The APs used to be on 11.2. And I used to have CNUT 4.5 (if I remember correctly), now I’m using 4.9 because it’s required for 13.4 or 14.x, I forget which. My current guess is this is some kind of sequencing issue with CNUT 4.9 and SM firmware 12.x. And somehow the AP firmware enters into it also, so that the CNUT still has a verification error if the AP is on 11.2 but at least the SM doesn’t get screwed up. Next test would be to downgrade CNUT, but the oldest in the archive on the website is 4.8. I don’t know if I can go back to 4.5. From: Ken Hohhof Sent: Tuesday, June 21, 2016 12:20 AM To: [email protected] Subject: Re: [AFMUG] 430 FW upgrade path (for 450 transition) Dropping the AP to 12.1.2 didn’t help. I’m not sure it is possible to go back before 12.1 once you’ve upgraded, or I would try taking the AP back to 11.2. Maybe I should try 13.4.1 on the AP. From: Sean Heskett Sent: Monday, June 20, 2016 8:03 PM To: [email protected] Subject: Re: [AFMUG] 430 FW upgrade path (for 450 transition) Yeah 13.x on an AP with the SM at a lower version = no Bueno :-/ -Sean On Monday, June 20, 2016, Ken Hohhof <[email protected]> wrote: Interesting. I started doing the next sector, and discovered a couple SMs still on 10.5. So I decided to first take them to 11.2. Same problem! I’ve never had a problem going from 10.5 to 11.2 before. So it sounds like it’s actually a 13.x on the AP problem if SM is on <13.x, even 11.x? Actually though none of the SMs that were already on 11.2 had any problem with the AP on 13.2, the problem seems to be after an upgrade. And once the SM is rebooted, it is OK. From: George Skorup Sent: Monday, June 20, 2016 6:37 PM To: javascript:_e(%7B%7D,'cvml','[email protected]'); Subject: Re: [AFMUG] 430 FW upgrade path (for 450 transition) 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 Sent: Monday, June 20, 2016 6:02 PM To: javascript:_e(%7B%7D,'cvml','[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 Sent: Monday, June 20, 2016 11:54 AM To: javascript:_e(%7B%7D,'cvml','[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 <javascript:_e(%7B%7D,'cvml','[email protected]');> wrote: When Cambium says to first upgrade to 12.1, do they literally mean 12.1, or 12.1.2?
