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
Actions