EPMP 3000 all sta disassoc

[alfredobren]

Hello, we have a problem with epmp3000, we have all the clients and the sector in 4.5.4, every few days we realize that all the clients are disassociated, in the sector log we have this output
137 WMI Pending cmds reached.All STAs disassociated. IEEE80211_REASON_TDD_STOP (20)
We see that the gps is constantly losing and recovering it, we already have the maximum time selected so that the transmission does not cut off and the clients are disconnected.
We have already tried with frequency changes and different firmware versions and also to select internal sync but without result.
any ideas?
Thank you.

[Simon_King]

Welcome to the Cambium community. I’m sorry you’ve had a problem with your ePMP. Your GPS issues might be due to this:

3KL GPS issue on 4.5.4 official

Unfortunately, we have identified an issue in the 4.5.4 official release that has made GPS acquisition a bigger problem on the e3KL line. It seems to be happening more frequently. We apologize and are working on a hot fix that will result in 4.5.5 release shortly. As much beta and internal testing we have done, this was not reported during the phase and unfortunately made it into the official release. Thx Sakid

There is a beta version of the AP firmware linked further down which you might like to try:

3KL GPS issue on 4.5.4 official

Since many people asked for this release and I have provided via private message, I am curious to hear how the 4.5.5 release is working out. We are really looking for some feedback please. If you still would like the release here is the link below: https://drive.google.com/file/d/1iAXkJqsCiAe6WwjFocZsszYC2c9vYooX/view?usp=sharing

[ninedd]

@Simon_King

Welcome to the Cambium community. I’m sorry you’ve had a problem with your ePMP. Your GPS issues might be due to this:

Simon - he said that he had tried “internal sync” already - so that doesn’t sound to me like he’s reporting just a GPS issue.

@alfredobren

and also to select internal sync but without result.

It’s probably still a good idea for Alfredo to try the 4.5.5-RC beta (why not, try everything randomly with crossed fingers…) but since he’s tried turning the GPS off already, this is likely not a GPS only issue.

[gregn]

Upgraded from 4.5 to 4.5.5 today. ePMP3000L connected to 5 Force 180 SM’s
In a few hours all 5 SM’s lose connection to the AP 4 times. The AP is dropping all connections at the same time. Here is the log file:
Sep 17 09:02:45 MDNSwt01 kernel: [31690.698878] SM[58:c1:7a:46:f6:35] aid=5 associated with AP
Sep 17 09:02:37 MDNSwt01 kernel: [31682.936939] SM[58:c1:7a:49:5d:d7] aid=4 associated with AP
Sep 17 09:02:35 MDNSwt01 kernel: [31681.138606] SM[58:c1:7a:46:f6:35] aid=5 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 09:02:31 MDNSwt01 kernel: [31677.681793] SM[00:04:56:f6:4d:e1] aid=2 associated with AP
Sep 17 09:02:27 MDNSwt01 kernel: [31673.431790] SM[00:04:56:ed:eb:c3] aid=3 associated with AP
Sep 17 09:02:26 MDNSwt01 kernel: [31672.076698] SM[00:04:56:f2:55:57] aid=1 associated with AP
Sep 17 09:01:52 MDNSwt01 kernel: [31638.398906] SM[58:c1:7a:46:f6:35] aid=5 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 09:01:52 MDNSwt01 kernel: [31638.391330] SM[58:c1:7a:49:5d:d7] aid=4 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 09:01:52 MDNSwt01 kernel: [31638.366927] SM[00:04:56:f6:4d:e1] aid=2 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 09:01:52 MDNSwt01 kernel: [31638.350989] SM[00:04:56:f2:55:57] aid=1 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 09:01:52 MDNSwt01 kernel: [31638.343792] SM[00:04:56:ed:eb:c3] aid=3 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 04:39:45 MDNSwt01 kernel: [15911.601434] SM[00:04:56:f6:4d:e1] aid=2 associated with AP
Sep 17 04:39:44 MDNSwt01 kernel: [15910.351527] SM[58:c1:7a:46:f6:35] aid=5 associated with AP
Sep 17 04:39:44 MDNSwt01 kernel: [15909.855401] SM[00:04:56:f2:55:57] aid=1 associated with AP
Sep 17 04:39:42 MDNSwt01 kernel: [15908.351041] SM[58:c1:7a:49:5d:d7] aid=4 associated with AP
Sep 17 04:39:41 MDNSwt01 kernel: [15907.375534] SM[00:04:56:ed:eb:c3] aid=3 associated with AP
Sep 17 04:38:29 MDNSwt01 kernel: [15835.472672] SM[00:04:56:f2:55:57] aid=1 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 04:38:29 MDNSwt01 kernel: [15834.737370] SM[58:c1:7a:46:f6:35] aid=5 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 04:38:29 MDNSwt01 kernel: [15834.721172] SM[00:04:56:ed:eb:c3] aid=3 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 04:38:29 MDNSwt01 kernel: [15834.713026] SM[58:c1:7a:49:5d:d7] aid=4 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 04:38:29 MDNSwt01 kernel: [15834.697835] SM[00:04:56:f6:4d:e1] aid=2 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 02:42:54 MDNSwt01 kernel: [ 8900.042766] SM[58:c1:7a:46:f6:35] aid=5 associated with AP
Sep 17 02:42:49 MDNSwt01 kernel: [ 8895.038428] SM[00:04:56:ed:eb:c3] aid=3 associated with AP
Sep 17 02:42:48 MDNSwt01 kernel: [ 8894.538614] SM[00:04:56:f2:55:57] aid=1 associated with AP
Sep 17 02:42:46 MDNSwt01 kernel: [ 8891.958089] SM[58:c1:7a:49:5d:d7] aid=4 associated with AP
Sep 17 02:42:44 MDNSwt01 kernel: [ 8889.963463] SM[00:04:56:f6:4d:e1] aid=2 associated with AP
Sep 17 02:42:08 MDNSwt01 kernel: [ 8853.928545] SM[58:c1:7a:46:f6:35] aid=5 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 02:42:08 MDNSwt01 kernel: [ 8853.904033] SM[58:c1:7a:49:5d:d7] aid=4 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 02:42:08 MDNSwt01 kernel: [ 8853.888125] SM[00:04:56:ed:eb:c3] aid=3 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 02:42:08 MDNSwt01 kernel: [ 8853.872126] SM[00:04:56:f6:4d:e1] aid=2 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 02:42:08 MDNSwt01 kernel: [ 8853.864913] SM[00:04:56:f2:55:57] aid=1 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 00:18:46 MDNSwt01 kernel: [ 252.229111] SM[58:c1:7a:46:f6:35] aid=5 associated with AP
Sep 17 00:17:18 MDNSwt01 kernel: [ 164.231295] SM[58:c1:7a:46:f6:35] aid=5 disassociated. Reason: 48 (COMMUNICATION LOST)
Sep 17 00:16:42 MDNSwt01 kernel: [ 128.099507] SM[58:c1:7a:46:f6:35] aid=5 associated with AP
Sep 17 00:16:41 MDNSwt01 kernel: [ 127.529428] SM[58:c1:7a:49:5d:d7] aid=4 associated with AP
Sep 17 00:16:25 MDNSwt01 kernel: [ 110.894308] SM[00:04:56:ed:eb:c3] aid=3 associated with AP
Aug 28 17:02:07 MDNSwt01 DEVICE-AGENT[4828]: SessionID unavailable, regenerating
Aug 28 17:02:07 MDNSwt01 kernel: [ 95.924755] SM[00:04:56:f6:4d:e1] aid=2 associated with AP
Aug 28 17:02:02 MDNSwt01 kernel: [ 91.355749] SM[00:04:56:f2:55:57] aid=1 associated with AP
Aug 28 17:01:47 MDNSwt01 snmpd[4153]: DFS status: N/A
Syslog File
Not Happy

[Simon_King]

I’m sorry to hear that. Maybe it’s the same problem as this?

All SMs disconnecting from ePMP3000 on 4.5.4

Chad, More than likely you are witnessing a phy reset which is a work around we put in instead of a full AP reboot. This has been an intermittent problem plaguing some customers for a while. It has been a tough problem to address but finally we have some light at the end of the tunnel. The team is going to work with some customers to validate the solution and we will then push out to additional customers. Could you elaborate how often you see this? Thx Sakid