What you saw is an engineering debug tool.
I would like to emphasize one more time you can’t use it to access ePMP via SSH/Web without knowing admin password. It is not a remote accessible backdoor as you are trying to call it.
Dmitry
2 Likes
Dimitry,can You tell it˙s safe to upgrade 4.4.1 from 4.1.4,I see the 4.4.1 is image file and old 4.1.4 was tar file.
Thanks in advance
On EPMP3000 in the user guide for 4.3.2 there is a MU-MIMO configuration section inside Configuration -> Radio. On my AP running 4.4.1 this option is not present. Has this option been removed? Unfortunately I can't verify this myself by downgrading the AP.
Thanks.
Earlier 4.x firmware had some options for different MU-MIMO configurations, but as more testing was done with various 3rd party antenna configurations and firmware matured, these options were removed as there was no benefit. The upcoming 4.5 release will support various antenna configurations and will add omni support.
2 Likes
Hi,
This option was removed in 4.4 and now it is done automatically.
As Eric noted we will have support for Omnidirectional antenna option from KP Performance in 4.5 release. This is the only supported antenna so far.
Thanks,
Dmitry
So far, other than a couple of backhauls, all our stuff is ePMP 1000/2000. I have one Micropop where I upgraded the AP and the customer radios to 4.4.1 (it is 5ghz ePMP 1000 connectorized AP all 12 subscribers are within 500ft , all are F180 except for 1 F200). Both banks on the AP upgraded to 4.4.1.
The old problem were the AP randomly starts hanging / timing out on HTTP, SNMP and SSH (still responds to pings) is back with a vengence. It will still pass traffic and works as far as the customers are not complaining. However when we seen this with some of the previous versions of software it would require a reboot and then the problem would go away for hours/days/weeks. On 4.4.1 however the services are just really flaky. It may not work for days and then start working on its own even though there as no reboot. The services top and start working randomly with "not working" being the default state.
Even when you can log into the radio's GUI it will randomly "Connection temporarily lost" every few minutes and it may start working again in a few minutes or it may be down for hours/days.
Also appears you can't make changes / reboot (also a bug back from the past). It acts like the change you made is being applied but it never actually happens. Same with rebooting via the GUI, acts like it reboots but it doesn't. Haven't been able to access it via SSH since the upgrade to 4.4.1 a week ago and SSH has only responded for a few minutes a few times each day (even after physically power cycling it).
Just FYI.
Hi,
That is very weird and I beleive we have no reports of anything like that in our support system.
If you are willing to debug it please shoot me an e-mail at dmitry.moiseev@cambiumnetworks.com
Thanks,
Dmitry
I meant that SNPM only responds for a few minutes a few times a day not SSH.
Anyway, doesn't matter the only reason this AP was upgraded to v4 was so we could upgrade the CPE's to v4 in preperation for replacing this AP with with a 3000 AP and Mimosa Omni for testing.
I decided to try 4.4.1 on one of our 2.4 epmp 1000, all SM's are F200's one of them keeps rebooting I have tried to reflash/reboot it has
aid=3 disassociated. Reason: INVALID SECURITY KEY
aid=3 disassociated. Reason: COMMUNICATION LOST
in the logs of the AP, SM was fine before upgrade. Any ideas? Should I just downgrade?
Can you try to reboot SMs? It should help
Thanks,
Dmitry
I rebooted all SM's then the AP, SM still crashing and AP giving in logs:
aid=6 disassociated. Reason: COMMUNICATION LOST
aid=1 disassociated. Reason: INVALID SECURITY
has the MAC of the crashing SM
What we can do is to give you the 4.4.2-RC that should fix the issue or you can safely downgrade.
If you want the RC please shoot me an email at dmitry.moiseev@cambiumnetworks.com
Thanks,
Dmitry
1 Like
@Dmitry Moiseev wrote:What we can do is to give you the 4.4.2-RC that should fix the issue or you can safely downgrade.
If you want the RC please shoot me an email at dmitry.moiseev@cambiumnetworks.com
Thanks,
Dmitry
I am having a similar issue with 2.4Ghz SM's on one AP and thought it was severe interference. Tower has been up for 2 years and no such issues to this extent until this week. All SM's are getting booted off in the last few days. Even SM's in the 50's. Upgraded 2.4Ghz equipment (AP's and SM's) on this tower to 4.4.1 from 3.5.6 maybe 2 weeks ago.
Does this look like a candidate for either downgrading back to 3.5.6 -or- 4.4.2-RC2 as well?
Hi,
Please send me an email. I would say that I need tech support dump from both AP and one of the disconnecting SMs to say for sure.
In any case I will share the 4.4.2-RC with you.
Thanks,
Dmitry
1 Like
@Dmitry Moiseev wrote:
Hi,
Please send me an email. I would say that I need tech support dump from both AP and one of the disconnecting SMs to say for sure.
In any case I will share the 4.4.2-RC with you.
Thanks,
Dmitry
Just emailed you tech support files for the AP and 2 SM's with RSSI's in the 50's that never got booted until recently. Thanks.
Having the same issue on 2.4. From the forums looks like 4.4.2 has even more issues so will probably down grade. Here are the logs incase it helps figure out the issue.
AP
Nov 10 22:52:51 School-N kernel: [200764.960000] SM[00:04:56:] aid=2 disassociated. Reason: COMMUNICATION LOST Nov 11 13:46:35 School-N kernel: [254389.230000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 11 13:47:40 School-N kernel: [254453.670000] SM[00:04:56:] aid=1 disassociated. Reason: INVALID SECURITY KEY Nov 11 15:57:11 School-N kernel: [262224.910000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 11 15:57:32 School-N kernel: [262246.250000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 11 17:26:22 School-N kernel: [267576.470000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 11 17:27:02 School-N kernel: [267615.740000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 11 17:27:23 School-N kernel: [267637.140000] SM[00:04:56:] aid=1 disassociated. Reason: INAC MISS TIMEOUT Nov 11 20:26:23 School-N kernel: [278376.530000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 11 21:32:57 School-N kernel: [282371.410000] SM[00:04:56:] aid=6 disassociated. Reason: COMMUNICATION LOST Nov 12 05:24:09 School-N kernel: [310642.620000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 12 05:25:06 School-N kernel: [310700.260000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 12 13:15:29 School-N kernel: [338923.480000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 12 13:16:22 School-N kernel: [338975.720000] SM[00:04:56: aid=1 disassociated. Reason: COMMUNICATION LOST Nov 12 23:36:33 School-N kernel: [376187.420000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 13 07:02:55 School-N kernel: [402969.370000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST Nov 13 09:57:04 School-N kernel: [413417.680000] SM[00:04:56:] aid=7 disassociated. Reason: COMMUNICATION LOST Nov 13 09:57:43 School-N kernel: [413457.230000] SM[00:04:56:] aid=7 disassociated. Reason: INVALID SECURITY KEY Nov 13 09:57:51 School-N kernel: [413465.290000] SM[00:04:56:] aid=7 disassociated. Reason: COMMUNICATION LOST Nov 13 13:08:34 School-N kernel: [424908.310000] SM[00:04:56:] aid=1 disassociated. Reason: COMMUNICATION LOST
sm 1
Nov 10 17:20:36 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 10 17:20:36 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 10 17:43:11 Bubby- kernel: [164877.630000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 33 (GPFs MISS) Nov 10 17:43:23 Bubby- kernel: [164889.470000] SM associated with AP[00:04:56:] Nov 10 17:43:27 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 10 17:43:27 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 10 22:59:43 Bubby- kernel: [183868.610000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 33 (GPFs MISS) Nov 10 22:59:52 Bubby- kernel: [183877.900000] SM associated with AP[00:04:56:] Nov 11 01:57:08 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 11 01:57:08 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 11 04:56:24 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 11 04:56:24 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 14:57:04 Bubby- kernel: [414109.580000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 33 (GPFs MISS) Nov 13 14:57:35 Bubby- kernel: [414141.000000] SM associated with AP[00:04:56:] Nov 13 14:57:44 Bubby- kernel: [414149.440000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 49 (INVALID SECURITY KEY) Nov 13 14:57:57 Bubby- kernel: [414162.890000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 32 (NO ALLOCATION ON AP) Nov 13 14:58:18 Bubby- kernel: [414183.960000] SM associated with AP[00:04:56:] Nov 13 14:58:24 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 14:58:24 Bubby- DEVICE-AGENT[6276]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found)
sm 2
Nov 13 08:02:54 Tom- kernel: [26763.880000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 33 (GPFs MISS) Nov 13 08:03:24 Tom- kernel: [26793.840000] SM associated with AP[00:04:56:] Nov 13 09:17:30 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 09:17:30 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 11:56:37 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 11:56:37 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 12:09:46 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 12:09:46 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 14:08:34 Tom- kernel: [48703.370000] SM disassociated from AP[00:04:56:] F=2467 11nght10. Reason: 48 (COMMUNICATION LOST) Nov 13 14:08:57 Tom- kernel: [48726.330000] SM associated with AP[00:04:56:] Nov 13 14:09:14 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 13 14:09:14 Tom- DEVICE-AGENT[4823]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found)
Nov 14 11:31:08 CS24_AP kernel: [136884.960000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: INAC MISS TIMEOUT Nov 14 11:31:18 CS24_AP kernel: [136894.440000] SM[68:72:51:00:54:8e] aid=3 disassociated. Reason: COMMUNICATION LOST Nov 14 11:31:30 CS24_AP kernel: [136906.370000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:31:38 CS24_AP kernel: [136914.870000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:31:56 CS24_AP kernel: [136932.120000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:08 CS24_AP kernel: [136944.840000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:29 CS24_AP kernel: [136965.320000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:44 CS24_AP kernel: [136980.270000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:53 CS24_AP kernel: [136989.260000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:33:05 CS24_AP kernel: [137001.290000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:33:53 CS24_AP DEVICE-AGENT[2986]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 14 11:35:08 CS24_AP kernel: [137124.290000] SM[00:27:22:20:1e:9b] aid=8 disassociated. Reason: COMMUNICATION LOST Nov 14 11:35:43 CS24_AP kernel: [137160.020000] SM[00:27:22:20:1e:9b] aid=8 disassociated. Reason: COMMUNICATION LOST Nov 14 11:36:38 CS24_AP kernel: [137214.320000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:37:09 CS24_AP kernel: [137245.300000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:37:41 CS24_AP kernel: [137277.840000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:38:04 CS24_AP kernel: [137300.580000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:38:38 CS24_AP kernel: [137334.870000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST
also having troubles with disconnecting SM on 2.4 Ghz epmp1000 with elevated ubnt (4.4.2)
@haver wrote:
Nov 14 11:31:08 CS24_AP kernel: [136884.960000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: INAC MISS TIMEOUT Nov 14 11:31:18 CS24_AP kernel: [136894.440000] SM[68:72:51:00:54:8e] aid=3 disassociated. Reason: COMMUNICATION LOST Nov 14 11:31:30 CS24_AP kernel: [136906.370000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:31:38 CS24_AP kernel: [136914.870000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:31:56 CS24_AP kernel: [136932.120000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:08 CS24_AP kernel: [136944.840000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:29 CS24_AP kernel: [136965.320000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:44 CS24_AP kernel: [136980.270000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:32:53 CS24_AP kernel: [136989.260000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:33:05 CS24_AP kernel: [137001.290000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:33:53 CS24_AP DEVICE-AGENT[2986]: [src/epmp.c:182 json_config_show] request failed, ret = 2 (Param not found) Nov 14 11:35:08 CS24_AP kernel: [137124.290000] SM[00:27:22:20:1e:9b] aid=8 disassociated. Reason: COMMUNICATION LOST Nov 14 11:35:43 CS24_AP kernel: [137160.020000] SM[00:27:22:20:1e:9b] aid=8 disassociated. Reason: COMMUNICATION LOST Nov 14 11:36:38 CS24_AP kernel: [137214.320000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:37:09 CS24_AP kernel: [137245.300000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:37:41 CS24_AP kernel: [137277.840000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:38:04 CS24_AP kernel: [137300.580000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOST Nov 14 11:38:38 CS24_AP kernel: [137334.870000] SM[00:27:22:00:66:12] aid=38 disassociated. Reason: COMMUNICATION LOSTalso having troubles with disconnecting SM on 2.4 Ghz epmp1000 with elevated ubnt (4.4.2)
Hi Alexander,
We are looking into the issue.
Thank you for provided Tech Support Files.
We will keep you updated.
Thank you.