I upgraded the AP to 3.1 final 46 minutes ago.
I already had 2 disconnections of all SMs on the AP.
I’ll upgrade some SMs to 3.1 to check their disconnections and let you know
EDIT:
Just checked all SM are 2.6.2 and only some SMs are 3.0.1 and they’re not disconnecting! I’m sorry for misunderstanding. I’m upgrading all to 3.1 to see if the problem is still there.
Sorry for multiple posts, but I want to help to check what is the cause of this problem :-)
I upgraded all SM to 3.1, and at the moment they're not disconnecting anymore.
I can confirm the issue seems to be 2.6.2: I have other ePMP 2000 APs with 3.1-RC30, with all users on 3.0.1, and no disconnections.
Performances are not so good: lots of SMs are choosing Sector instead of Smart Antenna (with 3.0.1 almost 95% was on Smart Antenna), and this means very low upload throughput.
EDIT (UPDATE):
After about 20 minutes of 3.1 I'm seeing multiple flapping from Smart Antenna to Sector of each user, and then disconnections of each one, one after another.
I'm now downgrading to 3.0.1 only the AP.
Hi Giuseppe,
I've sent you e-mail.
I would be grateful if you could provide access to your link to troubleshoot issue.
Thank you.
1 Like
@Chris_Bay wrote:
I'm not able to get a epmp2000 to link to a epmp1000 as a TDD SM or EPMP slave
running 40 mhz channel in DFS.
verfied Keys and netowork names, also tried with open secuirty.
they work fine swapping the roles.
Hi Chris,
Could you please specify which channel and Country Code is used?
I cannot reproduce described issue in 5.4 GHz band with US Country Code.
Thank you.
Ok, glad to see there's still some radar signatures outstanding. I rolled all our sectors to 3.1 last night and two started seeing DFS radar hits almost immediately once 3.1 was installed. Rolled back to 2.6.2.1 and issues went away.
OMG the speed!!! This feels so good.
1 Like
@Fedor wrote:
@Chris_Bay wrote:I'm not able to get a epmp2000 to link to a epmp1000 as a TDD SM or EPMP slave
running 40 mhz channel in DFS.
verfied Keys and netowork names, also tried with open secuirty.
they work fine swapping the roles.
Hi Chris,
Could you please specify which channel and Country Code is used?
I cannot reproduce described issue in 5.4 GHz band with US Country Code.
Thank you.
the AP is epmp 1000 lite, us model locked country code to united states
@its primary channel is 5275 @ 40 mhz. the 3.x DFS bug always hits that channel and it moves to its first alternate at 5280 @ 20mhz width and stays there. it is in TDD PTP flexible frame mode. same results in eptp master
the epmp2000 as the CPE set to connect to this AP, is set to listen only to the three dfs channels the AP is on, 5275 at 40mhz, 5280 at 20 mhz and 5285 and 20 mhz. the CPE this morning is repprting the wrong frequency. its not set to listen to 5560, but it shows the ap that is correctly sending on 5280 on that channel. attached is a side by side screenshot.
If i reverse roles, let the 2000 be the PTP master, everything works fine.
I'll PM you the config files for these radios also.
- e2k as SM not registering.png (186 KB)
Thank you for explanation.
Please send configuration files to: fedir.trutsko@cambiumnetworks.com
This will help as a lot.
Thank you.
Ugh! Just rolled my DFS AP to 3.1 right before you posted there are issues with DFS still. I'll let it sit since this is pretty disruptive on the customers and keep an eye on it. Otherwise, it's back to 2.6.2.1 again.
Could someone please help me with this error? This is on a subscriber module.
We currently don't use the RADIUS server, and I don't see any parameters in use in Monitor>Network.
- vlan error.jpg (21.5 KB)
I see that as well on a 1000 GPS AP but I don't get it on a 1000 non-GPS AP. Both have 3.1
Hi,
Thank you for your feedback.
Please skip incorrect Warning message, here the bug is.
You should just save VLAN and it will be applied on the ePMP device.
Thank you.
It won't let me access the radio remotely with the Vlan having the warning message. I was able to downgrade the firmware through the cnMaestro, then I could access it.
Could you please send me configuration files from AP and SM.
fedir.trutsko@cambiumnetworks.com
In bridge mode with only Management VLAN configured we don't see any issues except incorrect warning message.
Thank you.
I upgraded the radio again to 3.1 with it in bridge mode, and I had no trouble accessing it. When it was first installed I had it in NAT mode and was not able to access it remotely.
Thank you for sending configuration files.
We caannot reproduce issue with them as well.
So please just skip wrong warning message during configuration.
Thank you.
Encountering a webUI bug in 3.1 release - go to Configure->System and click on the Latitude field. Start typing in a latitude, like say 34.685105. It keeps trying to auto-correct away the decimal point then auto-correct the 'too large' value down to 90.
Same with Longitude. Oh, and if you type a leading "-" it auto-corrects that away as well.
I've found that if you type the next digit quickly enough it will retain the decimal point or minus sign, it only appears to auto-mangle if the non-numeric character is the last thing typed for more than about 1 second.
I've been battling my install/service crews forever to get near 90% compliance on GPS coordinates in SMs, now they have found another excuse... :(
j
Hi Joel,
Thank you for sharing this.
We will fix that issue as soon as possible.
Sorry for inconveniences.
Thank you.
Maybe it was a fluke thing. I have a couple installs today. I will let you know how it goes. Thank you
I tried it again, this time with a different AP and different SMs. All have same 3.1 firmware. I can’t access the SMs remotely nor ping them. I am able to access the AP with the 3.1 firmware.
I emailed you the configuration files on all 3.