9 Apr
2020
9 Apr
'20
12:15 p.m.
Hi,
I looked at the forum for answers before posting, but I
unfortunately couldn't get answers to what I was looking for. I looked into
particular
https://www.mail-archive.com/openbsc@lists.osmocom.org/msg09819.html for
solving my issue.
Setup: USRP B210 as radio head. NITB modules as components for 2G Network
and BTS-TRX and TRX-UHD modules.
Issue:
- TRX-UHD and BTS-TRX fail. NITB Module works. Components of NITB
network are able to connect to each other.
- I have the RSP POWEROFF message originating in log from TRX-UHD module
and the BTS module is shuttiing down.
- BTS connects via OML but fails to connect RSL.
- As per the previous email archive, I wanted to login to VTY and check
the logs, but, it logs out as the BTS module shuts down (I cannot connect
and see what's happening).
I looked through the configuration files and seem correct to me.
Any suggestions would be appreciated on solving the issue. I am trying to
create a test 2G OSMOCOM network. Logs are written below and configuration
as attachments.
Thanks for your help!
*OSMO_BTS_TRX log:*
systemd[1]: Started Osmocom osmo-bts for osmo-trx.
osmo-bts-trx[23221]: <0017> control_if.c:911 CTRL at 127.0.0.1 4238
osmo-bts-trx[23221]: <0010> telnet_interface.c:104 Available via telnet
127.0.0.1 4241
osmo-bts-trx[23221]: <0012> input/ipaccess.c:1024 enabling ipaccess BTS
mode, OML connecting to 192.168.0.9:3002
osmo-bts-trx[23221]: <000b> trx_if.c:1174 phy0.0: Open transceiver
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: <000d> abis.c:142 Signalling link down
osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason Abis close
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory response
from transceiver(CMD POWEROFF)
osmo-bts-trx[23221]: Shutdown timer expired
osmo-bts-trx[23221]: ((*))
osmo-bts-trx[23221]: |
osmo-bts-trx[23221]: / \ OsmoBTS
*OSMO_TRX_UHD log:*
ubuntu-HP-EliteBook-8470p systemd[1]: Started Osmocom SDR BTS L1
Transceiver (UHD Backend).
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21
2020 DLGLOBAL <0007> telnet_interface.c:104 Available via telnet
127.0.0.1 4237
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21
2020 DLCTRL <000e> control_if.c:911 CTRL at 127.0.0.1 4236
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21
2020 DMAIN <0000> osmo-trx.cpp:485 [tid=140554411180864] Config
Settings
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Log Level............... 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Device args.............
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TRX Base Port........... 5700
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TRX
Address............. 127.0.0.1
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: GSM BTS
Address......... 127.0.0.1
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Channels................ 1
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Tx Samples-per-Symbol... 4
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Rx Samples-per-Symbol... 4
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: EDGE support............ 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Extended RACH support... 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Reference............... 1
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Filler Burst
Type....... Empty bursts
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Filler Burst TSC........ 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Filler Burst RACH Delay. 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Multi-Carrier........... 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Tuning offset........... 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RSSI to dBm offset...... 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Swap channels........... 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Tx
Antennas............. '<default>'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Rx
Antennas............. '<default>'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21
2020 DMAIN <0000> osmo-trx.cpp:439 [tid=140554411180864] Setting
SCHED_RR priority 18
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: [INFO] [UHD] linux; GNU
C++ version 7.4.0; Boost_106501; UHD_3.14.1.1-release
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:21
2020 DDEV <0005> UHDDevice.cpp:470 [tid=140554411180864] Using
discovered UHD device
type=b200,name=MyB210,serial=31A92EA,product=B210
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:22 2020
DDEVDRV <0006> b200_impl.cpp:386 [tid=140554300024576] [B200] Detected
Device: B210
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:22 2020
DDEVDRV <0006> b200_impl.cpp:433 [tid=140554300024576] [B200]
Operating over USB 2.
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:22 2020
DDEVDRV <0006> b200_impl.cpp:587 [tid=140554300024576] [B200]
Initialize CODEC control...
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:650
[tid=140554300024576] [B200] Initialize Radio control...
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:957
[tid=140554300024576] [B200] Performing register loopback test...
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:966
[tid=140554300024576] [B200] Register loopback test passed
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:957
[tid=140554300024576] [B200] Performing register loopback test...
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:966
[tid=140554300024576] [B200] Register loopback test passed
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:758
[tid=140554300024576] [B200] Setting master clock rate selection to
'automatic'.
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:1013
[tid=140554300024576] [B200] Asking for clock rate 16.000000 MHz...
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:1024
[tid=140554300024576] [B200] Actually got clock rate 16.000000 MHz.
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DMAIN <0000> UHDDevice.cpp:214
[tid=140554411180864] Antennas configured successfully
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> multi_usrp.cpp:502
[tid=140554300024576] [MULTI_USRP] Setting master clock rate selection
to 'manual'.
huhti 09 11:22:23 ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:23 2020 DDEVDRV <0006> b200_impl.cpp:1013
[tid=140554300024576] [B200] Asking for clock rate 26.000000 MHz...
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEVDRV <0006> b200_impl.cpp:1024 [tid=140554300024576] [B200]
Actually got clock rate 26.000000 MHz.
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEV <0005> UHDDevice.cpp:275 [tid=140554411180864] Rates configured
for B210 4 SPS
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEV <0005> UHDDevice.cpp:235 [tid=140554411180864] Supported Tx gain
range [0; 89.75]
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEV <0005> UHDDevice.cpp:240 [tid=140554411180864] Supported Rx gain
range [0; 76]
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEV <0005> UHDDevice.cpp:244 [tid=140554411180864] Default setting Tx
gain for channel 0 to 44.875
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEV <0005> UHDDevice.cpp:251 [tid=140554411180864] Default setting Rx
gain for channel 0 to 38
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DDEV <0005> UHDDevice.cpp:569 [tid=140554411180864] Device
configuration: Single USRP:
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Device: B-Series Device
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Mboard 0: B210
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX Channel: 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX DSP: 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX Dboard: A
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: RX Subdev: FE-RX2
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX Channel: 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX DSP: 0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX Dboard: A
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: TX Subdev: FE-TX2
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DMAIN <0000> Threads.cpp:119 [tid=140554180474624] Thread
140554180474624 (task 8317) set name: CtrlService0
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DMAIN <0000> osmo-trx.cpp:533 [tid=140554411180864] -- Transceiver
active with 1 channel(s)
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:28 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:28 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:33 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:33 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:38 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:38 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:43 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:43 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:49 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:49 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:54 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:54 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:59 2020
DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:59 2020
DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
9 Apr
9 Apr
12:52 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hello Aalto,
your configuration looks good to me. As far as I understand, you're
running both osmo-bts-trx and osmo-trx on the same machine. As can be
seen from your logs, TRXC commands from osmo-bts-trx are received by
osmo-trx:
<0002> Transceiver.cpp:778
[tid=140554180474624][chan=0] command is 'POWEROFF'
however the response messages from osmo-trx do not reach osmo-bts-trx:
<0002> Transceiver.cpp:923
[tid=140554180474624][chan=0] response is 'RSP POWEROFF 0'
<000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD POWEROFF)
Maybe your firewall is blocking traffic (udp/5701 and udp/5801)
somehow? Could you please send us a *.pcap capture ('lo' interface)?
With best regards,
Vadim Yanitskiy.
2:09 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi Vadim,
Thank you for your quick replies. (Previously, due to error, I sent reply
to you. Now, I have resent with openbsc in cc)
I wasn't sure, if my firewall is blocking the port or not. Hence, I took a
wire shark trace test.pcap. I ran sudo ufw allow 5701 and sudo ufw allow
5801 and then again took wire shark trace test2.pcap. Both traces are
attached. From my inspection, the ports have still the same messages.
I am also attaching the configuration of other components, as a reference.
Thanks again for the help
On Thu, 9 Apr 2020 at 13:52, Vadim Yanitskiy <axilirator(a)gmail.com> wrote:
Hello Aalto,
your configuration looks good to me. As far as I understand, you're
running both osmo-bts-trx and osmo-trx on the same machine. As can be
seen from your logs, TRXC commands from osmo-bts-trx are received by
osmo-trx:
<0002> Transceiver.cpp:778
[tid=140554180474624][chan=0] command is
'POWEROFF'
however the response messages from osmo-trx do not reach osmo-bts-trx:
<0002> Transceiver.cpp:923
[tid=140554180474624][chan=0] response is
'RSP POWEROFF 0'
<000b> trx_if.c:185 phy0.0: No satisfactory
response from
transceiver(CMD POWEROFF)
Maybe your firewall is blocking traffic (udp/5701 and udp/5801)
somehow? Could you please send us a *.pcap capture ('lo' interface)?
With best regards,
Vadim Yanitskiy.
2:38 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi again,
Hence, I took a wire shark trace test.pcap.
I see ICMP Destination Unreachable messages in your captures:
3 0.010926 127.0.0.1 → 127.0.0.1 OsmoTRXC
55 CMD POWEROFF
4 0.010938 127.0.0.1 → 127.0.0.1 ICMP 83 Destination unreachable (Port
unreachable)
145 2.011000 127.0.0.1 → 127.0.0.1 OsmoTRXC 55 CMD POWEROFF
146 2.011016 127.0.0.1 → 127.0.0.1 ICMP 83 Destination unreachable (Port
unreachable)
185 4.011062 127.0.0.1 → 127.0.0.1 OsmoTRXC 55 CMD POWEROFF
186 4.011144 127.0.0.1 → 127.0.0.1 OsmoTRXC 57 RSP POWEROFF 0
239 18.099625 127.0.0.1 → 127.0.0.1 OsmoTRXC 55 CMD POWEROFF
240 18.099703 127.0.0.1 → 127.0.0.1 OsmoTRXC 57 RSP POWEROFF 0
269 35.349196 127.0.0.1 → 127.0.0.1 OsmoTRXC 55 CMD POWEROFF
270 35.349271 127.0.0.1 → 127.0.0.1 OsmoTRXC 57 RSP POWEROFF 0
Perhaps you're starting osmo-bts-trx before osmo-trx? Make sure to
start osmo-trx first and give it enough time to upload the UHD
firmware, unless you see "Transceiver active with X channel(s)".
With best regards,
Vadim Yanitskiy.
2:39 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi,
I have the feeling the connection between osmo-trx and osmo-bts-trx is
good. The problem is that your BTS<->BSC<->... is failing.
BTs shows these messages at startup because osmo-trx is not yet running:
""""
osmo-bts-trx[23221]: <000b> trx_if.c:1174
phy0.0: Open transceiver
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory
response from transceiver(CMD POWEROFF)
"""
Then at some point osmo-trx answers:
"""
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr
9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:778
[tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr
9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:923
[tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
"""
But it's already too late, the BTS is already exiting due to some issue
in Abis:
"""
osmo-bts-trx[23221]: <000d> abis.c:142
Signalling link down
osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason
Abis
close
"""
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
2:53 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi Aalto, Pau,
The problem is that your BTS<->BSC<->...
is failing.
I don't see any related packets in the captures, neither RSL nor OML...
However, I see an obvious issue - IPA unit-id mismatch:
# This is the unit id that has to match the BTS
configuration
ip.access unit_id 1800 0
vs
ipa unit-id 6969 0
Are you using some configuration examples? If so, where are they from?
Also, are you sure that osmo-bsc is actually running on 192.168.122.1?
With best regards,
Vadim Yanitskiy.
14 Apr
14 Apr
3:27 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi Vadim and Pau,
Thank you for the quick replies.
*Pau:* Probably your guess is correct. I am looking into it in detail at
the moment the core network configurations.
*Vadim*: I started osmo-trx first and waited until the message "Transceiver
active with 1 channel(s)", before running osmo-bts-trx and other modules.
I will look into the wireshark capture to ensure that there are RSL and OML
packets. Yes. I am using the configuration examples from
*https://osmocom.org/attachments/3473/nitb.tar
<https://osmocom.org/attachments/3473/nitb.tar>.* I am not sure, how to
test osmo-bsc is actually running on 192.168.122.1 (I guess, I have to ping
to ensure). Meanwhile, is there a basic configuration where I can run the
system? Can I find it somewhere(I tried to run /usr/local/etc/osmocom
config files and it didn't work. Probably, I have to fine tune the
configurations)? And, is there a wireshark trace by any chance for
reference?
On Thu, 9 Apr 2020 at 15:39, Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
Hi,
I have the feeling the connection between osmo-trx and osmo-bts-trx is
good. The problem is that your BTS<->BSC<->... is failing.
BTs shows these messages at startup because osmo-trx is not yet running:
""""
osmo-bts-trx[23221]: <000b> trx_if.c:1174
phy0.0: Open transceiver
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory
response from transceiver(CMD POWEROFF)
"""
Then at some point osmo-trx answers:
"""
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:778
[tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:923
[tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
"""
But it's already too late, the BTS is already exiting due to some issue
in Abis:
"""
osmo-bts-trx[23221]: <000d> abis.c:142
Signalling link down
osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason
Abis
close
"""
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
15 Apr
15 Apr
5:38 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi,
I figured out that the issue is in connectivity between BSC and BTS. I am
able to fix half of the issue. I would appreciate any further guidance.
*Firstly, I ran only BTS module*. In the BTS log, I see an OML connection
established. Transcribed are the logs.
<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
127.0.0.1:3002
<000b> trx_if.c:1174 phy0.0: Open transceiver
*<0012> input/ipa.c:128 127.0.0.1:3002 <http://127.0.0.1:3002> connection
done*<0012> input/ipaccess.c:846 received ID_GET for unit ID 1800/0/0
<000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD
POWEROFF)
It again fails to get any response.
*Next, I ran the combination of TRX-UHD module and BTS module. *I failed to
get even OML connection.
<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
127.0.0.1:3002
<000b> trx_if.c:1174 phy0.0: Open transceiver
<000d> abis.c:142 Signalling link down
<0001> bts.c:292 Shutting down BTS 0, Reason Abis close
Shutdown timer expired
I could see only this in trace.
[image: a.png]
Thanks for the help.
On Tue, 14 Apr 2020 at 16:27, Aalto Koskinen <aaltokoskinen(a)gmail.com>
wrote:
Hi Vadim and Pau,
Thank you for the quick replies.
*Pau:* Probably your guess is correct. I am looking into it in detail at
the moment the core network configurations.
*Vadim*: I started osmo-trx first and waited until the message
"Transceiver active with 1 channel(s)", before running osmo-bts-trx and
other modules.
I will look into the wireshark capture to ensure that there are RSL and
OML packets. Yes. I am using the configuration examples from
*https://osmocom.org/attachments/3473/nitb.tar
<https://osmocom.org/attachments/3473/nitb.tar>.* I am not sure, how to
test osmo-bsc is actually running on 192.168.122.1 (I guess, I have to ping
to ensure). Meanwhile, is there a basic configuration where I can run the
system? Can I find it somewhere(I tried to run /usr/local/etc/osmocom
config files and it didn't work. Probably, I have to fine tune the
configurations)? And, is there a wireshark trace by any chance for
reference?
On Thu, 9 Apr 2020 at 15:39, Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
Hi,
I have the feeling the connection between osmo-trx and osmo-bts-trx is
good. The problem is that your BTS<->BSC<->... is failing.
BTs shows these messages at startup because osmo-trx is not yet running:
""""
osmo-bts-trx[23221]: <000b> trx_if.c:1174
phy0.0: Open transceiver
osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory
response from transceiver(CMD POWEROFF)
"""
Then at some point osmo-trx answers:
"""
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:778
[tid=140554180474624][chan=0]
command is 'POWEROFF'
ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu
Apr 9 11:22:24
2020 DTRXCTRL <0002> Transceiver.cpp:923
[tid=140554180474624][chan=0]
response is 'RSP POWEROFF 0'
"""
But it's already too late, the BTS is already exiting due to some issue
in Abis:
"""
osmo-bts-trx[23221]: <000d> abis.c:142
Signalling link down
osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason
Abis
close
"""
Regards,
Pau
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
21 Apr
21 Apr
9:35 p.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi,
Sorry to bother you all again. I am stuck with this since a week trying to
figure out, but failing so. I am able to see OML in wireshark
traces(attached as a picture), but still not able to see RSL protocol.
I need to be able to connect bts-trx and bsc modules to get a working
connection. Any suggestions would be appreciated.
Thanks for the help.
On Wed, 15 Apr 2020 at 18:38, Aalto Koskinen <aaltokoskinen(a)gmail.com>
wrote:
Hi,
I figured out that the issue is in connectivity between BSC and BTS. I am
able to fix half of the issue. I would appreciate any further guidance.
*Firstly, I ran only BTS module*. In the BTS log, I see an OML connection
established. Transcribed are the logs.
<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
127.0.0.1:3002
<000b> trx_if.c:1174 phy0.0: Open transceiver
*<0012> input/ipa.c:128 127.0.0.1:3002 <http://127.0.0.1:3002> connection
done*<0012> input/ipaccess.c:846 received ID_GET for unit ID 1800/0/0
<000b> trx_if.c:185 phy0.0: No satisfactory response from transceiver(CMD
POWEROFF)
It again fails to get any response.
*Next, I ran the combination of TRX-UHD module and BTS module. *I failed
to get even OML connection.
<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
127.0.0.1:3002
<000b> trx_if.c:1174 phy0.0: Open transceiver
<000d> abis.c:142 Signalling link down
<0001> bts.c:292 Shutting down BTS 0, Reason Abis close
Shutdown timer expired
I could see only this in trace.
[image: a.png]
Thanks for the help.
On Tue, 14 Apr 2020 at 16:27, Aalto Koskinen <aaltokoskinen(a)gmail.com>
wrote:
> Hi Vadim and Pau,
>
> Thank you for the quick replies.
>
> *Pau:* Probably your guess is correct. I am looking into it in detail at
> the moment the core network configurations.
> *Vadim*: I started osmo-trx first and waited until the message
> "Transceiver active with 1 channel(s)", before running osmo-bts-trx and
> other modules.
> I will look into the wireshark capture to ensure that there are RSL and
> OML packets. Yes. I am using the configuration examples from
*https://osmocom.org/attachments/3473/nitb.tar
> <https://osmocom.org/attachments/3473/nitb.tar>.* I am not sure, how to
> test osmo-bsc is actually running on 192.168.122.1 (I guess, I have to ping
> to ensure). Meanwhile, is there a basic configuration where I can run the
> system? Can I find it somewhere(I tried to run /usr/local/etc/osmocom
> config files and it didn't work. Probably, I have to fine tune the
> configurations)? And, is there a wireshark trace by any chance for
> reference?
>
> On Thu, 9 Apr 2020 at 15:39, Pau Espin Pedrol <pespin(a)sysmocom.de> wrote:
>
>> Hi,
>>
>> I have the feeling the connection between osmo-trx and osmo-bts-trx is
>> good. The problem is that your BTS<->BSC<->... is failing.
>>
>> BTs shows these messages at startup because osmo-trx is not yet running:
>> """"
>> > osmo-bts-trx[23221]: <000b> trx_if.c:1174 phy0.0: Open transceiver
>> > osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory
>> > response from transceiver(CMD POWEROFF)
>> """
>>
>> Then at some point osmo-trx answers:
>> """
>> > ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24
>> 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0]
>> command is 'POWEROFF'
>> > ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24
>> 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0]
>> response is 'RSP POWEROFF 0'
>> """
>>
>> But it's already too late, the BTS is already exiting due to some issue
>> in Abis:
>> """
>> > osmo-bts-trx[23221]: <000d> abis.c:142 Signalling link down
>> > osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason
>> Abis close
>> """
>>
>> Regards,
>> Pau
>>
>> --
>> - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
>> =======================================================================
>> * sysmocom - systems for mobile communications GmbH
>> * Alt-Moabit 93
>> * 10559 Berlin, Germany
>> * Sitz / Registered office: Berlin, HRB 134158 B
>> * Geschaeftsfuehrer / Managing Director: Harald Welte
>>
>
22 Apr
22 Apr
11:14 a.m.
New subject: OSMOCOM TRX_BTS_BSC Connection Issue
Hi,
your png image clearly shows that you have some problem with AoIP side
(SCTP connections failing). Are you running osmo-stp and osmo-msc?
It's useless trying to help you better if you don't provide at least
config files and a pcap with all the generated traffic while start and
running your network.
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
1473
days inactive
1486
days old
9 comments
3 participants
participants (3)
-
Aalto Koskinen -
Pau Espin Pedrol -
Vadim Yanitskiy