George,
We ran the beta through most of it's revisions. I believe it was always
safe to have a 13.2 beta CPE registering to the AP.
There were several times we pulled all the CPE back to the shop to get
them on current software. Our process is supposed to insure any SM's
in the trucks are logged back in at night and flagged if they need
defaulted, updated, etc.
We found one guy hording about 30 SM's scattered around the truck, many
of them with antique software. Arg.
Mark
On 11/13/14, 2:15 PM, George Skorup (Cyber Broadcasting) via Af wrote:
I had a tech trying to install an SM that was old stock in the truck
with 12.2.2. He was trying to register and align with an AP running
build 35. I'd try to proxy into it to set the color code (from ICC)
and it would go idle. Power level was OK, about -72. Then about two
minutes later a couple other SMs would go idle. Tried again and again,
more SMs would go idle. Couldn't even get it to auto-update. Luckily
it was his house, so I had him bring the SM back, upgraded it to build
35, he re-installed, worked fine.
So now I gotta update the whole 450 network. Then gather all of the
radios from the trucks and all SMs in stock and update them. It sucks,
but I don't care because 13.2 is freakin awesome.
On 11/13/2014 12:46 PM, Aaron Schneider via Af wrote:
Thank you very much for all of you that helped with Open Beta. It was
a very long release, but there were lots of things found and fixed as
a result of having you helping us with access to your systems.
I’d like to highlight here, for those of you that don’t read the
release notes, due to the MIMO-A changes and isolated issues seen
during the upgrade procedure at some customers sites, we are
recommending an SM-first upgrade when going to 13.2. Most customers
were able to do the normal AP-first upgrade without issues. But
there were some changes in the Air Interface PHY that could
potentially cause SMs to have a hard time registering when you have
mixed versions between 13.2 and earlier (13.1.3). Even doing an
SM-first (reverse) upgrade, most, if not all, of the SMs should come
back in session, so it isn’t a downtime upgrade (where the SMs don’t
register until the AP is upgraded).
There is more information in the release notes as well as
instructions on how to do this type of upgrade as well as help to
switch procedures if you have already started a normal upgrade and
have SMs having trouble registering.
We saw no issues with registration (we actually saw improvements due
to MIMO-A control messages) in SM registration once the sector was
fully on 13.2. This last problem is a big part of the final 2-3 week
delay. Also we were able to fully fix the 13.2 Open Beta nagging
Ethernet lockup detection problem.
Please enjoy 13.2, it has been a long time in the making!
For the questions about 13.2 being for PMP100, the answer is no. And
I can’t comment quite yet on any possible upcoming releases for the
PMP100.
Regards,
-Aaron
*From:*Af [mailto:[email protected]] *On Behalf Of *Matt
Mangriotis via Af
*Sent:* Thursday, November 13, 2014 7:13 AM
*To:* [email protected]
*Subject:* [AFMUG] System Release 13.2 is Official
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
--
Mark Radabaugh
Amplex
[email protected] 419.837.5015 x 1021
