@BulldogEngineer 

BulldogEngineer wrote

I woke up this morning to no internet. No wifi or ethernet. The router had a heartbeat as did the OC300 and the main switch SG3428MP v6.20. The ATT residential gateway was green. I finally had to powercycle everything to restore service. The logs indicate this:

 

A8-6E-84-F5-86-1C: The online detection result of [2.5G WAN/LAN1] was offline.      May 29, 2025 01:36:39 am

 

At 01:33 am you see where the router was able to get the DHCP address for the WAN and then another device on the network, then everything stopped.

 

Just shortly after at May 29, 2025 01:45:33 am the OC300 controller goes offline which is plugged into the ER7412-M2. Every other device on the network and clients all go offline.

 

I don't see anything else in the logs. A powercycle of the ATT residential gateway did not fix it leading me to powercycle the OC300, ER7412, and the SG3428MP. I suspect it was the router though.

 

Any thoughts?

 

Offline is not a proper way to describe the devices in the LAN.

So, you are saying they are offline from the Omada Cloud?

If they are offline from the Cloud, meaning your WAN is down. Which fits what's been written in the log.

Then you need to take a peek at the ATT modem.

It loses all the ping to the external sites, so it shows as disconnected(no Internet) on the router. You might wanna test the ATT.

  @Clive_A Hello Clive and thanks for the response. Yes, every device and every client had a status of offline in the logs. The AT&T modem/gateway seemed fine. It is in passthrough mode so it acts as a modem rather than a router/gateway. The ER7412 is configured for dynamic IP to pull the IP address from the AT&T modem every 10 minutes and it seemed it just stopped. There is nothing else in the logs after it wrote that it said the wan was down. The ER7412 was essentially locked up and powercycling it, the switch and OC300 was the only fix. I have since adjusted the DHCP lease time on the AT&T gateway from every 10 minutes to once per day. I am added a backup fiber line today so if this happens again possibly it will failover to it. But, even if you can't get to the internet you should still be able to get to the OC300 on the LAN. It was totally inaccessible as well.

All very strange.

Brian

  @BulldogEngineer 

BulldogEngineer wrote

I also adjusted the WAN detection interval from 10 seconds to 15 to see if perhaps that was better. This was probably just a transient case, but it was concerning the entire router would just lock up. Without more logs, there's no other indication of what went wrong. I've also adjusted the lease time on the LAN from every 120 minutes to 7 days. This is a residence and not a business, so grabbing a new DHCP lease every 2 hours is excessive. Thanks again, Brian

Lease time is not important in this situation. If it is a WAN problem, changing the LAN DHCP lease time would never do any good.

120 or 1440 minutes would be fine for any situation. Increasing that time sometimes would not make your network run well. It depends.

Anyway, if the ping or resolution continues to fail, that's a problem with the WAN stability. Possibilty ISP side.

  @Clive_A appreciate the feedback Clive. Thanks again.