It's hard to trouble shoot behaviour which happens only rarely. When it happens next time, don't forget to thoroughly check the logs, there might be something in it. Another thing to do is to create supout.rif file and send it to Mikrotik support ... they might decode the device state and comment on what might have happened.
I'd suggest you to make sure your device is running latest stable ROS version (if your device is currently running v6, then that would be 6.49.17; if your device is running v7, then that would be 7.16.2). Make sure routerboot (System->Routerboard) is upgraded as well. There are some firmware upgrades available for LTE modems as well, consult LTE modem upgrade guide to see how that is performed.
If software/firmware upgrades don't make a difference, then you can implement a work-around using netwatch ... netwatch, running on LHG itself, might be able to detect sluggishness and reboot device ... in this case the service impact will likely be much shorter than with manual reboots.
I'd suggest you to make sure your device is running latest stable ROS version (if your device is currently running v6, then that would be 6.49.17; if your device is running v7, then that would be 7.16.2). Make sure routerboot (System->Routerboard) is upgraded as well. There are some firmware upgrades available for LTE modems as well, consult LTE modem upgrade guide to see how that is performed.
If software/firmware upgrades don't make a difference, then you can implement a work-around using netwatch ... netwatch, running on LHG itself, might be able to detect sluggishness and reboot device ... in this case the service impact will likely be much shorter than with manual reboots.
Statistics: Posted by mkx — Thu Jan 09, 2025 8:58 am