We gave noticed that SM update to 13.2 from various late beta builds without first updating the AP has resulted in SM radios reregistering at 2 minute intervals. Update of the AP to 13.2 seems to take care of it.
I have read the release notes, but there's no mention/documentation of a new option which appeared at the bottom of the Configuration -> Radio tab: "PMP 430 Interop Mode". For those of us operating with a mix of PMP430 and PMP450 SMs on certain APs, what are the benefits and drawbacks for each mode?
This is indeed a known issue and highlighted in the release notes. Most deployments will not see this, but we recommend upgrading the SMs before upgrading the AP.
We believe this happens because of the interaction between the 13.1.x MRC algoithm on the SM and the introduction of MIMO-A in 13.2. Since the MRC was enhanced in 13.2, you don;t see the issue when both AP and SM are on 13.2.
While upgrading your SMs to 13.2 first, there might be SM re-registrations. These will go away once all the other SMs are on 13.2 and then you upgrade you AP to 13.2.
There is an issue with the following SNMP OID to set the frequency list on an SM.
.1.3.6.1.4.1.161.19.3.2.1.1.0
For Example:
snmpset -v 2c -c "Canopy" 169.254.1.1 .1.3.6.1.4.1.161.19.3.2.1.1.0 s "548000"
If this OID is used to set aa frequency on an SM, it will cause the SM to crash. After the SM reboots, the list of frequencies listed the SNMP set will not be set on the SM.
We have carefully reviewed the code, and this is the only OID effected.
This issue is being tracked under Issue Number "CPY-10392" and is slated to 13.3 for repair.
We apologize for any inconvenience that this may have caused.
Both the SM and AP were using beta build 22 before the SM was upgraded to 13.2 final. The SM remained unregistered until I saw it the next morning. I upgraded the AP to 13.2 final and the SM registered as it should have and has remained that way with a -61 signal. That was the only customer on that sector. We then discovered the same thing had happened to many other subscribers on 3.65 and 5 GHz as well. Upgrade of the AP and the SM reconnects properly. Last time I will hit upgrade of the SM list in CNUT and go to sleep thinking it will all be OK.
Beta build 22 was quite old, but any beta build in general should be treated as if it is the previous released version when doing the upgrade. The release notes and forum recommended an SM first upgrade, and if SMs don't come back, they will once the AP is upgraded. Please see the release notes for more information.
If you pre-stage devices, we recommend setting these prior to upgrading the unit to 13.2 prior to deployment. if you need to configure them in the field, you will need to use the GUI interface.
We have a fix undergoing test now and will communicate more as it is availble.
Monir - We are working quite hard on getting R13.3 done before the end of the year... with it will come 7 MHz channels (in addition to 5, 10 and 20 MHz) for the 3 GHz PMP 450. Stay tuned to this forum for announcement of the open Beta release, which should be in a couple of weeks.
We upgraded our entire 450 deployment to 13.2 over the weekend. We had some high noisefloor sites where typcially a SM could not get a link cap test more than 20Mbps down. With this newest build we are seeing 60+Mbps on the link cap. Absolutely incredible.
Same holds true with low noisefloor areas... I would say at least a 40% inmprovement in capacity. Let it be known that we were operating with 12.x.x software before.
After a bit of a test I've rolled out 13.2 across the entire deployment too, ~160 SMs maybe a dozen APs. Two weeks on some gear, three on others, so far so good! The MIMO-A modes have made tremendous improvements in near-LOS situations, we don't see QPSK anymore! We were kinda hoping that 256QAM MIMO-A would be displayed as 7X but like I explained to the techs that display doesn't really matter anyway ;)
