Hi @RaRu 

Thanks for posting in our business forum.

RaRu wrote

Hi,

 

I have two sets of ER706W in two different locations.

One is connected to 4G cellular network (modem is in bridge mode) - let's call it Side Office,

Second is connected to fiber 1/1Gbps network (directly to ONT) - let's call it Main Office.

 

Devices are connected via IPsec Site-2-Site, where Main Office is in responder mode. I do use DynDNS since public IPs may change.

Both sites are managed by one OC200 controller, placed in Main Office, connected directly to router, powered separately. Cloud access is enabled.

 

Since (about) a month I'm facing weird "freezez" of both devices which looks for me totally random and can happen at night, when there is no traffic in the network at all. It happens to both but not at the same time, every few days.

The freezes, looks the same for both routers: the device in theory is working (LEDs are blinking) but router is not responding:

1. Can't attempt to access it's webgui (address not responding) - both

2. Can't connect to WiFi - any attempt end up with failed connection - both

3. Side Office on Controller's dashboard looks like it is totally disconnected (no graph)

4. When Main Office's router is frozen, shows as Offline Controller in cloud access

5. After router's reboot (point 4) Main Office on Controller's dashboard from that time shows as connected, but there was no traffic, PING line was totally flat and constantly on value 1mc (which is impossible, minimum ping is 6ms)

 

The only thing I can do to make those devices work then is to manually restart those (reconnect to power supply).

 

I do have some more configuration on Main Office router (few subnets, IPsec and OpenVPN server, DynDNS, some ACLs) but Side Office router has almost no specific config (IPsec, DynDNS only).

 

No device error is showed in logs, no massive CPU/memory usage/spikes, no traffic before/during those freezes.

The only thing that comes to my mind is the last update (1.1.2) - but I'm not 100% sure if the problems started after that upgrade or some time before.

 

What should I check in that case? Are there any additional logs somewhere available or only those I can see in controller's log section? Anyone faced the same issue by any chance?

 

Thanks for any tips.

Cheers!

 

Based what I read, I am more into this question:

Are you able to ping the gateway while it looks like "dead"?

What do you mean by the highlighted part?

You cannot even connect to the WIFI. When you wire to the router, do you get an IP address? It gives me a feeling that the router crashes. I think you need to verify both ends as you describe there are two routers and they behave the same. They do not have similarities but they create the VPN. I am curious if it is the VPN that caused the problem and crashed them so they behave in this way randomly.

Hi @RaRu 

Thanks for posting in our business forum.

RaRu wrote

  @Clive_A 

 

Hi,

 

Scheduled restarts (at least once a week) were not enough to "fix" the issue. Today the router died again, during workday. Last Reboot was during sunday's night.

The last logs before it died are:

 

 

So nothing really informative. The WAN port was not responding. I don't know about LAN.

 

Unfortunately, the device is in remote location and the users there were not able to test anything. I'll keep trying tho.

 

Simple restart (reconnect to power supply) "fixed" the case. Question is - for how long?

 

I don't want to set daily reboot schedule. I don't believe that's a proper solution imo.

I understand. What I want to learn is still not answered.

Is this a WAN issue or does the router completely crash? That's what I want to learn by pinging the LAN IP address which I ask you to perform earlier in the conversation.

If you could clarify, I can decide if this goes to the dev to collect the debug log or if I can try something else.