Interesting, we’ve seen this issue sporadically over the last year or two and every time we come across it we swap the 300-25L to a 300-25. It’s hard to leave it faulty for troubleshooting as that could cost us a customer.
We’ve seen this issue across our network with Force 300-25L. No fix in latest Beta21 FW
Abbiamo diverse antenne con questo problema, la soluzione e metterne una nuova e tutto funziona, quindi solita posizione e solito AP, esclusi problemi di interferenze, anche su banco la cpe non si connette si vedono in monitor gli AP e non si collegano errore Rejected - INA response not received
Nel Log
Mar 28 16:42:52 heumann kernel: [ 4099.108452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:42:36 heumann kernel: [ 4083.608451] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:42:28 heumann kernel: [ 4075.608452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:42:23 heumann kernel: [ 4070.608452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:42:06 heumann kernel: [ 4053.608452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:42:04 heumann kernel: [ 4051.608453] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:41:54 heumann kernel: [ 4041.108453] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:41:29 heumann kernel: [ 4016.108452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:40:54 heumann kernel: [ 3981.118473] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 16 (INA RETRIES EXHAUSTED)
Mar 28 16:40:54 heumann kernel: [ 3981.108451] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:40:35 heumann kernel: [ 3962.608451] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:40:30 heumann kernel: [ 3957.108451] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:40:11 heumann kernel: [ 3938.608452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:40:06 heumann kernel: [ 3933.108451] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:39:46 heumann kernel: [ 3913.608453] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:39:35 heumann kernel: [ 3902.108452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:39:33 heumann kernel: [ 3900.108452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:39:32 heumann DEVICE-AGENT[5922]: Unable to discover cnMaestro URL (re-discover in 347 seconds)
Mar 28 16:39:11 heumann kernel: [ 3878.618448] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:38:49 heumann kernel: [ 3856.118464] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:38:36 heumann kernel: [ 3843.618448] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:38:12 heumann kernel: [ 3819.618444] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:37:57 heumann kernel: [ 3804.618447] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:37:35 heumann kernel: [ 3782.618450] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:37:19 heumann kernel: [ 3766.118452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:36:40 heumann kernel: [ 3727.628462] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 16 (INA RETRIES EXHAUSTED)
Mar 28 16:36:40 heumann kernel: [ 3727.618449] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:36:34 heumann kernel: [ 3721.618452] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:36:32 heumann kernel: [ 3719.118458] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Mar 28 16:36:18 heumann kernel: [ 3705.118453] SM cannot be associated on AP[00:04:56:d8:84:50] F=5525 11acvht40plus. Reason: 24 (LOST INAR)
Siamo un WISP e abbiamo diverse situazioni, le antenne che non si collegano a nessun AP, abbiamo resettato di default, abbiamo aggiornato, abbiamo fatto downgrade
Unfortunately this force series epmp 300-13, 300-16, 300-25l is giving me a headache.
This leaves us a little discouraged. I used ubiquiti and had no problems with the ac radios. I’m already abandoning the Cambium network, to see the LTU of ubiquiti or radwin.
Hi Junior,
I appreciate that you are discouraged - especially by what must have felt like harsh and dismissive comments from Cambium. That certainly sounded discouraging for me to read also. 
YET… I encourage you to keep with Cambium… in our experience, sometimes there is a wall getting them to understand, BUT once they understand that this is a problem affecting a number of clients and a number of radios (and not just a single out-of-warranty radio) then in my experience, I’m confident that Cambium will get to the bottom of it for you and for everybody else. 
@Andri - I’d encourage you to re-examine things and to look more deeply. I may be incorrect, but there seems to be a number of reports and it doesn’t seem to be the case of a single customer, with a single out-of-warranty radio that can be dismissed. To me, this appears to be a number of people, having the issue with a large number of radios. 
3 Likes
Hello, other Force 300 13 units seem to have upload issues. less than 4 months of use. I’m replacing it with force 180
1 Like
For what it’s worth, we found the same thing with 300-13 and we don’t use 300-13 anymore - we only use 300-25 and 300-16 now. For the few $ difference between -13 and -16 it wasn’t worth it to save the few $$. As well, the radios in 300-13 are also lower power output, so not only are the antennas lower gain and a much wider & worse pattern, the radio chipsets themselves are different and lower power as well.
1 Like
We just put a brand new force 30025L and have that INA response, issue, put another force30025L and it works. we are using 4.71 RC24, is cambium really trying to fix this issue? how can I get an RMA for the unit showing this message?
any soluton with 30025L and INA error?
No …Cambium still ignore this bug.
2 Likes
I can confirm this happens on 300-13L’s with 4.7.1-RC24 and final 4.7.1 (which is the same RC24 as we’ve been told in other thread). We have a site where 3 ePMP3000 4x4 sectors cover ~120deg with sector overlap, APs are properly freq-spaced, 75/25 GPS synced. When we go to replace N SMs to AC for our clients, previously perfectly worked SM on that sector cannot connect due to this INA response error. Our guys always connect these SMs to adjecent AP with lower signal in such case. Last week they said there were more than 5 such occasions.
1 Like
Yes I can confirm we have a similar situation. These radios with INA response do not Connect in any scenario we have tried. They are brand New. Maybe is a hardware issue as we put other forcé 30025L and it works.
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?
Generally speaking, if the RSSI is greater than -40 dBm, the receiver is contributing to the error rate. OFDM based radios like the signal to be between -40 dBm and -60 dBm on 20/40 MHz channel sizes, meaning the SNR should be less than 50 dB for best operation. 64QAM needs 23 dB SNR, 256 QAM needs ~28 to 30 dB SNR (these values can vary between different systems). For any problem that appears on a link with SNR higher than -40 dBm, try reducing the AP’s tranmit power by 3 or 6 dB, and see if the issues change or abate.
That is not the issue. How can you explain just repalcing the same radio f30025L by another force30025L radio dont get the INA error?
1 Like
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.
for me it has happened with 6 radios all of them F30025L. Last year 2 of them were replaced by warranty from my distributor, the other 4 got this error this month and I have not sent to warranty yet as I was expecting there could be a potential software solution but it may be a hardware issue. Just to clarify again these are brand new F30025L, we put them and get that INA error, then put another F30025L radio and it works.
1 Like
IIRC, the “L” series is just for ROW use and not for sale or certified for use in the FCC/IC regions.
I’m wondering if there’s something else different with those radios… a physical difference or manufacturing difference between the “L” series and the FCC/IC radios?
The L means light version. here you can see some comparison
https://community.cambiumnetworks.com/t/force-300-25-vs-300-25l