Hi
i have every night (but only during the night) lots of log messages “forced reconfiguration due to difficulty setting link up”
Lhgg passtrough the private ip (10…) to one hapac2.
I never know this message on others installations with same configuration and material
may be it’s because antenna operator slow down signal every night (for energy saving) ?
I think this has been introduced in RouterOS 7.17. Rolling back down to 7.16.2 - I was unable to get the error/message again unless I didn’t wait long enough.
RouterOS 7.17-7.12.2 - error says “forced reconfiguration due to long search time”
RouterOS 7.18 & above - error says “forced reconfiguration due to difficulty setting link up”
I’m seeing this on the older LHG LTE as well - probably applies to all MikroTik LTE devices. I’m only able to reproduce the error if I purposely choose a band that doesn’t exist in my area = no signal. This might be a debugging feature but it seems very unclear what it actually does when it says “forced reconfiguration” since all the lte settings remain the same - maybe it does something with the modem directly.
Checking the changelogs on 7.17 (unless I’m blind) but can’t find out where it mentions that change at all.
I have never seen those script errors before - are they yours or is that the watchdog feature? (I’ve never used it)
Starting to see this behaviour on hAP ac3 LTE running 7.18.2 aswel…
We’ve got two NetWatch scripts running to detect a non working LTE interface.
The first script runs frequent and disables, waits and re-enables the LTE interface, this often (not always) fixes connectivity issues.
The second script runs daily and reboots the complete router
The issue we are recently (not really sure since which RouterOS version) seeing that indeed daily the LTE stops working in the end of the evening and gets back in the morning arround 11:00 with this log-message:
“forced reconfiguration due to difficulty setting link up”
The message “forced reconfiguration due to difficulty setting link up” means that the lte interface was not in running state for 2 minutes (default value) so it is reconfigured (basically the same as disable/enable). You should look into the reason why the interface is not in running (R) state. If it is still unclear why it is reconfigured please create a support ticket.