Actions
Bug #5006
closedNS2: Wrong state for NSVC that never comes up
Start date:
02/03/2021
Due date:
% Done:
100%
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
Updated by lynxis about 3 years ago
I would like to have a test case for:
- configure gbproxy with 2x initial sns nsvc
- react only on the 2nd nsvc.
- SNS config uses 2nd nsvc and 3rd nsvc (but not the 1st initial nsvc)
this should show the same UNCONFIGURED DYNAMIC.
Updated by daniel about 3 years ago
- Related to Bug #4887: ns2: Missing unittests added
Updated by lynxis about 3 years ago
- % Done changed from 0 to 40
the root cause should be fixed already.
Updated by lynxis over 2 years ago
"According to lynxis we should never be in the state UNCONFIGURED for an NSVC."
This is not anymore true. However the 1st NSVC should not show up at all!
Updated by lynxis over 2 years ago
- Status changed from New to Closed
- % Done changed from 40 to 100
I think I fixed both issues here already (the unconfigured dynamic and the NSE is DEAD). I couldn't reproduce this issue anymore.
Actions