Would someone who works at Cambium please explain to us peons the process of an ePMP-2000 SM when it is scanning and trying to lock onto its associated ePMP2000 AP, both at initial power up and after a loss of RF connectivity between the SM and the AP?
We have SM's that refuse to connect back up to an AP until you reboot the power at the SM.
What firmware version are you running on the AP and SM's?
Hi Danny. This probably isn't helpful, but we have many ePMP AP's and SM's - both in PTMP and in PTP configuration, and we have zero problems with them linking, or relinking after a power outage or any other loss of link reason.
In your situation - this isn't a DFS holdoff happening, right? How about loss of GSP sync? Those are the only things that come to mind where the systems can (on purpose) stop talking for a time-out or hold-off period.
Current firmware - 4.3.2.1, as I recall without going to look it up.
Not a DFS problem - operating on non-DFW channels.
AP GPS not a problem either. Have multiple AP's at various locations - all have long term UPS and generators.
Had to travel to another SM this morning and power cycle to get it to lock onto an AP.
Got into it first before power cycle and the radio had seen multiple AP's to lock onto. After power cycle, the SM could see the same AP's. All 20 Mhz and 40 Mhz channels selected in frequency list.
We are looking for a detailed explanation from someone at the factory as to what the SM's do as far as trying to lock onto an AP after initial bootup and after is looses lock on the first AP.
Please roll back to 3.5.6 on everything, this is 100% known good working firmware for e1k/e2k deployments. 4.3.2.1 should only be used for mixed mode or AC only deployments. Alternatively u could try the new 4.4 beta… but your best bet is 3.5.6.
>> Current firmware - 4.3.2.1, as I
>> recall without going to look it up.
Ok, yeah, what Eric says… on a pure 1000/2000 system, 3.5.6 is your best bet currently. The focus in v4 is to get forward & backwards compatibility, as well as the ACwave2 chipset dialed in… 3.5.6 is good and mature on 1000/2000 systems. 
If v4 shouldn't be run on 1k/2k networks then the ePMP team should put v3.5.6 back in the firmware download section instead of making people go to the Archives to find it.
Also re-sticky the v3.5.6 post on the forum. Or , is v4.whatever the one true firmware for all radios now ?
It is more about known / unknowns. As the affectionately called "peon's" we have good insight (release notes) but not perfect insight to the changes being made. I would agree that running 3.5.6 is at least worth taking a look at to see if it resolves the issue.
A significant amount of changes are happening in the 4x firmware with no advantage that I am aware of over 3.5.6 for a pure 1000 / 2000 installation.
Also to your OP, I have seen this behavior on a 1000 system in the 5ghz band that directly related to interference. It was not obvious but a channel change resolved the issue for us. It only effected one of 4 AP's deployed on the tower and it only effected about 1/3 of the customers. The odd thing was that it effected the stronger signal customers more so we initially ruled out interference. Ultimately we believe that a local interference source in the area of the effected customers that is not a wifi transmitter is likely the cause.
Same issue here. I have several ap's that randomly drop all customers. It reports that it's transmitting and I am not using a DFS channel. Reboot doesn't seem to work, but power cycle does. This started with 4.3.2.1. I may have to roll the entire thing back to 3.5.6.
We are still waiting on someone at Cambium to explain the process of an ePMP-2000 SM when it is scanning and trying to lock onto its associated ePMP2000 AP....... both at initial power up and after a loss of RF connectivity between the SM and the AP.
@Danny Ray Boyer wrote:We are still waiting on someone at Cambium to explain the process of an ePMP-2000 SM when it is scanning and trying to lock onto its associated ePMP2000 AP....... both at initial power up and after a loss of RF connectivity between the SM and the AP.
As mentioned a bunch of times in this thread... there's problems with the 4.3.2.1 build on e1k/e2k radios. All of these problems will go away with 3.5.6. Just use 3.5.6 until 4.4 comes out.