ePMP trouble. AP remove all clients.

afetisov · October 18, 2019, 8:52am

Good afternoon.
Sometimes Epmp 1000 2.4 / 5 GHz removes all clients. Remains 1 regular and 1 elevate. Rebooting the device solves the problem for a while.

-------------------------------------------

Добрый день.
Иногда Epmp 1000 2.4 / 5 GHz удаляет всех клиентов. Остается 1 обычный и 1 элевате. Перезагрузка устрайства решает проблему на некоторое время.

UPD. Version: 2.4 - 3.5.5, 5 - 3.5.6

Fedor · October 18, 2019, 10:08am

Hi,

Could you please provide System Log from AP and one of disconnected SMs when the issues happens?

Thank you.

Dmitry_Moiseev · October 18, 2019, 10:04pm

I also guess it might have been solved in 4.4.1 release so give it a try.

Thanks,

Dmitry

afetisov · October 21, 2019, 4:55am

AP - log

Oct 21 10:50:15 AP-Koskol kernel: [ 7177.530000] SM[00:04:56:##:##:##] aid=19 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:15 AP-Koskol kernel: [ 7177.530000] SM[24:a4:3c:##:##:##] aid=12 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:20 AP-Koskol kernel: [ 7182.660000] SM[00:27:22:##:##:##] aid=17 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:20 AP-Koskol kernel: [ 7182.670000] SM[00:27:22:##:##:##] aid=14 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:20 AP-Koskol kernel: [ 7182.680000] SM[00:27:22:##:##:##] aid=4 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:20 AP-Koskol kernel: [ 7182.690000] SM[68:72:51:##:##:##] aid=1 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:34 AP-Koskol kernel: [ 7196.860000] SM[68:72:51:##:##:##] aid=5 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:40 AP-Koskol kernel: [ 7202.360000] SM[00:27:22:##:##:##] aid=4 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:43 AP-Koskol kernel: [ 7205.350000] SM[68:72:51:##:##:##] aid=7 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:43 AP-Koskol kernel: [ 7205.860000] SM[00:04:56:##:##:##] aid=10 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:44 AP-Koskol kernel: [ 7206.860000] SM[00:27:22:##:##:##] aid=4 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:49 AP-Koskol kernel: [ 7211.860000] SM[24:a4:3c:##:##:##] aid=8 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:50:55 AP-Koskol kernel: [ 7217.830000] SM[68:72:51:##:##:##] aid=9 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:11 AP-Koskol kernel: [ 7233.150000] SM[68:72:51:##:##:##] aid=15 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:14 AP-Koskol kernel: [ 7236.360000] SM[00:27:22:##:##:##] aid=14 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:20 AP-Koskol kernel: [ 7242.100000] SM[24:a4:3c:##:##:##] aid=18 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:24 AP-Koskol kernel: [ 7246.360000] SM[24:a4:3c:##:##:##] aid=2 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:39 AP-Koskol kernel: [ 7261.860000] SM[24:a4:3c:##:##:##] aid=12 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:40 AP-Koskol kernel: [ 7262.860000] SM[68:72:51:##:##:##] aid=11 disassociated. Reason: COMMUNICATION LOST
Oct 21 10:51:43 AP-Koskol kernel: [ 7265.880000] SM[24:a4:3c:##:##:##] aid=8 disassociated. Reason: COMMUNICATION LOST

Client log

Sep  3 14:51:39 Tarasov A kernel: [226304.250000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 48 (COMMUNICATION LOST)
Sep  3 14:52:35 Tarasov A kernel: [226360.620000] SM associated with AP[00:04:56:##:##:##]
Sep  3 15:17:04 Tarasov A kernel: [227829.710000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 15:18:15 Tarasov A kernel: [227900.890000] SM associated with AP[00:04:56:##:##:##]
Sep  3 15:20:03 Tarasov A kernel: [228008.800000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 15:20:48 Tarasov A kernel: [228053.910000] SM associated with AP[00:04:56:##:##:##]
Sep  3 15:20:55 Tarasov A kernel: [228060.390000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 15:22:26 Tarasov A kernel: [228151.920000] SM associated with AP[00:04:56:##:##:##]
Sep  3 15:22:29 Tarasov A kernel: [228154.810000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 15:22:43 Tarasov A kernel: [228168.920000] SM associated with AP[00:04:56:##:##:##]
Sep  3 15:34:44 Tarasov A kernel: [228889.400000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 15:35:13 Tarasov A kernel: [228918.530000] SM associated with AP[00:04:56:##:##:##]
Sep  3 15:36:54 Tarasov A kernel: [229019.750000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 15:38:25 Tarasov A kernel: [229110.550000] SM associated with AP[00:04:56:##:##:##]
Sep  3 16:13:50 Tarasov A kernel: [231235.410000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 16:14:00 Tarasov A kernel: [231245.410000] SM associated with AP[00:04:56:##:##:##]
Sep  3 16:33:44 Tarasov A kernel: [232429.450000] SM disassociated from AP[00:04:56:##:##:##] F=2422 11nght40plus. Reason: 32 (NO ALLOCATION ON AP)
Sep  3 16:34:44 Tarasov A kernel: [232489.090000] SM associated with AP[00:04:56:##:##:##]
Sep  3 16:36:02 Tarasov A kernel: [232567.760000] SM disassociated from AP[00:04:56:##:##:##

Version update to 4.4.1

GINEBRA254 · October 23, 2019, 11:38am

my problem is similar.....

beeonline · October 24, 2019, 8:34am

And i have it almost every 2 days. Thought of high interference, but this interference is permanent in my area and UBNT keeps all the clients even with low TXQ/RXQ.

With same log.

I have also tried to set sync source to internal, thinking that somebody might jam the GPS freq, but it happened again.

I will try new FW and we'll see.

Dmitry_Moiseev · October 24, 2019, 8:30pm

Can you please reach ot to me at dmitry.moiseev@cambiumnetworks.com in case 4.4.1 doesn't help?

Dmitry

Chris_2 · October 25, 2019, 3:33am

I have the same issue. Didn't start happening until I upgraded from 3.x firmwares to 4.4.1.

Dmitry_Moiseev · October 28, 2019, 10:38pm

Well, I would recommend everyone having this issue to drop me an email at dmitry.moiseev@cambiumnetworks.com

Dmitry

Chris_2 · November 1, 2019, 2:28pm

Any update on this issue. Any fixes in 4.4.2.

Chris_2 · November 5, 2019, 1:10am

Please respond, this is creating a fair amount of issues with our customers. Threats to cancel service, etc.

Eric_Ozrelic · November 5, 2019, 3:13am

@Chris_2 wrote:
Please respond, this is creating a fair amount of issues with our customers. Threats to cancel service, etc.

Have you tried 4.4.2? This error is typically due to interference. Have you confirmed that the client isn't operating a home router on or near the ePMP's channel? Have you tried changing your channel and/or channel width? You could also try long GI as well. If all of that fails, please email Dmitry with an AP and client support dump so he can look into it.

ninedd · November 5, 2019, 6:48am

@Chris_2 wrote:
Please respond, this is creating a fair amount of issues with our customers.

Hi Chris. Have you tried emailing Dmitry? He previously said the following:

Can you please reach ot to me at dmitry.moiseev@cambiumnetworks.com
in case 4.4.1 doesn't help?
I would recommend everyone having this issue to drop me an email
at dmitry.moiseev@cambiumnetworks.com

Now 4.4.2 is out since he said the above, so as Eric suggests, 4.4.2 should be tried to see if it has any fixes or tweaks which help. BUT, as Dmitry says, if you are having this issue, drop him an email. :)