Hello everybody,
I have serveral Chateau models using lte interface with problems.
The router that fails the most is a Chateau S53UG+5HaxD2HaxD&FG621-EA with 7.18.2 routeos and mostly every day the lte1 interface is Inative throwing to the log this errors every second:
lte1 mbim: >>> E #88501 - connect: radio state, error: FAILURE
The interface can’t be disabled because is inactive. The only way I’ve found to get it working again is to restart the router or applying a firmware update to the interface if exist. But after a few hours or the next day the interface is inactive again.
The Interface list most of the days show the error coment (in red) --modem failed or just Inactive.
interface/lte/print
Flags: I - INACTIVE
Columns: NAME, MTU, NETWORK-MODE, APN-PROFILES
# NAME MTU NETWORK-MODE APN-PROFILES
;;; modem failed
0 I lte1 1500 3g default
lte
The lte interface model is FG621-EA with the lastest firmware version (16121.1034.00.01.01.09).
If I install the SIM card in a mobile phone, it works perfectly. So I have discarted an issue with the SIM.
I have a total of 14 Chateau routers all with the lte as backup, 3 of them are the mentioned model and they are the ones that are failing the most, one of them daily.
Could you provide me some advice to try to understand the problem or to solve it?
This sounds like a bug. As I suggested in other thread, I’d make sure the /system/routerboard “RouterBOOT” firmware is running 7.18.2 firmware. If it is, then I’d try the 7.19beta as a test/workaround.
Yes, the RouterBOOT firmware is running the 7.18.2 version.
The issues are the same as before installing the latest LTE firmware 16121.1034.00.01.01.09, now are much more frecuently.
I will try to update one of the routers to 7.19beta to check if the issues persist.
Is there any command to restart or reboot the LTE interface? Just like when you apply a firmware update, that the interface reboots to apply the new firmware
The “bus=0” may be bus=1 etc… — I don’t have Chateau with FG621 to check. Also duration= might be shorter if you like… but often modem do have some residual power and you likely want RouterOS “USB hotplug”-equivalent to have time to remove / add modem, so duration of 15 seconds is shown.
edit: originally shown bus=0, but bus=2 is reported at the right one for this chateau.
Yeah RouterOS has to have time to detect it gone and reinitialize, and often 10 seconds was too short on other modem… so good to see the “force” the minimum duration in power-reset (which may reflect some 30 second timeout in MBIM/LTE stuff… since modem SHOULD actually restart itself).