LTE CAT6 modem disconnecting every 2-3 minutes

WeWiNet

Yes, I not know you script you have but the any startup stuff must have got some delay.
Even the /system reset-configuration run-after-reset=WithDelay.rsc must have added delay like 20s because it’s not work. Means every export to file not will be works here as out-of-box and the “delay 20” must be added at first.

I see post’s at forum when the “/interface lte set lte1 modem-init=” is not used and MikroTik employe give info to add scheduler with delay.
This is another good tip to have in memory. I hope this was a real problem here. Good Luck.

Hi SIB,

I confirm for now, with LTE interface delay, my router continues to work correctly.

But I think it is not correct to depend on the user to foresee delay (how much???) when switching on/off an interface:
Example in my case:

  • Netwatch starts at boot (but when???)
  • In boot script I disable first thing the netwatch script (but when???).
    Guess what happens? → Boot script runs before or after netwatch is configured and therefore either I can’t disable it really
    or Netwatch already brought up LTE…
    In my case Netwatch starts to work (I see the log) and then stops luckily before LTE went up… not a clean way to do things.

I have a workaround now but think ROS should take care of boot times/status of external modules (within the product) without having
user to add arbitrary delays…!

The good (or in this particular case: bad) thing about ROS is that it’s completely open for everybody to adapt it according to their needs. So it’s mighty hard to foresee everything in advance to make systematic work-arounds.

For example: netwatch is a generic command that checks L3 connectivity. It doesn’t have any fine tuning parameters (such as defining route towards test target) and it relies on general router setup (which is mostly fine, but I can think of cases when one would prefer to have more control). Ditto for up/down actions, they are normal scripts. And I can imagine that not all interfaces are equal. For example, an ethernet interface with static IP set can be up and running within milliseconds after both ends enable their interfaces.

Broadband modems are on the other extreme end regarding startup time … some time is taken by modem initialization (and it largely depends on modem type), some more time is taken by modem to find and register to mobile network … this depends a lot on modem settings and on mobile network as a whole. Then it comes to data link establishment (in legacy technologies this is a separate operation and takes some time to authenticate user in MNO’s core network while in LTE this is usually part of registration procedure). Which means that script which performs action on LTE modem should take these peculiarities into account … e.g. skip the action on host down if ROS uptime is less than say 1 minute or delay script termination by 30 seconds after modem is being reset or something like this.

I have many scripts/schedulers but any of them are not interference that way to r11e-lte6 stops working properly. I don’t understand what your script can execute who will be that mess.
My netwatch have got 10s interval and even is down-script have got at+reset then still works fine.
You can do few stuff.
Check when netwatch/scheduler start working - you can add line to generate a blue log entry to see every running of script in logs..
.

log warning ("UPTIME: ".[/system resource get uptime ])

.
You can add at start of any script just exiting is uptime is not 5m by:

local uptime [/system resource get uptime ]; if ($uptime < 5m) do={:error "Not now" };

.

I have a workaround now but think ROS should take care of boot times/status of external modules (within the product) without having
user to add arbitrary delays…!

Write it to support@mikrotik.com

Hi SIB,

Today I had again a couple of link downs after 25 minutes good LTE connection with the modem
stuck on same problem as I described earlier (not using any cell lock or so).

So my “workaround” did not really solves the issue.

I might need to move back to my RB4011 and use external LTE router!!!

WeWiNet

Summary:
#1 you show some lte logs but not all and I write you to enable full logs and lte export in #2 - you not provide this.
#3+#5 you write about “Rx/TX disabled, not searching”
like in Cell/Freq Lock with bad settings.
#8 you write that “AT*CELL=0” give you “+CME ERROR: phone failure” or even “output: ERROR”
This is total bad like you have different modem from r11e-[ lte | lte6 ] but you still not provide full info or export of configuration.
I never see this on my r11e-lte6.
#11 Support of MikroTik write you to send them description to support@mikrotik.com
but you not write about this.
#12 I write you to give “info lte1”, prints from cli. Give you alternative modem on your request.
#15 I write you again request about logs and give hint that +CFUN is responsible about modem functionality mode.
#18 LOGs !!! with wrongs AT answers on common commends. Too strange and I write about warranty.
#20 You write about some start-up scripts but you not provide any export etc.

Now:
I still assume that your signature means we speak about ltap-mini but with what modem? I still don’t know, because it can be buy without it and modem can be added. Modem version’s US/4G/LTE/LTE6 works differ.
Maybe you works on old v6.x version and never do a modem upgrade by " interface lte firmware-upgrade lte1".
Maybe the at*cell is not proper for your and before error’s are normal.

Still the errors #18 should work and if all this is not releated with ISP or just SIM card then you should use a warranty and write to support@mikrotik.com long ago. They can install you a new releace candidate modem firmware v22, check logs from supout.rif or from your device etc. Realy. Without checking your export to finding kill-herself behavior in scripts/netwatch/etc. and bad doings the MTK Support can recommend you write RMA.
In my possition of regular user who read manual and can use google to do additional searching I can write you in my opinion new firmware or warranty are your way to solve your case.

Some person’s write me PM into links from my signature and we do remote assistance with call. Firmware/Warranty is your way or bad configuration with scheduler who do every 2m the usb power-reset.
I hope you learn someting from my answers.
BR Marcin

Hi Marcin,

I highly appreciate your effort to help me debug my setup!
For instance I was not aware of the delay you can add with “uptime”, which helps me for other things as well!
Therefore thank you for all your good advice. You are for me Mr. LTE!!!

Right now I can’t and don’t want to spent much more time on debugging it.
It works so-so which is for now enough (and I like the Audience for the rest of its Wifi functionality).

For completeness my config below. As you see it is as basic as it could be. When I drop my SIM card in an ASKEY LTE router,
a Laptop with 3G modem etc it always “just works”, (and in general gives me higher data rates than the LTE11-CAT6 modem).

/interface lte export
/interface lte apn
add apn=my-apn name="My-APN-Name"
/interface lte
set [ find ] apn-profiles="My-APN-Name" mac-address=xx:xx:xx:xx:xx:xx mtu=1480 name=\
    WAN2-LTE network-mode=3g,lte

Subject closed :slight_smile:
PS: If I go to Prague, I pay you a beer, how about that ?

WeWiNet

.
Beer Accepted, I will be in Prague and I just create a t-shirt with my avatar and footer/signature on it. Beer connecting ppl :slight_smile:

I have this issue on the new Mikrotik LTE Audience.

  • I have upgraded to latest lte modem firmeware.
    I have tested all different routerboard software (testing/beta/stable)
    Upgraded routerboard firmware.

I can reproduce this issue with LTE disconnecting by just starting a simple speedtest.

Any news on a working workaround, or is it a hardware bug? I have another Mikrotik Chateu LTE router, and it is working just fine…

Watch LTE parameters: http://forum.mikrotik.com/t/sxt-lte-4g-cat6/134468/1
Enable logs: /system logging add topics=lte

with this you can see when and how often the cell/tower will be change - this should be start point for you.

Good afternoon. I have a similar problem. Yesterday i installed a new Mikrotik RBwAPGR-5HacD2HnD, Ros version 6.47.8, modem firmware version R11e-LTE6_V026. Approximately every 60-120 minutes, the connection breaks “failed to register on network”. Is this a common problem with this modem or is there already a solution?

https://prnt.sc/w4r6t9

That behavior is know from few problems and you have enabled logs but not show all who do breake.

You should show logs from before brakes happend, only some lines give me a clue…

Please public the result of:
/log print file=log.txt

You can search if you have got a error just after SIMDETECT=2,NOP - if yes then this is solved in new firmware. Then please write to support@mikrotik.com or https://mikrotik.com/support

Hi! I have exactly the same problem with my lhg lte6 kit. Modem disconnects every 30-40 minutes with “failed to register on network”. firmware R11e-LTE6_V026, ros 6.48
log screenshots are here https://prnt.sc/wfhk50, https://prnt.sc/wfhknh

any help here? I really have no idea with that. I’ve found a similar problem http://forum.mikrotik.com/t/ltap-lte6-regularly-disconnects-from-lte-network/145789/12

I heard 2 things to try.

  1. is to bulk up your sim card with some tape at the back of it to ensure its pushing up against the pins, as apparently some sim’s are thinner than the specification
  2. There is a beta v027(as of Jan2021) that mikrotik can send you. They will also ask you to put the current LONG-TERM RoS on your device with that update too.

Ensure your power supply can supply the amperage too. !
Whats your signal levels too when its is runnings ?

Tech support Mikrotik recommended me to stick tape on the back of the SIM card. So-so solution, did not try. With the SIM card of another operator, there were no breaks, the thickness is the same. As a result, we decided to take the Mikrotik to the store, and instead buy a regular router, which was sold by the telecom operator itself. With their router, everything works stably, while it is 3 times cheaper. For the home, this router is enough with the head, users are happy. I came to the conclusion that the problem is a conflict between the equipment or networks of a particular provider and the Mikrotic modem. In this case, we decided not to go too deep into the reasons and replaced the router. I have already installed several hundred Mikrotiks of various models and never had any problems.

It is possible to lock R11e-LTE6 modem in hAP ac3 to work only on Primary band? When modem using primary-band and ca-band it is unstable.
When modem using Primary-band B7@15MHz and ca-band B3@10MHz connection was lost every 30-60 minutes. When modem change primary-band to B1 and ca-band to nothing, signal is stable, connection too (9hours).

Distance to tower is ~200m.

When primary-band: B7@15MHz and ca-band: B3@10MHz

When primary-band: B1@10MHz and ca-band: B20@10MHz

I have ROS v6.46.8 (long-term) and R11e-LTE6 V026.

Feb/03/2021 23:51:13 script,warning primary-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/03/2021 23:51:13 script,warning ca-band:  -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 00:48:40 script,warning current-cellid: 57376799 -> 57376819
Feb/04/2021 00:48:43 script,warning primary-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 00:48:43 script,warning ca-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> 
Feb/04/2021 00:51:22 script,warning ca-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 00:51:49 script,warning ca-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 00:55:22 script,warning ca-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 01:06:29 script,warning current-cellid: 57376819 -> 
Feb/04/2021 01:06:29 script,warning enb-id: 224128 -> 
Feb/04/2021 01:06:29 script,warning primary-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> 
Feb/04/2021 01:06:29 script,warning ca-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 01:07:36 script,warning current-cellid:  -> 57376789
Feb/04/2021 01:07:36 script,warning enb-id:  -> 224128
Feb/04/2021 01:07:39 script,warning current-cellid: 57376789 -> 57376799
Feb/04/2021 01:07:42 script,warning primary-band:  -> B1@10Mhz earfcn: 54 phy-cellid: 75
Feb/04/2021 01:07:42 script,warning ca-band:  -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 01:07:45 script,warning primary-band: B1@10Mhz earfcn: 54 phy-cellid: 75 -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 01:12:51 script,warning current-cellid: 57376799 -> 57376819
Feb/04/2021 01:12:54 script,warning primary-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 01:12:54 script,warning ca-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> 
Feb/04/2021 01:50:54 script,warning ca-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 01:51:15 script,warning ca-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 03:09:35 script,warning current-cellid: 57376819 -> 57376789
Feb/04/2021 03:09:38 script,warning primary-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> B1@10Mhz earfcn: 54 phy-cellid: 75
Feb/04/2021 03:19:54 script,warning current-cellid: 57376789 -> 57376819
Feb/04/2021 03:19:57 script,warning primary-band: B1@10Mhz earfcn: 54 phy-cellid: 75 -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 03:41:43 script,warning ca-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 03:43:11 script,warning ca-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 05:10:37 script,warning ca-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 05:10:55 script,warning ca-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 05:40:52 script,warning current-cellid: 57376819 -> 57376789
Feb/04/2021 05:40:55 script,warning primary-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> B1@10Mhz earfcn: 54 phy-cellid: 75
Feb/04/2021 10:16:58 script,warning current-cellid: 57376789 -> 57376799
Feb/04/2021 10:17:01 script,warning primary-band: B1@10Mhz earfcn: 54 phy-cellid: 75 -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 10:17:01 script,warning ca-band:  -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 10:24:04 script,warning Internet  is down
Feb/04/2021 10:24:11 script,warning current-cellid: 57376799 -> 
Feb/04/2021 10:24:11 script,warning enb-id: 224128 -> 
Feb/04/2021 10:24:11 script,warning primary-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 10:24:11 script,warning ca-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> 
Feb/04/2021 10:25:17 script,warning current-cellid:  -> 57376819
Feb/04/2021 10:25:17 script,warning enb-id:  -> 224128
Feb/04/2021 10:25:17 script,warning primary-band:  -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 10:25:17 script,warning ca-band:  -> B7@15Mhz earfcn: 3025 phy-cellid: 75
Feb/04/2021 10:25:30 script,warning Internet is up
Feb/04/2021 10:26:44 script,warning current-cellid: 57376819 -> 
Feb/04/2021 10:26:44 script,warning enb-id: 224128 -> 
Feb/04/2021 10:26:44 script,warning primary-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> 
Feb/04/2021 10:26:44 script,warning ca-band: B7@15Mhz earfcn: 3025 phy-cellid: 75 -> 
Feb/04/2021 10:27:00 script,warning Internet is down
Feb/04/2021 10:27:39 script,warning current-cellid:  -> 57376779
Feb/04/2021 10:27:39 script,warning enb-id:  -> 224128
Feb/04/2021 10:27:42 script,warning current-cellid: 57376779 -> 57376820
Feb/04/2021 10:27:42 script,warning ca-band:  -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 10:27:45 script,warning primary-band:  -> B20@10Mhz earfcn: 6200 phy-cellid: 63
Feb/04/2021 10:27:45 script,warning ca-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> B20@10Mhz earfcn: 6200 phy-cellid: 64
Feb/04/2021 10:27:48 script,warning current-cellid: 57376820 -> 57376819
Feb/04/2021 10:27:48 script,warning primary-band: B20@10Mhz earfcn: 6200 phy-cellid: 63 -> B3@10Mhz earfcn: 1749 phy-cellid: 76
Feb/04/2021 10:27:48 script,warning ca-band: B20@10Mhz earfcn: 6200 phy-cellid: 64 -> B20@10Mhz earfcn: 6200 phy-cellid: 63
Feb/04/2021 10:27:51 script,warning primary-band: B3@10Mhz earfcn: 1749 phy-cellid: 76 -> B3@10Mhz earfcn: 1749 phy-cellid: 75
Feb/04/2021 10:27:54 script,warning current-cellid: 57376819 -> 57376779
Feb/04/2021 10:27:57 script,warning current-cellid: 57376779 -> 57376789
Feb/04/2021 10:28:00 script,warning Internet  is up
Feb/04/2021 10:28:00 script,warning primary-band: B3@10Mhz earfcn: 1749 phy-cellid: 75 -> B1@10Mhz earfcn: 54 phy-cellid: 75

It seems that you have defective of your antenna or modem unit.
Go on with your router to reseller for warranty, they should replace it to you.
At least I had such kind situation with my LHGG LTE6.

You have change BTS/eNB few times and theyr antennas… like it’s not stable connection to one antenna.
It’s like modem try to hard to connect and cannot select one proper bts.

We cannot disable 2CA at R11e-LTE6 but you can just enable one Band and this lock you at one band only.
Then you can still have changes between this one Band but you say B1 is stable if it’s not 2CA, maybe other better Bands will work for you.

Other way is just lock to specific BTS Antenna - this is only selective for Primary Band.
e.g. of your logs: → B3@10Mhz earfcn: 1749 phy-cellid: 75
Then https://wiki.mikrotik.com/wiki/Manual:Interface/LTE#Using_Cell_lock

  • Cell Lock /interface lte at-chat lte1 input=“AT*Cell=2,3,1749,75”
  • FreqLock /interface lte at-chat lte1 input=“AT*Cell=1,3,1749”

Poland ISP Freq from UKE:
UKE B3_1_7.png

P.S. You can write me at Telegram message. Zapraszam.