And what you see when networks is down?All of the above done.
It's just a one of way to do reboot. Re-power USB is faster. Disable/Enable or set lte parameter is more faster. Change by AT*Cell is more faster.Set watch dog to 10 mintutes with 600 seconds...
Perfect. When you detect the offline state then you can do a diagnostic staff. e.g. check if lte device exist in USB magistral etc. grab logs, do some re-enable stuff.Also use a scheduled script that pings but on fail instead of reboot it just resets the LTE. This takes a lot less time than a reboot. (Bare in mind the time it takes for the device to reboot as well as regain in it's connection.)
Unfortunately I have been really busy. We currently only have 10 LHG 4G Kit Radios in stock.is it happening for only that device or also other 4g kits experience this problem?
Please contact support so we could get support output files and logs from the device.
I will give that a try once it starts crashing reliably. There is a chance that the issue is location dependant, so I want to rule that out first.Have you tried a factory reset and importing a config file?
I had an R11-LTE ROW link up, but not pass traffic, and the reset fixed it in <2 minutes. I think maybe the flash memory is not create in some of these, and something gets corrupted, and resetting seems to fix a lot of problems. I've had to factory reset devices straight out of the box to get them to work, but after that they spend a year in the field with no problems.
Code: Select all
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: sent AT%MEAS="8"
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd Signal Quality: RSRP = -101, RSRQ = -8, SINR = 11, RSSI = -85
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: sent AT%PCONI
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd duplexing mode: TDD
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd Transmission mode: Open loop MIMO
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd Bandwidth: 5
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd EARFCN: 43715
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd Global Cell ID: 006F4101
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd Physical Cell ID: 1
Nov 28 09:30:49 192.168.2.130 lte,async,raw lte1: rcvd HNBN: N/A
Nov 28 09:30:52 192.168.2.130 lte,async,raw lte1: sent AT%MEAS="7"
Nov 28 09:30:52 192.168.2.130 lte,async,raw lte1: rcvd CQI: 8
Code: Select all
Nov 28 09:31:51 192.168.2.130 lte,async lte1: sent AT+COPS=?
Nov 28 09:32:35 192.168.2.130 lte,async,raw +CEREG: 3
Nov 28 09:32:35 192.168.2.130 lte,async lte1: rcvd +COPS: (1,,,"31198",7),(0,,,"302131",7),,(0-4),(0-2)
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: sent AT%MEAS="7"
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd CQI: 8
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: sent AT%MEAS="8"
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd Signal Quality: RSRP = -89, RSRQ = -6, SINR = 24, RSSI = -75
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: sent AT%PCONI
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd duplexing mode: TDD
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd Transmission mode: Open loop MIMO
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd Bandwidth: 2
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd EARFCN: 44360
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd Global Cell ID: 040B8F06
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd Physical Cell ID: 52
Nov 28 09:32:35 192.168.2.130 lte,async,raw lte1: rcvd HNBN: N/A
Code: Select all
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: sent AT%MEAS="8"
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd Signal Quality: RSRP = -91, RSRQ = -7, SINR = 25, RSSI = -73
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: sent AT%PCONI
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd duplexing mode: TDD
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd Transmission mode: Open loop MIMO
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd Bandwidth: 2
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd EARFCN: 44360
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd Global Cell ID: 040B8F06
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd Physical Cell ID: 52
Nov 28 09:36:30 192.168.2.130 lte,async,raw lte1: rcvd HNBN: \0x18d\0xae*
Thanks for that.Forgot to mention, thanks for the write up SiB, very useful! I was unaware of the passthrough mode.
Please check this value at https://www.cellmapper.net/arfcn?net=LT ... 3715&MCC=0rcvd EARFCN: 43715
width of band is 5Mhz means from 3612.5 to 3617.5rcvd Bandwidth: 5
006F4101 hex = 7291137 decimal by https://www.rapidtables.com/convert/num ... cimal.htmlrcvd Global Cell ID: 006F4101
This is truly a physical antenna ID at tower and this number can be see at many ISP who share the same physical antenna.rcvd Physical Cell ID: 1
[admin@MikroTik] > interface lte cell-monitor lte1
PHY-CELLID BAND EARFCN RSRP RSRQ RSSI
11 B3 1300 -107dBm -175dB
306 B1 150 -115dBm -195dB
373 B3 1300 -111dBm -195dB
374 B3 1300 -111dBm -195dB
384 B1 150 -106dBm -120dB
384 B7 2850 -115dBm -175dB
384 B20 6300 -97dBm -195dB
I haven't idearcvd HNBN: N/A
HNBN: \397\174* -> by converting hex>decrcvd HNBN: \0x18d\0xae*
You should try scan your area towers and try connection to particular antenna, maybe you discover that your ISP at some tower give you internet every time and on some not every time, maybe.It seems to me like the MikroTik and the LTE card are not on the same page, or when a registration failure happens it just gives up all hope.
Code: Select all
[admin@LTE Test Radio] > interface lte cell-monitor 0 duration=10s
failure: cell-monitor not supported!
[admin@LTE Test Radio] /interface lte> scan 0
Flags: C - current, A - available, F - forbidden
OPERATOR MCC-MNC ACCESS-TECHNOLOGY RSSI RSRP RSRQ
-- [Q quit|D dump|C-z pause]
Log File During Scan:
Nov 29 09:34:22 192.168.2.130 lte,async lte1: sent AT+COPS=?
Nov 29 09:34:22 192.168.2.130 lte,async lte1: rcvd +CME ERROR: PLMN busy
Nov 29 09:34:23 192.168.2.130 lte,async lte1: sent AT+COPS=?
Nov 29 09:34:23 192.168.2.130 lte,async lte1: rcvd +CME ERROR: PLMN busy
Nov 29 09:34:24 192.168.2.130 lte,async lte1: sent AT+COPS=?
Nov 29 09:34:24 192.168.2.130 lte,async lte1: rcvd +CME ERROR: PLMN busy
/interface lte info lte1 once do={
:log info "RSRP:= $"rsrp" RSRQ:= $"rsrq" SINR:= $"sinr""}
:local i 0; {:do {:set i ($i + 1)} while (($i < 2) && ([/ping 8.8.8.8 interval=1 count=1]=0))};
:if ($i=2) do={:log warning "LTE Lost";
/interface lte at-chat lte1 input="AT+reset";
:log info "Script Reset LTE1"}
EARFCN actually defines centre frequency of LTE carrier. So in example above (EARFCN 43715 and 5MHz bandwidth the used frequency band is between 3610 MHz and 3615 MHz.Please check this value at https://www.cellmapper.net/arfcn?net=LT ... 3715&MCC=0rcvd EARFCN: 43715
decoding this "43715" = TDD Band 43 and 3612.5 MHz is a start freq of your ISP
width of band is 5Mhz means from 3612.5 to 3617.5rcvd Bandwidth: 5
Both fields (eNbID and CID) are fully operator configurable and there are no constraints other than that eNbID must be unique inside MNO and that CID is unique within single eNodeB. Meaning that CID can be whatever and doesn't have to start from 0 (however that seems to be customary).006F4101 hex = 7291137 decimal by https://www.rapidtables.com/convert/num ... cimal.htmlrcvd Global Cell ID: 006F4101
This 7291137(d) give information about YOUR Tower Antenna to what you are connecting. It's your target in LTE.
In LTE we have got formula that:
eNBID * 256 + CLID = E-CID = 7291137 decimal
a) Number eNBID is a identificator of ISP at tower. Multiple it by 256.
28481 * 256 + 1 = 7291137 (check this https://www.cellmapper.net/enbid?net=LTE&cellid=7291137 )
b) CLID it's a number of antena and counting start from 0 by step +1. 0 it's a first antena of your ISP and he can have few of them on different Band's, 3 x sectors of one Band and 4x sectors of other Band .
c) Final Cell ID = e-CID is your ISP ID *256 = 7291136 + CLID=0 for first sector antenna
This is truly a physical antenna ID at tower and this number can be see at many ISP who share the same physical antenna.rcvd Physical Cell ID: 1
@ksthree: "reads LTE Unregistred State 0 or LTE Unregistred State 11"The "R" indicator does disappear while it is stuck in the Registration Denied State
But this is response when the modem have not a FULL Functionality.interface lte cell-monitor 0 duration=10s
failure: cell-monitor not supported!
WOW, Then you know more then me. You can reach a log's from opposite devices "LTE basestation" ?1) We are our own operator
I just read all book's at MikroTik, do certification from MikroTik, read a wiki when I configure stg. new and before I helps few persons with scripting to LTE devices and I buy SXTR with R11e-LTE6 to check this device. My primary WAN's are two E3372 with custom firmware connected by USB HUB and I use both ISP at the same time. SXTR have a good antenna and works 4days for now.I also wasn't aware it was possible to lock frequency on the Mikrotik's. It would be nice if this was a sub menu on the LTE interface. I am going to lock it down and see if it helps
I understand that in problem situation, the LTE logs are not give you any logs with "crashing modem" etc. and you see the new log LTE entry when you do scan/cell-monitor ?2) Here is where it gets really strange. At this time, it isn't possible to scan with both cell-monitor and scan
https://wiki.mikrotik.com/wiki/Manual:I ... _Cell_lockAnd it looks like I can't lock it down even if I wanted to
how did you fix this issue?Hello Everyone
We have purchased a few Mikrotik LHG 4G Kit units for use with a 3.5Ghz Baicell basestation. The 4G Kit (With the R11e-4G card) supports Band 43 which is what we are using, and they seem to work great most of the time, however we are finding that the LTE has issues with locking up and winbox sessions continually disconnect (Without lossing LTE connectivity).
We are currently running 6.45.6 (Just updated to 6.45.7 for security patches) with the LTE firmware being R11e-4G_V007
Signal levels are RSSI: -72, RSRP:-86, RSRQ:-5, SINR: 28, CQI: 15.
This issue is on both 10Mhz and 5Mhz channel widths.
From what I know, the few Baicell clients we have on the sector do not have these issues and stay connected 24/7 with lower signal levels.
It seems the LTE locks up requiring a full reboot to get it functional again. We have mitigated it a bit by enabling the watchdog, however it's still rebooting every 5-6 hours and causing service disruptions.
Because of the watchdog I haven't been able to get any detailed logs from it. I am going to be setting up a test unit at the office with remote syslog running with LTE INFO enabled to see if I can get more data.
I am just wondering if there are some tweaks or something I am missing? I have seen quite a few form posts with similar issues, however they mostly seem to be resolved with patches from older versions.