Signal strength too strong?

Cellular Routers
,
1

We have a IX10 configured and run for few days at our shop, standard configuration. Shipped out to site and project is started up on Monday morning. By Monday afternoon the site has gone into com fail, and modem remains offline until Tuesday morning. I log into the modem and see that it has rebooted so I assume the Surelink got to that stage. By Tuesday afternoon it has once again gone into com fail and remains so. The SIM (Verizon) is offline.

One thing I did catch when logging into the modem yesterday was the signal strength was good:bars=5
dbm=-51
lte_rsrp=-59.0
lte_rsrq=-11.0
lte_rssi=-34.0
lte_snr=24.0
rsrp=-59.0
rsrq=-11.0
rssi=-34.0
snr=24.0
temp=21C

I am use to sites that have -105 to -110+ signal strength that go for weeks without failure. Is it possible the signal is too strong, and something configuration wise needs to be adjusted? I am at a loss for why this would be going into com fail with this signal.

Edit: Surelink is configured to ping 2 IPs, with requirement only 1 passes and this is set now for every 2 minutes. Update routing & Switch SIM disabled. Restart, Reset, and Reboot are enabled.

2

I have never heard of a too high signal causing a reboot. What I would suggest is submitting a case via my.digi.com and provide the log from the IX10.

3

The reboots are assumed due to Surelink heatbeat running through its process. The issue at hand is more that we have a significantly high signal strength and yet are losing connectivity daily for hours.

Problem is this modem is in another state, I only have access when it is online. It comes online, as today, I can access is about 20 minutes after it has restarted. As a result, not much logging to gain.

4

What I would suggest is setting up an Automation in remote Manager to download the logs from the gateway. This way, when it comes online, it will download the files. You can then provide the Support logs to Digi Support. Note that the logs carrier more information than just the Surelink and may point to why the issue is occurring. It may also allow Support to make suggested configuration changes to keep the issue from occurring.