@MR.S 

I've tried switching out the router with a pfsense router... It ends up doing the same thing...

I believe it's something with the switch, it refuses to respond to the router port, just turns off, it happens with my omada router and pfsense router where they no longer get a signal from the switch.

I tried moving the cable to a different port and that doesn't solve it, rebooting the switch fixes it temporarily but the issue comes back. 

I'm going to try factory resetting, and building the set up from scratch for all of it. 

  @Medster87 

Have you done switch acl? If yes. My-bee you have close your self out from the network. 

  @MR.S 

No switch ACL, but it maybe that the port for the router is being switched from 1000 duplex to 100 duplex and since I don't have my router on auto it stops responding ?

I've currently forced the port to be 1000duplex to see how that will work out and will report back.

  @MR.S 

My net just crashed again and the DHCP server failed, I am using my pfsense to have more accurate logs

Below is the log when my internet stops working and wifi and no ips, I assume it's either the switch or controller as changing the router doesn't fix the issue, I am currently gonna try adding a regular switch between my main switch and router and see if this does anything.

May 26 14:23:42 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000] COMMAND_RECEIVED Received command 'lease4-get-all'
May 26 14:24:38 ZimaBoard dhcp6c[63902]: Sending Solicit
May 26 14:24:45 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000]  COMMAND_RECEIVED Received command 'lease4-get-all'
May 26 14:25:47 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000] COMMAND_RECEIVED Received command 'lease4-get-all'
May 26 14:26:41 ZimaBoard dhcp6c[63902]: Sending Solicit
May 26 14:26:50 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000] COMMAND_RECEIVED Received command 'lease4-get-all'
May 26 14:27:53 ZimaBoard kea-dhcp4[14117]: INFO [kea-dhcp4[.]commands[.]0x3a9c5aa12000] COMMAND_RECEIVED Received command 'lease4-get-all'
May 26 14:28:33 ZimaBoard dhcp6c[63902]: Sending Solicit
May 26 14:28:55 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000] COMMAND_RECEIVED Received command 'lease4-get-all'
May 26 14:29:58 ZimaBoard kea-dhcp4[14117]: INFO [kea-dhcp4[.]commands[.]0x3a9c5aa12000] COMMAND_RECEIVED Received command 'lease4-get-all'

This all repeats until 

May 26 15:11:16 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
May 26 15:11:16 ZimaBoard kea-dhcp4[14117]: INFO  [kea-dhcp4[.]commands[.]0x3a9c5aa12000] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /usr/local/sbin/kea-lfc -4 -x /var/lib/kea/dhcp4.leases.2 -i /var/lib/kea/dhcp4.leases.1 -o /var/lib/kea/dhcp4.leases.output -f /var/lib/kea/dhcp4.leases.completed -p /var/lib/kea/dhcp4.leases.pid -c ignored-path
May 26 15:11:16 ZimaBoard kea-dhcp6[14567]: INFO [kea-dhcp4[.]commands[.]0x3a9c5aa12000] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
May 26 15:11:16 ZimaBoard kea-dhcp6[14567]: INFO [kea-dhcp4[.]commands[.]0x3a9c5aa12000] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /usr/local/sbin/kea-lfc -6 -x /var/lib/kea/dhcp6.leases.2 -i /var/lib/kea/dhcp6.leases.1 -o /var/lib/kea/dhcp6.leases.output -f /var/lib/kea/dhcp6.leases.completed -p /var/lib/kea/dhcp6.leases.pid -c ignored-path

  @Medster87 

Have you tried a factory reset of the switch? if not, try, see if everything works before adopting it to the controller again

  @MR.S 

Next time it fails I'll do that

  @Hank21 

I do have VLAN settings, everything works fine and all VLAN IPs are assigned properly... For a while. It used to last a few days and then it would fail. Now, it seems it's been doing this on a daily basis. When the failure happens all wireless clients aren't being assigned an IP both those with reserved IPs and without.

I haven't tried pinging the switch, I'll do that when the next failure happens.

  @Medster87 

Everything has been up for 23hours before the port that is connected to my router just switched off...

I don't know why, it was sudden, I am able to access all other wired devices in the network but the router is unreachable and with it the internet.

I will try to forget the switch and have it run standalone mode and see if that makes any difference.

@Hank21 

@MR.S 

This time I made sure to only have the router as a DHCP server (seems I also had the server on the switch).

The port that's connected to the router just stopped working and nothing was connecting, wired or wireless. I changed the port to another one and it all started working again, I am sure it's the switch that is the issue.

I am changing the port from loopback control to spanning tree, maybe that will help.