Welcome @FlexiTog,

 

Hmmm, that is strange.  I doubt it's an issue with the EAP's themselves.  Seems more like an issue with the DHCP server / router / switch / cabling / power supply.  Especially if all of the EAP's are displaying the same behavior.

 

Are there other DHCP clients which are using the same DHCP server / router / switch / cabling?  And are these fine?  Is your DHCP address pool large enough?  How frequently are leases expiring / being renewed?

 

Are you running Omada all the time?  Ideally you would be.  Are the EAP's loosing connectivity to Omada during this time?

 

Please describe some additional details:

1) how are the EAP's powered?

2) what security / encryption approach are you using?  PSK, Radius, other?

3) If all of your EAP's are Ethernet connected MESH can be off.  If you're running Omada all the time, Fast Roaming should be on.

4) Make sure firmware and Omada are up to date.

5) I'd recommend static IP's for the EAP's instead of DHCP -- though I use DHCP for mine and it's fine.

6) Are there specific device types that are losing connectivity more than others?

7) Are there specifc AP's that are more impacted then others?

8) Are you using DFS channels?

9) Is this a new setup?  Or did you recently replace the AP's, or other components?

 

-Jonathan

@JSchnee21 

 

Hi Jonathan, 

 

Thanks for your quick response. 

 

 

In answer to your question.

1) how are the EAP's powered?

POE using a Netgear GS748TP should have ample amount of power of 802.3 

2) what security / encryption approach are you using?  PSK, Radius, other?

just the default settings  WPA-PSK 

3) If all of your EAP's are Ethernet connected MESH can be off.  If you're running Omada all the time, Fast Roaming should be on.

OK will adjust this and see what happens

4) Make sure firmware and Omada are up to date.

Yep ran this and have systematically checked that it's the latest version

5) I'd recommend static IP's for the EAP's instead of DHCP -- though I use DHCP for mine and it's fine. 

On the LAN I have set-up the AP to bind IP to MAC so these should effectively be static.  but 'm new to network set-ups / config 

so am a bit unsure what i should be setting the static IP, sub mask and gateway to? we have a leased line.

6) Are there specific device types that are losing connectivity more than others?

Mainly laptops - running windows (but not all laptops running windows!!?) 

7) Are there specifc AP's that are more impacted then others?

Its hard to say as people tend to desk-hop a lot and be in different parts of the office. but i know the one in the main upstairs office people who don't move about still have internet connection suddenly stop.. 

8) Are you using DFS channels?

no

9) Is this a new setup?  Or did you recently replace the AP's, or other components?

Relatively new as we had 2 TP-link AP's set-up in the warehouse and these worked fine, so decided to upgrade the others in the upstairs office and control them all through the Omada controller. 

 

since then the issues seem to have cropped up.

 

Regarding other settings. 

Router is a Draytek vigor2862

DHCP pool - was 154 ( should be ample for our staff ) but increased to 500 to test. 

Lease time - 259200

 

Omada is always running

Wiring should be all fine and switches have all previously been without issue. 

 

I was wondering about the fallback IP on each AP that gets assigned by default. as i  notice this just seems to assign a default IP in there - does this communicate with the dhcp to get this info? 

 

Thanks again for your help on this much appreciated. 

 

I'll update the thread if i notice any difference from changing the mesh, fast roaming, IP pool size etc. 

 

Many thanks,

 

Ben.