hello:
I installed the osmo-NITB on ubuntu18.04, including osmo-trx,osmo-bts,and openbsc.
The following is the print messages when these three applications start up.
*1.osmo-trx*
$ sudo osmo-trx-uhd -C osmo-trx-usrp_b200.cfg Info: SSE3 support compiled in and supported by CPU Info: SSE4.1 support compiled in and supported by CPU Tue May 5 12:36:27 2020 DLGLOBAL <0007> telnet_interface.c:104 Available via telnet 127.0.0.1 4237 Tue May 5 12:36:27 2020 DLCTRL <000e> control_if.c:911 CTRL at 127.0.0.1 4236 Tue May 5 12:36:27 2020 DMAIN <0000> osmo-trx.cpp:484 [tid=139758118945664] Config Settings Log Level............... 0 Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 GSM BTS Address......... 127.0.0.1 Channels................ 1 Tx Samples-per-Symbol... 4 Rx Samples-per-Symbol... 4 EDGE support............ 0 Extended RACH support... 0 Reference............... 1 Filler Burst Type....... Empty bursts Filler Burst TSC........ 0 Filler Burst RACH Delay. 0 Multi-Carrier........... 0 Tuning offset........... 0 RSSI to dBm offset...... 28 Swap channels........... 0 Tx Antennas............. '<default>' Rx Antennas............. '<default>'
Tue May 5 12:36:27 2020 DMAIN <0000> osmo-trx.cpp:438 [tid=139758118945664] Setting SCHED_RR priority 18 Tue May 5 12:36:27 2020 DDEVDRV <0006> log.cpp:460 [tid=139758008424192] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; UHD_3.14.0.HEAD-0-g6875d061 Tue May 5 12:36:27 2020 DDEV <0005> UHDDevice.cpp:470 [tid=139758118945664] Using discovered UHD device type=b200,name=Lab_B210,serial=86680AA,product=B210 Tue May 5 12:36:28 2020 DDEVDRV <0006> b200_impl.cpp:386 [tid=139758008424192] [B200] Detected Device: B210 Tue May 5 12:36:29 2020 DDEVDRV <0006> b200_iface.cpp:441 [tid=139758008424192] [B200] Loading FPGA image: /home/cruise/openBSC/osmo-trx/usrp_b210_fpga.bin... Tue May 5 12:36:45 2020 DDEVDRV <0006> b200_impl.cpp:433 [tid=139758008424192] [B200] Operating over USB 3. Tue May 5 12:36:45 2020 DDEVDRV <0006> b200_impl.cpp:484 [tid=139758008424192] [B200] Detecting internal GPSDO.... Tue May 5 12:36:46 2020 DDEVDRV <0006> gps_ctrl.cpp:253 [tid=139758008424192] [GPS] No GPSDO found Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:587 [tid=139758008424192] [B200] Initialize CODEC control... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:650 [tid=139758008424192] [B200] Initialize Radio control... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:957 [tid=139758008424192] [B200] Performing register loopback test... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:966 [tid=139758008424192] [B200] Register loopback test passed Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:957 [tid=139758008424192] [B200] Performing register loopback test... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:966 [tid=139758008424192] [B200] Register loopback test passed Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:758 [tid=139758008424192] [B200] Setting master clock rate selection to 'automatic'. Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:1013 [tid=139758008424192] [B200] Asking for clock rate 16.000000 MHz... Tue May 5 12:36:46 2020 DDEVDRV <0006> b200_impl.cpp:1024 [tid=139758008424192] [B200] Actually got clock rate 16.000000 MHz. Tue May 5 12:36:47 2020 DMAIN <0000> UHDDevice.cpp:211 [tid=139758118945664] Antennas configured successfully Tue May 5 12:36:47 2020 DDEVDRV <0006> multi_usrp.cpp:502 [tid=139758008424192] [MULTI_USRP] Setting master clock rate selection to 'manual'. Tue May 5 12:36:47 2020 DDEVDRV <0006> b200_impl.cpp:1013 [tid=139758008424192] [B200] Asking for clock rate 26.000000 MHz... Tue May 5 12:36:47 2020 DDEVDRV <0006> b200_impl.cpp:1024 [tid=139758008424192] [B200] Actually got clock rate 26.000000 MHz. Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:275 [tid=139758118945664] Rates configured for B210 4 SPS Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:235 [tid=139758118945664] Supported Tx gain range [0; 89.75] Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:240 [tid=139758118945664] Supported Rx gain range [0; 76] Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:244 [tid=139758118945664] Default setting Tx gain for channel 0 to 44.875 Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:251 [tid=139758118945664] Default setting Rx gain for channel 0 to 38 Tue May 5 12:36:47 2020 DDEV <0005> UHDDevice.cpp:569 [tid=139758118945664] Device configuration: Single USRP: Device: B-Series Device Mboard 0: B210 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: FE-RX2 TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: FE-TX2 Tue May 5 12:36:47 2020 DMAIN <0000> osmo-trx.cpp:532 [tid=139758118945664] -- Transceiver active with 1 channel(s)
*_/when the osmo-bts-trx launched later, the following messages will arise, shows that the osmo-trx received the 'POWEROFF' command and feed back the 'RESPONSE' to osmo-bts-trx./_*
Tue May 5 12:42:44 2020 DTRXCTRL <0002> Transceiver.cpp:832 [tid=139758118945664][chan=0] command is 'POWEROFF' Tue May 5 12:42:44 2020 DTRXCTRL <0002> Transceiver.cpp:977 [tid=139758118945664][chan=0] response is 'RSP POWEROFF 0'
**
*_/POWERON command was not launched. and the USRP TX/RX LED was not lighted./_*
*2.osmo-bts-trx*
$ sudo osmo-bts-trx ((*)) | / \ OsmoBTS <0017> control_if.c:911 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:104 Available via telnet 127.0.0.1 4241 <0012> input/ipaccess.c:1024 enabling ipaccess BTS mode, OML connecting to 192.168.122.1:3002 <000b> trx_if.c:1174 phy0.0: Open transceiver
**
*_/About one minutes later, the osmo-bts-trx will exit automatically, and the following messages was printed./_*
<0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 90 0f 00 c8 <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 88 12 06 00 00 00 00 00 00 <000d> abis.c:143 Signalling link down <0001> bts.c:293 Shutting down BTS 0, Reason Abis close Shutdown timer expired
*3. osmo-nitb*
$ sudo osmo-nitb -c osmo-nitb-ipa.cfg <001e> telnet_interface.c:104 Available via telnet 127.0.0.1 4242 <0020> input/ipaccess.c:985 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports <0025> control_if.c:911 CTRL at 127.0.0.1 4249 DB: Database initialized.
DB: Database prepared.
In a word, the hardware USRP TX/RX LED has not been lighted, it seems not work. How to poweron it?
Hi,
the problem is not in osmo-bts-trx <-> osmo-trx, that's working fine so far on your setup (sending a POWEROFF at startup is fine since then it makes sure the osmo-trx is powered off before configuring it and finally running POWERON on it). It won't be configured until the BSC (in your case osmo-nitb) instructs osmo-bts-trx on how to do it through Abis OML connection.
The problem is here:
On 5/9/20 3:15 AM, cruise wrote:
*_/About one minutes later, the osmo-bts-trx will exit automatically, and the following messages was printed./_*
<0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 90 0f 00 c8 <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 88 12 06 00 00 00 00 00 00 <000d> abis.c:143 Signalling link down <0001> bts.c:293 Shutting down BTS 0, Reason Abis close Shutdown timer expired
The Abis connection, be it OML or RSL, between the BTS and the BSC (in your case osmo-nitb) fails at some point. Unfortunately unless you provide config files, complete logs and pcap files it's difficult to tell you more. Please next time provide those while reporting.
*3. osmo-nitb*
FYI, osmo-ntib is deprecated and not maintained since years ago. Please better use new software stack: https://osmocom.org/projects/cellular-infrastructure/wiki
Thanks for your detailed and generous explanation. I am a beginner on openBSC, looking forward to your guidance.
There are some files in the attachment, i don't know whether they are enough.
1. The config files of osmo-trx, osmo-bts-trx and osmo-nitb. They are the original files downloaded from git repository, and i select one of them to run the application, i don't know whether they are correct, and i don't know how to modify it.
2. config.log files of osmo-trx, osmo-bts-trx and osmo-nitb. I don't know whether they are the logs you mentioned in your reply. I guess not, but i don't know how to get the complete logs, Maybe you give me some tips ?
3. pcap file which includes the data package whose src ip and dst ip are the 127.0.0.1, these packages were captured using wireshark.
I guess there are some problems on the config file osmo-nitb-ipa.cfg , i select it as the config file without reason, because i don't know how to config the file.
thanks for your help again.
在 2020/5/9 下午8:52, Pau Espin Pedrol 写道:
Hi,
the problem is not in osmo-bts-trx <-> osmo-trx, that's working fine so far on your setup (sending a POWEROFF at startup is fine since then it makes sure the osmo-trx is powered off before configuring it and finally running POWERON on it). It won't be configured until the BSC (in your case osmo-nitb) instructs osmo-bts-trx on how to do it through Abis OML connection.
The problem is here:
On 5/9/20 3:15 AM, cruise wrote:
*_/About one minutes later, the osmo-bts-trx will exit automatically, and the following messages was printed./_*
<0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 90 0f 00 c8 <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 88 12 06 00 00 00 00 00 00 <000d> abis.c:143 Signalling link down <0001> bts.c:293 Shutting down BTS 0, Reason Abis close Shutdown timer expired
The Abis connection, be it OML or RSL, between the BTS and the BSC (in your case osmo-nitb) fails at some point. Unfortunately unless you provide config files, complete logs and pcap files it's difficult to tell you more. Please next time provide those while reporting.
*3. osmo-nitb*
FYI, osmo-ntib is deprecated and not maintained since years ago. Please better use new software stack: https://osmocom.org/projects/cellular-infrastructure/wiki
Hi,
you sent compilation logs, which are of no use here.
I recommend you to drop osmo-nitb and switch to the new osmocom stack as I already said on my last email. Furthermore, go through the wiki and read about al lthe components, as well as user manuals in http://ftp.osmocom.org/docs/latest/ to understand better the setup and basic configuration.
which are the useful logs? I didn't find them. How to get them?
在 2020/5/11 下午5:14, Pau Espin Pedrol 写道:
Hi,
you sent compilation logs, which are of no use here.
I recommend you to drop osmo-nitb and switch to the new osmocom stack as I already said on my last email. Furthermore, go through the wiki and read about al lthe components, as well as user manuals in http://ftp.osmocom.org/docs/latest/ to understand better the setup and basic configuration.
You can follow mine at user wiki.
regards, Sandi / DUO
On Mon, May 11, 2020, 16:57 cruise zhankun_bi@163.com wrote:
which are the useful logs? I didn't find them. How to get them?
在 2020/5/11 下午5:14, Pau Espin Pedrol 写道:
Hi,
you sent compilation logs, which are of no use here.
I recommend you to drop osmo-nitb and switch to the new osmocom stack as I already said on my last email. Furthermore, go through the wiki and read about al lthe components, as well as user manuals in http://ftp.osmocom.org/docs/latest/ to understand better the setup and basic configuration.
Hi cruise,
On Mon, May 11, 2020 at 05:56:21PM +0800, cruise wrote:
which are the useful logs? I didn't find them. How to get them?
Maybe this video is useful to you: https://media.ccc.de/v/osmocon17-4008-reporting_and_investigating_issues_in_...
-
cruise -
Harald Welte -
Pau Espin Pedrol -
Sandi Suhendro