Project

General

Profile

Actions

Bug #4958

closed

NSVC still makred as ALIVE even minutes after peer is gone

Added by laforge over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
01/19/2021
Due date:
% Done:

100%

Spec Reference:

Description

I start any TTCN3 testcase (like TC_BVC_bringup) and that test terminates.

Some minutes later I checkt the VTY output:

OsmoGbProxy> show ns nsei 101
NSEI 00101: UDP, DEAD
FSM Instance Name: 'GPRS-NS2-SNS-BSS(NSE00101-SNS)[0x6120000015a0]', ID: 'NSE00101-SNS'
 Log-Level: 'DEBUG', State: 'CONFIGURED'
Maximum number of remote  NS-VCs: 8, IPv4 Endpoints: 4, IPv6 Endpoints: 0
Local IPv4 Endpoints:
 127.0.0.1:23000, Signalling Weight: 2, Data Weight: 1
Remote IPv4 Endpoints:
 127.0.0.10:7777, Signalling Weight: 1, Data Weight: 0
 127.0.0.10:7770, Signalling Weight: 0, Data Weight: 1
 NSVCI none: ALIVE DYNAMIC data_weight=1 sig_weight=0 udp)[127.0.0.1]:23000<>[127.0.0.10]:7770
 NSVCI none: ALIVE DYNAMIC data_weight=0 sig_weight=1 udp)[127.0.0.1]:23000<>[127.0.0.10]:7777

As we can see, the NSE has gone to "DEAD", but magically its two NSVCs are still marked ALIVE at the bottom. This is fals. There's nothing that response to NS-ALIVE messages for several minutes already.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)