LTE interface going up/down on chateu ax lte6

RouterOS Wireless Networking
1

Hello,

So I bought a new chateu ax lte6 and put in my lte card. Setup everything and it’s working. However, spuriously its LTE interface would go down. Here is a log:

08:43:57 lte,async,raw lte1: sent AT+GTCAINFO?
 08:43:57 lte,async,raw lte1: rcvd +GTCAINFO:
 08:43:57 lte,async,raw lte1: rcvd PCC:107,101,3350,100,1,62,15,4,59,2693,21350
 08:43:57 lte,async,raw lte1: rcvd SCC1:2,0,103,380,1550,100,0,70,19,0,0,-1,19550
 08:43:57 lte,async,raw lte1: sent AT+GTCCINFO?
 08:43:57 lte,async,raw lte1: rcvd +GTCCINFO:
 08:43:57 lte,async,raw lte1: rcvd LTE service cell:
 08:43:57 lte,async,raw lte1: rcvd 1,4,284,05,23B,A853F,D16,65,7,100,4,62,62,15
 08:43:57 lte,async,raw lte1: rcvd 
 08:43:57 lte,async,raw lte1: rcvd LTE neighbor cell:
 08:43:57 lte,async,raw lte1: rcvd 2,4,,,,,D16,17C,,61,61,13
 08:43:57 lte,async,raw lte1: rcvd 2,4,,,,,D16,1E4,,58,58,8
 08:43:57 lte,async,raw lte1: rcvd 2,4,,,,,60E,65,,65,65,9
 08:43:57 lte,async,raw lte1: rcvd 2,4,,,,,60E,1E4,,63,63,4
 08:43:57 lte,async,raw lte1: sent AT+GTANTINFO?
 08:43:57 lte,async,raw lte1: rcvd +GTANTINFO: "0",60,18
 08:43:57 lte,async,raw lte1: rcvd +GTANTINFO: "1",62,15
 08:43:59 lte,async,raw lte1: +CGREG: 1,"0241","000A853F",7
 08:43:59 lte,async,raw lte1: +CEREG: 1,"023B","000A853F",7
 08:43:59 lte,packet,raw lte1 mbim: wdm >>> recv #0
 08:43:59 lte,packet,raw lte1 mbim: 07000080 7c000000 00000000 01000000
 08:43:59 lte,packet,raw lte1 mbim: 00000000 a289cc33 bcbb8b4f b6b0133e
 08:43:59 lte,packet,raw lte1 mbim: c2aae6df 09000000 50000000 00000000
 08:43:59 lte,packet,raw lte1 mbim: 03000000 01000000 20000000 01000000
 08:43:59 lte,packet,raw lte1 mbim: 30000000 0a000000 3c000000 12000000
 08:43:59 lte,packet,raw lte1 mbim: 50000000 00000000 00000000 32003800
 08:43:59 lte,packet,raw lte1 mbim: 34003000 35000000 59006500 74007400
 08:43:59 lte,packet,raw lte1 mbim: 65006c00 20004200 47000000
 08:43:59 lte,debug lte1 mbim: >>> N service: connect, command: register state
 08:43:59 lte,packet lte1 mbim: status data: 
 08:43:59 lte,packet lte1 mbim: 00000000 03000000 01000000 20000000
 08:43:59 lte,packet lte1 mbim: 01000000 30000000 0a000000 3c000000
 08:43:59 lte,packet lte1 mbim: 12000000 50000000 00000000 00000000
 08:43:59 lte,packet lte1 mbim: 32003800 34003000 35000000 59006500
 08:43:59 lte,packet lte1 mbim: 74007400 65006c00 20004200 47000000
 08:43:59 lte,packet,raw lte1 mbim: wdm >>> recv #0
 08:43:59 lte,packet,raw lte1 mbim: 07000080 48000000 00000000 01000000
 08:43:59 lte,packet,raw lte1 mbim: 00000000 a289cc33 bcbb8b4f b6b0133e
 08:43:59 lte,packet,raw lte1 mbim: c2aae6df 0a000000 1c000000 00000000
 08:43:59 lte,packet,raw lte1 mbim: 02000000 20000000 00002003 00000000
 08:43:59 lte,packet,raw lte1 mbim: 00006009 00000000
 08:43:59 lte,debug lte1 mbim: >>> N service: connect, command: packet service
 08:43:59 lte,packet lte1 mbim: status data: 
 08:43:59 lte,packet lte1 mbim: 00000000 02000000 20000000 00002003
 08:43:59 lte,packet lte1 mbim: 00000000 00006009 00000000
 08:43:59 lte,debug lte1 mbim: packet service: attached data class: 0x20 nwe: 
 08:44:00 lte,packet,raw lte1 mbim: wdm >>> recv #0
 08:44:00 lte,packet,raw lte1 mbim: 07000080 40000000 00000000 01000000
 08:44:00 lte,packet,raw lte1 mbim: 00000000 a289cc33 bcbb8b4f b6b0133e
 08:44:00 lte,packet,raw lte1 mbim: c2aae6df 0b000000 14000000 19000000
 08:44:00 lte,packet,raw lte1 mbim: 05000000 05000000 00000000 ffffffff
 09:15:14 interface,info lte1 link down
 09:15:15 lte,info lte1 mbim: error: wdm send failed: 19
 09:15:59 lte,info lte1 IPv4: xxxxxxxx, DNS: xxxxxxxx
 09:15:59 interface,info lte1 link up
 09:16:59 interface,info lte1 link down
 09:16:59 lte,info lte1 mbim: error: wdm send failed: 19
 09:17:41 lte,info lte1 IPv4: xxxxxxxx, DNS: xxxxxxxx
 09:17:41 interface,info lte1 link up
 09:18:57 interface,info lte1 link down
 09:18:57 lte,info lte1 mbim: error: wdm send failed: 19
 09:19:41 lte,info lte1 IPv4: xxxxxxxx, DNS: xxxxxxxx
 09:19:41 interface,info lte1 link up
 09:23:29 interface,info lte1 link down
 09:23:29 lte,info lte1 mbim: error: wdm send failed: 19
 09:24:11 lte,info lte1 IPv4: xxxxxxxx, DNS: xxxxxxxx
 09:24:11 interface,info lte1 link up

Also here is what the signal quality looks like:

         status: connected
             model: FG621-EA
          revision: 16121.1034.00.01.01.03
  current-operator: Yettel BG
    current-cellid: 1128767
            enb-id: 4409
         sector-id: 63
        phy-cellid: 380
        data-class: LTE
    session-uptime: 7m20s
              imei: xxxxx
              imsi: xxxxx
              uicc: xxxxx
      primary-band: B7@20Mhz earfcn: 3350 phy-cellid: 380 
           ca-band: B1@15Mhz earfcn: 75 phy-cellid: 380
              rssi: -48dBm
              rsrp: -78dBm
              rsrq: -14dB

The router os is upgraded to latest stable 7.10.2 and the modem’s firmware is also using the latest version.


Here’s the interface when it’s up:

[admin@MikroTik] > interface/lte/print detail  
Flags: X - disabled; R - running 
 0  R default-name="lte1" name="lte1" mtu=1500 mac-address=2E:1F:07:A4:FF:21 apn-profiles=default allow-roaming=no network-mode=lte band=""

This happens with a simcard that doesn’t have pin setup, when I put in another sim card, from the same provider but with a PIN configured and I have also configured the same pin in the lte interface config it works on the first insert but afterwards when the interface cycles I get a “Sim locked” prompt in webfig and have to manualy disable/reeanble the interface for it to come back. When this happens the signal strength leds are off but also the power led which usually lights up in blue is also off just the wifi signal led is turned on during the issue however the router is not being turned off.



What else can I do to further debug this?

2

If you go into “LTE APNs” from the LTE interface menu, you can check in the “default” profile if “Use Network APN” is checked. If so, try unchecking it, then providing the APN name. Your carrier should know the APN to use, but quick google suggests “telenorbg” (instead of Mikrotik’s default of “internet”).

If Google is to be believed (https://www.apnsettings.org/bulgaria/telenor-globul-bulgaria-apn-settings/)…
you may also need to set a username, which can only be done via command line:

/interface/lte/apn/set [find] authentication=pap user=telenorbg apn=telenorbg
3

So I’ve been testing some more and it seems that if I disable carrier aggregation i.e set only 1 particular band to be allowed (say 1 or 3) then the connection is stable. If I allow more than 1 band (1,3,7) then I will get those spurious disconnects. And for the record - yes the “Use network default APN” is checked, but if the problem was due to the APN wouldn’t internet not run at all?

4

Noted @Amm0

i’m having the same issue, it was working fine for three days.
Now i will need remote hands to checks what is going on

5

It when you sent an APN and have “Use Network APN” that I was kinda thinking might be issue… since it’s kinda subtle that the APN field is NOT used if “Use Network APN”, even if it looks APN set. But if you “Use Network APN” is working and APN is not set…

I still want to say the MBIM error 19 is authentication failure – why I focused on that. But totally agree hours/days later that theory start having more trouble :wink:.

If modem firewall and router at stable RouterOS, you might try a ticket… Mikrotik is pretty good at looking at LTE things – especially when you have the added LTE logging topic & include a supout.rif…

6

I’ve read a few of these posts about the LTE6 “up/down’s”…it does smell like a bug here.

Only other theory is perhaps the latest firmware needs something in the 7.11rc… (e.g. bug was fixed, just not in stable)