Hi  @CraigMcQ 

Are they more stable?

Yes.

Please update your EAP to the latest version, as well as the Omada controller.

BTW, does the behavior remain the same as before?

Hi  @CraigMcQ 

We are very concerned about your feedback.

Did you update the firmware? Has the issue been resolved? 
 

If not, please kindly give us the following details for further troubleshooting:

1. You previously mentioned that you have configured 5 personal (PSK) encrypted SSIDs and 2 enterprise (802.1X) SSIDs. When the issue occurred, did you try connecting to both personal and enterprise SSIDs separately? Were all the enterprise and personal SSIDs failing to connect?

2. You mentioned not using an OC200. Are you managing these two EAP660s via the standalone web interface, or are you using a software controller?

3. When the issue occurred, were all types of devices unable to connect to the SSID, or only specific device(s) failing to connect to the EAP's SSIDs?

Hi  @CraigMcQ 

Thank you for the quick reply.

I should find out on around 27 September if it is more stable.

>>>Looking forward to your update at that time.

3. It's difficult to say, because I have two EAP660 HD, and only one had been running for > 50 days. The other had only been running for about 36 days. So results depend on which EAP660 HD devices tried to connect to.

>>>Does this mean clients originally connected for 50 days will be disconnected from this EAP and reassociated to the other EAP?

Do the two EAP sharing the total same SSID settings? If not, can you distinguish it from the SSIDs? For example, when EAP_1 running after 50 days, will all clients connect to EAP_2's SSID?

@CraigMcQ 

Since the issue doesn't occur frequently, I recommend collecting all the necessary information at once the next time it happens. This will help us pinpoint the root cause and resolve it as soon as possible.

To assist with this, I've sent you an email listing all the required details. Please check your inbox, the case ID is TKID250826006.