20.2.1 throughput issue on 5GHz 450m

I’m wondering if you are seeing a similar issue as we are. We see it in v16.x + v20.x where our some of our SM’s suddenly have a bad uplink power level. Usually a sudden 20dB swing. Re-registering the SM to the AP fixes the condition temporarily. Or it sometimes corrects itself. We already have an open ticket but troubleshooting has hit a wall.

I can’t say for certain as we don’t graph AP receive dBm. But, we don’t notice it while t/s.

Any chance those low AP receive levels happen at a time of low throughput? Does a linktest straighten them out?

Any chance those low AP receive levels happen at a time of low throughput? Does a linktest straighten them out?

No, this happens at any random part of the day. A link test does not correct the problem. Only forcing a re-reg (rescan, reboot SM, reboot AP) will correct it every time. Until it randomly happens again. Usually to the same SM’s.
It seems to happen more to connections that are a distance >2-3 miles away or who have a narrow LOS or fresnel zone clearance issue. Multiple 450m AP’s @ multiple sites.

Cambium is testing a fix for this on one of our 450m.

How is that going for you?

Much improved but they’ve said not quite how they want it so still in progress.

Anybody in Cambium (@Charlie ?) can confirm this issue?
Should we wait to upgrade?

Yeah we are looking at issue on a 450m AP with @Craig_Wass where the rate adapt isn’t 100% stable and performing as well as We’ve found one fix that we will be getting into 20.3, but seems the rabbit hole goes deeper, so we are still investigating.

@Craig_Wass can maybe answer better as it caused him to roll back to, meanwhile there are thousands of radios running 20.2.1 or later. So I don’t have any critical concerns but there’s still issues we need to iron out with 20.X line.

1 Like

As we are discussing here, I’m wondering if your issues are coming from you still using BAM. We will discuss in the other thread, but you linked here so wanted to post in case others come here.

Hello @Charlie, we experienced similar issues and opened a case (269040) to the Support with logs and screenshots attached if you need more data to analize the problem.

What is the status on this. Should 450M AP’s be reverted back to for better rate adapt?

Have you tried Issues has been solved?

We have not. I’m under the impression this is addressed in 20.3. We’ll give that a try after a few days.

Any news about it?
Is this fixed in 20.3-B1? CPY-17365 maybe?

Thank you

4 posts were split to a new topic: MAC address change when moving from to 20.2.1

Sorry for the no response I was away taking some time off. There is one fix in 20.3-B1 and we have found another fix that will be included in 20.3-B2 coming up (hopefully) this week. More details when we post the updated beta load.

1 Like

Hello @Charlie ,

this is a great news.

Sincerely yours,

Niragira Olympe

DId 20.3-B2 get pushed back haven’t seen any news on it.

Nope, not yet. We are close but found an issue in internal testing that is delaying it. I’m not sure how long but once we have it fixed we’ll be posting the beta. vs 20.3

16 win, better throughput