Project

General

Profile

Bug #5006

NS2: Wrong state for NSVC that never comes up

Added by daniel about 1 month ago. Updated 23 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
libosmogb
Target version:
-
Start date:
02/03/2021
Due date:
% Done:

40%

Spec Reference:

Description

There seems to be an issue with IP-SNS NSVCs that never come up:

OsmoGbProxy# show ns             
NSEI 00004: UDP, DEAD
 FSM Instance Name: 'GPRS-NS2-SNS-BSS(NSE00004-SNS)[0x55bfd8ffbf10]', ID: 'NSE00004-SNS'
  Log-Level: 'DEBUG', State: 'CONFIGURED'
 Maximum number of remote  NS-VCs: 8, IPv4 Endpoints: 4, IPv6 Endpoints: 0
 Local IPv4 Endpoints:
  10.0.0.1:2157, Signalling Weight: 2, Data Weight: 1
 Remote IPv4 Endpoints:
  10.0.0.2:43072, Signalling Weight: 1, Data Weight: 0
  10.0.0.2.168:2158, Signalling Weight: 0, Data Weight: 1
 NSVCI none: ALIVE DYNAMIC data_weight=1 sig_weight=0 udp)[10.0.0.1]:2157<>[10.0.0.2]:2158
 NSVCI none: ALIVE DYNAMIC data_weight=0 sig_weight=1 udp)[10.0.0.1]:2157<>[10.0.0.2]:43072
 NSVCI none: UNCONFIGURED DYNAMIC data_weight=1 sig_weight=1 udp)[10.0.0.1]:2157<>[10.0.0.2]:2157

Here remote port 2157 was configured in osmo-gbproxy, but all packets are dropped. According to lynxis we should never be in the state UNCONFIGURED for an NSVC.


Related issues

Related to libosmocore - Bug #4887: ns2: Missing unittestsResolved12/02/2020

History

#1 Updated by lynxis about 1 month ago

I would like to have a test case for:

  1. configure gbproxy with 2x initial sns nsvc
  2. react only on the 2nd nsvc.
  3. SNS config uses 2nd nsvc and 3rd nsvc (but not the 1st initial nsvc)

this should show the same UNCONFIGURED DYNAMIC.

#2 Updated by daniel 25 days ago

  • Related to Bug #4887: ns2: Missing unittests added

#3 Updated by lynxis 23 days ago

  • % Done changed from 0 to 40

the root cause should be fixed already.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)