Cellular Network Infrastructure » Core Network (CN) » osmo-gbproxy

If I start osmo-gbproxy, run a single TTCN3 test against it (so all BVC get up once), the output looks as follows:

OsmoGbProxy> show gbproxy bvc bss
NSEI  2003, SIG-BVCI     0 [UNBLOCKED]
NSEI  2003, PTP-BVCI 20031, RAI 262-42-13135-1 [UNBLOCKED]
NSEI  2003, PTP-BVCI 20032, RAI 262-42-13300-0 [UNBLOCKED]
NSEI  2003, PTP-BVCI 20033, RAI 262-42-13300-0 [UNBLOCKED]
NSEI  2001, SIG-BVCI     0 [UNBLOCKED]
NSEI  2001, PTP-BVCI 20011, RAI 262-42-13135-0 [UNBLOCKED]
NSEI  2002, SIG-BVCI     0 [UNBLOCKED]
NSEI  2002, PTP-BVCI 20021, RAI 262-42-13135-1 [UNBLOCKED]
NSEI  2002, PTP-BVCI 20022, RAI 262-42-13135-2 [UNBLOCKED]
OsmoGbProxy> show gbproxy bvc bss
NSEI  2003, SIG-BVCI     0 [UNBLOCKED]
NSEI  2003, PTP-BVCI 20031, RAI 262-42-13135-1 [UNBLOCKED]
NSEI  2003, PTP-BVCI 20032, RAI 262-42-13300-0 [UNBLOCKED]
NSEI  2003, PTP-BVCI 20033, RAI 262-42-13300-0 [UNBLOCKED]
NSEI  2001, SIG-BVCI     0 [UNBLOCKED]
NSEI  2001, PTP-BVCI 20011, RAI 262-42-13135-0 [UNBLOCKED]
NSEI  2002, SIG-BVCI     0 [UNBLOCKED]
NSEI  2002, PTP-BVCI 20021, RAI 262-42-13135-1 [UNBLOCKED]
NSEI  2002, PTP-BVCI 20022, RAI 262-42-13135-2 [UNBLOCKED]

However, even 10 minutes after the TTCN3 tester terminates (and hence all BSS and SGSN peers are gone), the output is still unchanged.

I guess a normal user would have expected that the BVCs would go into BLOCKED or some kind of recovery state if the underlying NSE disappears / becomes unavailable.

The same applies to

OsmoGbProxy> show gbproxy cell     
BVCI 20031 RAI 262-42-13135-1: BSS NSEI  2003, SGSN NSEI   101   102 
BVCI 20021 RAI 262-42-13135-1: BSS NSEI  2002, SGSN NSEI   101   102 
BVCI 20011 RAI 262-42-13135-0: BSS NSEI  2001, SGSN NSEI   101   102 
BVCI 20032 RAI 262-42-13300-0: BSS NSEI  2003, SGSN NSEI   101   102 
BVCI 20022 RAI 262-42-13135-2: BSS NSEI  2002, SGSN NSEI   101   102 
BVCI 20033 RAI 262-42-13300-0: BSS NSEI  2003, SGSN NSEI   101   102 

where the NSEI are shown even a long time after those NSEI are gone. Interestingly, when you start another test, they temporarily become

OsmoGbProxy> show gbproxy cell 
BVCI 20031 RAI 262-42-13135-1: BSS NSEI <none>, SGSN NSEI   101   102 
BVCI 20021 RAI 262-42-13135-1: BSS NSEI <none>, SGSN NSEI   101   102 
BVCI 20011 RAI 262-42-13135-0: BSS NSEI <none>, SGSN NSEI   101   102 
BVCI 20032 RAI 262-42-13300-0: BSS NSEI <none>, SGSN NSEI   101   102 
BVCI 20022 RAI 262-42-13135-2: BSS NSEI <none>, SGSN NSEI   101   102 
BVCI 20033 RAI 262-42-13300-0: BSS NSEI <none>, SGSN NSEI   101   102 

only to go bac kto 2001/2002/2003 a few seconds later. So the state is lost (maybe on BVC RESET?) In that case, maybe if the BVC would go to BLOCKED or some kind of other state, this would solve itself?

This may not seem super critical, but from an operational point of view, we will be wondering about this as soon as we go into deployment/testing, as will our users, AFAICT.