Bug #4856

PCU is running but has no NS connection and does not retry.

Added by keith 9 months ago. Updated about 1 month ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Spec Reference:


It has been noticed that at times osmo-bts, osmo-pcu are up and running on a sysmobts, GPRS is configured but there is no NS connection to the SGSN.

What I don't have about this:

  • A method to reproduce.
  • logs leading up to failure.
  • I don't know if the NS was up and failed, or if it never came up on pcu startup.
  • osmo-bts and pcu are not current master, if fact there are some various versions installed.. (BSC is nitb)

As I am writing this, I have one case of running osmo-pcu with no connection.

pcu is not logging ANYTHING. (logging level set-all debug)
version: OsmoPCU
show stats: all counters are zero.

ntib shows all of the "states" Oper 'Enabled', Admin 'Unlocked', Avail 'OK'
as does the associated pcu osmo-bts

also, shows PCU connected:

OpenBSC# show bts 2
BTS 2 is of sysmobts type in band GSM850, has CI 2 LAC 269, BSIC 63 (NCC=7, BCC=7) and 1 TRX
Description: (null)
PCU version connected

To possibly simplify a little:
It seems to be that the PCU is in a states where it "knows" that the NS is down

OsmoPCU# show ns
Encapsulation NS-UDP-IP     Local IP:, UDP Port: 0

yet it it not trying to bring it up.
Maybe the bts did not inform the PCU of the config?

show bts statistics: also all counters at ZERO.
all rate-counters are zero.

really looks like it was never initialised.

Maybe needless to say, but worth adding - systemctl restart osmo-pcu restores service.


#1 Updated by keith 9 months ago

  • Description updated (diff)

#2 Updated by lynxis 8 months ago

OsmoPCU# show ns
Encapsulation NS-UDP-IP     Local IP:, UDP Port: 0

This looks like there wasn't any NS configuration transmitted over the PCU socket. Can you update to the latest PCU?

#3 Updated by pespin 2 months ago

  • Status changed from New to Feedback

Hi keith , can you comment on whether you still see this issue? I'd say the issue was probably due to some bug in early NS2 implementation.

#4 Updated by keith 2 months ago

Hi pespin I'm pretty sure it's fixed now, I haven't seen it happen with current osmo-pcu.

#5 Updated by keith 2 months ago

  • Status changed from Feedback to Closed

#6 Updated by keith about 1 month ago

  • Status changed from Closed to In Progress

Unfortunately I have to re-open this as I am still observing it.

At least with osmocom 'latest' release.

Stack running on the BTS itself is more recent.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)