Project

General

Profile

Bug #4271

sctp-role and role seem to interfere

Added by roch 24 days ago. Updated 14 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/18/2019
Due date:
% Done:

100%


Description

Hi,

When configuring the ASP role as ASP and then setting the sctp-role as client,
the ASP role reverts to SG.

Here's the log:
OsmoSTP# show run

Current configuration:
!
!
log stderr
logging filter all 1
logging color 1
logging print category-hex 1
logging print category 1
logging timestamp 0
logging print file 1
logging level lglobal notice
logging level llapd notice
logging level linp notice
logging level lmux notice
logging level lmi notice
logging level lmib notice
logging level lsms notice
logging level lctrl notice
logging level lgtp notice
logging level lstats notice
logging level lgsup notice
logging level loap notice
logging level lss7 debug
logging level lsccp debug
logging level lsua debug
logging level lm3ua debug
logging level lmgcp notice
logging level ljibuf notice
logging level lrspro notice
!
stats interval 5
!
line vty
no login
!
cs7 instance 0
xua rkm routing-key-allocation dynamic-permitted
asp stp2 2919 2919 m3ua
local-ip 10.26.30.247
local-ip 10.26.31.247
remote-ip 199.255.7.133
role ASP
as STP2 m3ua
asp stp2
routing-key 56 0.8.6
route-table system
listen m3ua 2905
accept-asp-connections dynamic-permitted
listen ipa 5001
end
OsmoSTP# conf t
OsmoSTP(config)# cs7 instance 0
OsmoSTP(config-cs7)# asp stp2 2919 2919 m3ua
OsmoSTP(config-cs7-asp)# sc
OsmoSTP(config-cs7-asp)# sctp-role cli
OsmoSTP(config-cs7-asp)# sctp-role client
OsmoSTP(config-cs7-asp)# exit
OsmoSTP(config-cs7)# exit
OsmoSTP(config)# exit
OsmoSTP#
OsmoSTP#
OsmoSTP#
OsmoSTP# show run

Current configuration:
!
!
log stderr
logging filter all 1
logging color 1
logging print category-hex 1
logging print category 1
logging timestamp 0
logging print file 1
logging level lglobal notice
logging level llapd notice
logging level linp notice
logging level lmux notice
logging level lmi notice
logging level lmib notice
logging level lsms notice
logging level lctrl notice
logging level lgtp notice
logging level lstats notice
logging level lgsup notice
logging level loap notice
logging level lss7 debug
logging level lsccp debug
logging level lsua debug
logging level lm3ua debug
logging level lmgcp notice
logging level ljibuf notice
logging level lrspro notice
!
stats interval 5
!
line vty
no login
!
cs7 instance 0
xua rkm routing-key-allocation dynamic-permitted
asp stp2 2919 2919 m3ua
local-ip 10.26.30.247
local-ip 10.26.31.247
remote-ip 199.255.7.133
role SG
as STP2 m3ua
asp stp2
routing-key 56 0.8.6
route-table system
listen m3ua 2905
accept-asp-connections dynamic-permitted
listen ipa 5001
end

Thanks

Roch.

History

#1 Updated by laforge 24 days ago

On Mon, Nov 18, 2019 at 09:46:36PM +0000, roch [REDMINE] wrote:

When configuring the ASP role as ASP and then setting the sctp-role as client,
the ASP role reverts to SG.

Thanks for this bug report. It indeed was true that every time you re-entered a
given 'asp' node, they ASP role would be reset to the default (SG) and the sctp-role
would be reset to server (default).

Those defaults should of course only be set if the ASP node is just newly created,
and not for any ASP that already existed before entering the ASP node again.

This bug is fixed by https://gerrit.osmocom.org/c/libosmo-sccp/+/16099 and
https://gerrit.osmocom.org/c/libosmo-sccp/+/16100

#2 Updated by laforge 24 days ago

  • Status changed from New to In Progress
  • Assignee set to laforge
  • % Done changed from 0 to 80

#3 Updated by laforge 14 days ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100

patch merged some time ago.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)