The reason may be that the 300-25L has a bit less power and the message indicates that this power is missing, Log show that the signal is weak to establish the connection.
How far is this link?
Maybe there is a frequency interference between AP1 and the Force300-25L that will not connect? You state the same configuration, but are both APs set to the same frequency?
Hi @Majk,
it there was such a bug we could notice it before. To figure out what is going on in your setup we need techsupport files form all equipment in question and right after it could not connect.
I suggest collect it and raise a support ticket. Then our engineer will be able to isolate the issue. https://support.cambiumnetworks.com/
Hi Andrii, we are opened support ticket #313930 one month before and we are described same situation in different location (tech. support files was attached). This ticket was marked as solved, but its not solved!. For now ticket #320154 was opened (with screenshots and support files)
We get this time to time with F300-13L. Usually the solution is to replace to F300-13 or to connect to AP with lower RSSI. This happens with ePMP3000.
Another problem with ePMP3000 is where F300 units are stuck at SS modulation and never goes up. Even when conditions seam ideal. We then replace to L or sometimes even to elevated N gear to fix things, when BF-off doesn’t help for F300 non L SMs. It’s just how it is Don’t expect everything to work just out of the box without a hassle. Cambium gear are probably not expensive enough to give such trouble-free experience
Sorry, but this bug was reported one year ago with logs and complete field testing (Force 300-25, Force 300-19, Force 300-16, Force 200, Force 190 etc) All of this radios works flawlesly with outstanding throughput with the exception of force 300-25L (problem with connection with AP described above)
Cambium does not solve this problem and it is a shame.
I know 2-3 solved engineering tickets that could be relevant to such issues since 4.7.0.
In stable 4.7.0-RC17 was the fix, exactly for F325L that was dropping into connect/disconnect cycle on random occasion. Reason was something about INAR, Allocation, GPF etc
I checked 320154 ticket. There was no response for requested remote session.
If you are still observing this issue and ready to help us to fix it. I will be very grateful for the remote access to the setup on 4.7.1-RC18.
Thank you!
for the provided ticket RMA was approved as for faulty unit. RMA process stalled because purchase invoice was not provided.
If you you believe both AP and SM are ok, PM me techsupport files from AP and SM when the issue is in progress. I will take a look!
Thank you!
in your mentioned case I see a faulty unit without warranty. It is not a software issue and can not be fixed.
As any other gear our radio can fail due to natural reasons. Like fatigue, harsh environment, inaccurate usage etc. When it happens under warranty we RMA it asap without pain.
I’m sorry! But I can not help in your case.
Just to let you know. Force 300-13 its doing the same thing i had like 30 CPE going to RMA. And now i have some 300-L doing the same thing. This really is a pain and no fix yet.