Force 300-25L unable to connect

Quick question… is this only happing with the “L” type radios? All of our F300-25’s and 16’s are running 4.7.1… but we don’t have any “L” radios on our network.

We have observed this only on F300-13L SMs, don’t really ever use 300-25L’s. Guys reported that when they get into this issue, they reconnect to different AP or try another radio, mostly F300-13 or -16. And it works, also all N gear work from elevated to F130/F180/F200.

Hey, is it possible this happens when the signal from the AP is too hot? Pic above is -37 so has anyone noticed if it’s just close in clients with really hot signals? Or is it more ‘random’ than that?

Ours are -48 ~ -58, depending on distance and thin tree obstruction on some places. I can lower tx-power on AP a bit, but don’t think it’ll help. Distances are 0.75-1.6km. All AP RSSIs are very similar at SMs. I’d rule out interference (except possibly from ourselves), because this is quite isolated territory in the middle of forest, only interferers being 5GHz client Wi-Fi routers. Also there can’t be interference at every client across 70 degree AP coverage. As I told - there are successfuly working F300-13Ls on this AP… But we get this very frequently when replacing N to AC SMs.

Affected radios:

Force 300-13L
Force 300-25L

Same HW specs (Atheros 9563 CPU @720Mhz + Wifi Chipset QCA9886)

1 Like

I don’t know - you are probably correct. For me, I was just making a ‘bluesky’ kinda wild-guess type of suggestion - trying to figure out what might be wrong for those folks. I was just basing that on some people saying that connecting to a lower signal AP worked - and I also think the 25L SMs have a lower power (maybe lower quality or lower spec?) radio card in them, so it occurred to me that perhaps that was somehow overwhelmed by the too strong signal. But I dunno :man_shrugging:

That’s a good idea for a test, but probably not a practical work around for him long term, since that would limit distance and quality of connection on the longest distance clients. But a good idea for a test just to see from the same distance if that temporarily solves it.

1 Like

@Majk,

Can we arrange the remote session please so we can conduct the investigation?

Thank you.

Yes we see that SS9 on F300-13s too a lot. Previously F130/F180 or elevated units have seen no problem staying at MCS15 all the time, just “upgrade” to AC and 99% packets sent via SS modulation :slight_smile: I think even -13L’s work better. There are clear LoS to 70 meter high tower with a distance of 1+ km. Perfect conditions :man_shrugging: There were some BF issues on F300-13 chipset, but I think they were only applicable to downlink, not uplink… It’s crazy…

1 Like

what do we do? i purchase 30 and can no use them

1 Like

Hello!

Small question strictly about 13-L and 25-L. Do you see “INA retries exhausted” with E3K-L or with normal E3K too?

I read in this thread and heard from other engineers, that if there is another AP present with a lower signal 13-L and 25-L will connect to it after “INA retries exhausted” with higher signal AP.
I’ve tried it t in he lab multiple times but it does not happen.

Hello @Dryden_Net,

I suggest you to “Raise ticket” in the right top of this page. Our support engineer will help you with your issue.

This happens with both e3k and e3kL APs. But only with -13L SMs. All other ordinary F300s connect instantly and have no trouble at the very same spot, same time. Oddly enough, if you’ll leave it for say a day, it might successfully connect after million retries and operate until reboot. It’s a pesky problem at very least. Technicians climb on the roofs and never know if SM will work or not. We sometimes have additional 300-13 in the backpack just in case. It became somewhat anecdotical among our employees. Hopefully you can determine the issue and fix it.

We would really appreciate it if you can drop me Tech Support Files from the SM or SMs that are experiencing this issue. The remote session is highly appreciated too.

Thanks.

We’re already working it through support ticket #383413
Thanks

Perhaps there are more experiencing the same problem that would be willing to help pinpoint the problem.

1 Like

any forward move squirrely?

Hi @Dryden_Net,

we are working on it! Current status: we are preparing a debug build.
squirrely is the only one who has showed us a clear reproduce on request.
Before it was impossible to catch it in the field or in the lab.

transmit it to me as well

Hello, I put it on the bench and fixed the force 300 13, Below are images of the problem with the CI RF

marked in green has been repaired, marked in red shows poor performance.

2 Likes

How exactly did you “repair” it?

Hello, I bought the Chips from China and changed them.

2 Likes

Interesting. How did you discover that chip was the problem? How did you know that was broken?

Hello everybody,

we have a fix for “INA retries exhausted” issue! Here you can download a custom build with the fix based on 4.7.1.
It also will be merged in 4.8.0. Beta coming soon!
I’ve already 2 reports that it resolves this issue on Force300-13L and Force300-25L.
I will be glad to here your feedback!

5 Likes

Hello @Junior_almeida,

which exactly issue did you fix? This topic is about Force300-L version. But you mention normal F300.

Also we have found that F300-L issue is related to different antenna pattern compared to normal F300 and our Network Entry procedure.