Project

General

Profile

Actions
Copy link

Bug #6270

open

osmo-bts sends version report every 5s to BSC?

Added by laforge 5 months ago. Updated 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
dexter
Category:
osmo-bts-trx
Target version:
-
Start date:
11/22/2023
Due date:
% Done:

30%

Spec Reference:

Description

on a Debian 12 system using osmocom-nightly 202311212026 (osmo-trx-uhd + osmo-bts-trx), I'm seeing osmo-bts sending a PCU version report every 5 seconds:

Nov 22 15:57:37 nuc-osmocom2 osmo-bts-trx[7356]: <0001> oml.c:93 OC=GPRS-CELL INST=(00,00,ff): Sending PCU version report to BSC: 1.3.1.9-26dc.202311212026
Nov 22 15:57:37 nuc-osmocom2 osmo-bsc[648]: <0004> abis_nm.c:352 OC=BTS(01) INST=(00,ff,ff): Reported connected PCU version 1.3.1.9-26dc.202311212026
Nov 22 15:57:38 nuc-osmocom2 osmo-bts-trx[7356]: <000b> trx_if.c:138 phy0.0: Clock indication: fn=1123815
Nov 22 15:57:38 nuc-osmocom2 osmo-bts-trx[7356]: <0000> rsl.c:496 Tx RSL RF RESource INDication
Nov 22 15:57:39 nuc-osmocom2 osmo-bts-trx[7356]: <000b> trx_if.c:138 phy0.0: Clock indication: fn=1124031
Nov 22 15:57:40 nuc-osmocom2 osmo-bts-trx[7356]: <000b> trx_if.c:138 phy0.0: Clock indication: fn=1124248
Nov 22 15:57:41 nuc-osmocom2 osmo-bts-trx[7356]: <0000> rsl.c:496 Tx RSL RF RESource INDication
Nov 22 15:57:41 nuc-osmocom2 osmo-bts-trx[7356]: <000b> trx_if.c:138 phy0.0: Clock indication: fn=1124464
Nov 22 15:57:42 nuc-osmocom2 osmo-bts-trx[7356]: <000b> trx_if.c:138 phy0.0: Clock indication: fn=1124681
Nov 22 15:57:42 nuc-osmocom2 osmo-bts-trx[7356]: <0001> oml.c:93 OC=GPRS-CELL INST=(00,00,ff): Sending PCU version report to BSC: 1.3.1.9-26dc.202311212026
Nov 22 15:57:42 nuc-osmocom2 osmo-bsc[648]: <0004> abis_nm.c:352 OC=BTS(01) INST=(00,ff,ff): Reported connected PCU version 1.3.1.9-26dc.202311212026

osmo-pcu is not respawning. There are no PDCH configured for this BTS, and "gprs mode none" is in the osmo-bsc.cfg

I'm wondering why we keep sending those version reports every 5 seconds to the BSC. They are not needed at all and just spam the logs.

root@jma-osmocom2:/etc/osmocom# dpkg -l | grep osmo
ii  libosmo-gsup-client0:amd64              1.7.0.5.e513.202311212026      amd64        Osmocom GSUP (General Subscriber Update Protocol) client library
ii  libosmo-mgcp-client12:amd64             1.12.1.3.8b663.202311212026    amd64        libosmo-mgcp-client: Osmocom's Media Gateway Control Protocol client utilities
ii  libosmo-mslookup1:amd64                 1.7.0.5.e513.202311212026      amd64        Osmocom MS lookup library
ii  libosmo-ranap7:amd64                    1.5.0.1.5484.202311212026      amd64        Osmocom code for the Iuh interface (HNBAP, RUA, RANAP)
ii  libosmo-sigtran9:amd64                  1.8.0.22.42ed.202311212026     amd64        Osmocom SIGTRAN library (SCCP, SUA, M3UA and more)
ii  libosmoabis13:amd64                     1.5.0.2.247e.202311212026      amd64        GSM A-bis handling
ii  libosmocodec4:amd64                     1.9.0.48.459c.202311212026     amd64        Osmo codec library
ii  libosmocoding0:amd64                    1.9.0.48.459c.202311212026     amd64        Osmo coding library
ii  libosmocore                             1.9.0.48.459c.202311212026     amd64        Open Source MObile COMmunications CORE library (metapackage)
ii  libosmocore21:amd64                     1.9.0.48.459c.202311212026     amd64        Osmo Core library
ii  libosmoctrl0:amd64                      1.9.0.48.459c.202311212026     amd64        Osmo control library
ii  libosmogb14:amd64                       1.9.0.48.459c.202311212026     amd64        Osmo GPRS GB library
ii  libosmogsm20:amd64                      1.9.0.48.459c.202311212026     amd64        Osmo GSM utility library
ii  libosmoisdn0:amd64                      1.9.0.48.459c.202311212026     amd64        Osmo ISDN utility library
ii  libosmonetif11:amd64                    1.4.0.11.1a5f.202311212026     amd64        Common/shared code regarding network interface for OpenBSC
ii  libosmosim2:amd64                       1.9.0.48.459c.202311212026     amd64        Osmo SIM library
ii  libosmotrau2:amd64                      1.5.0.2.247e.202311212026      amd64        GSM trau handling
ii  libosmousb0:amd64                       1.9.0.48.459c.202311212026     amd64        Osmo USB library
ii  libosmovty13:amd64                      1.9.0.48.459c.202311212026     amd64        Osmo VTY library
ii  osmo-bsc                                1.11.0.36.647bc.202311212026   amd64        OsmoBSC: Osmocom's Base Station Controller for 2G circuit-switched mobile networks
ii  osmo-bsc-doc                            1.11.0.36.647bc.202311212026   all          PDF documentation
ii  osmo-bsc-ipaccess-utils                 1.11.0.36.647bc.202311212026   amd64        Command line utilities for ip.access nanoBTS
ii  osmo-bts-doc                            1.7.0.39.4a6a.202311212026     all          PDF documentation
ii  osmo-bts-trx                            1.7.0.39.4a6a.202311212026     amd64        osmo-bts-trx GSM BTS with osmo-trx
ii  osmo-ggsn                               1.10.2.202311212026            amd64        Osmocom Gateway GPRS Support Node (GGSN)
ii  osmo-ggsn-doc                           1.10.2.202311212026            all          PDF documentation
ii  osmo-hlr                                1.7.0.5.e513.202311212026      amd64        Osmocom Home Location Register
ii  osmo-hlr-doc                            1.7.0.5.e513.202311212026      all          PDF documentation
ii  osmo-mgw                                1.12.1.3.8b663.202311212026    amd64        OsmoMGW: Osmocom's Media Gateway for 2G and 3G circuit-switched mobile networks
ii  osmo-mgw-doc                            1.12.1.3.8b663.202311212026    all          PDF documentation
ii  osmo-msc                                1.11.1.5.1759.202311212026     amd64        OsmoMSC: Osmocom's Mobile Switching Center for 2G and 3G circuit-switched mobile networks
ii  osmo-msc-doc                            1.11.1.5.1759.202311212026     all          PDF documentation
ii  osmo-pcu                                1.3.1.9.26dc.202311212026      amd64        Osmocom GPRS/EDGE Packet Control Unit (PCU)
ii  osmo-pcu-doc                            1.3.1.9.26dc.202311212026      all          PDF documentation
ii  osmo-sgsn                               1.11.0.1.e746b.202311212026    amd64        OsmoSGSN: Osmocom's Serving GPRS Support Node for 2G and 3G packet-switched mobile networks
ii  osmo-sgsn-doc                           1.11.0.1.e746b.202311212026    all          PDF documentation
ii  osmo-stp:amd64                          1.8.0.22.42ed.202311212026     amd64        Osmocom SIGTRAN STP (Signaling Transfer Point)
ii  osmo-stp-doc                            1.8.0.22.42ed.202311212026     all          PDF documentation
ii  osmo-trx                                1.6.0.5.242c.202311212026      all          Metapackage for osmo-trx-uhd
ii  osmo-trx-doc                            1.6.0.5.242c.202311212026      all          PDF documentation
ii  osmo-trx-lms                            1.6.0.5.242c.202311212026      amd64        SDR transceiver that implements Layer 1 of a GSM BTS (LimeSuite)
ii  osmo-trx-uhd                            1.6.0.5.242c.202311212026      amd64        SDR transceiver that implements Layer 1 of a GSM BTS (UHD)
ii  osmocom-nightly                         202311212026                   amd64        Dummy package, con
Actions
Copy link
 #1

Updated by laforge 5 months ago

  • Subject changed from osmo-pcu sends version report every 5s? to osmo-bts sends version report every 5s to BSC?
Actions
Copy link
 #2

Updated by laforge 2 months ago

ping? This has been idle for 3 months.

Actions
Copy link
 #3

Updated by dexter 2 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

I am able to reproduce this. This happens indeed only when GPRS is not configured. The reason for this is that from the PCU's perspective the BTS never becomes active and this is why pcuif_sock:pcu_tx_txt_retry reschedules the timer over and over again. I have seen that on the BSC side the reception of the TXT message is used to trigger the sending of the system information parameters, so it seems to be vital for the proper operation of the PCUIF interface. However on OML we certainly do not need lots of copies of the same message. I think it should be ok when we only send the PCU_VERSION once (or when it changes)

There is now a patch in gerrit: https://gerrit.osmocom.org/c/osmo-bts/+/36018 pcu_sock: forward PCU_VERSION only once

Actions
Copy link

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)