Bug #5186
Updated by keith almost 3 years ago
_keyphrase from osmo-bsc log for search engines:_
<pre>
DLSS7 ERROR m3ua.c:507 XUA_AS(as-clnt-A-0-m3ua) {AS_DOWN}: Event AS-TRANSFER.req not permitted
</pre>
In osmo-stp.cfg we have typically have something like:
<pre>
cs7 instance 0
xua rkm routing-key-allocation dynamic-permitted
route-table system
listen m3ua 2905
local-ip ::
accept-asp-connections dynamic-permitted
</pre>
This is actually fine.
But, the configuration VTY tells us:
<pre>
OsmoSTP(config-cs7-listen)# local-ip
A.B.C.D IPv4 Address to use for XUA
X:X::X:X IPv6 Address to use for XUA
</pre>
and so the user might think, ah OK I want to use 127.0.0.1 resulting in a config of
<pre>
cs7 instance 0
xua rkm routing-key-allocation dynamic-permitted
route-table system
listen m3ua 2905
local-ip 127.0.0.1
accept-asp-connections dynamic-permitted
</pre>
Actually local-ip 0.0.0.0 will also trigger this issue.
Now let's start osmo-bsc and osmo-msc with the minimal configuration files needed needs to start up, leaving the rest to default values for the sake of clarify here, although this issue can be observed with a fully configured BSC/MSC:
*osmo-bsc.cfg:*
<pre>
msc 0
mgw remote-ip 127.0.0.1
</pre>
*osmo-msc.cfg:*
BLANK - Use all defaults.
osmo-bsc will constantly log: Event AS-TRANSFER.req not permitted
although osmo-bsc vty will show:
<pre>
OsmoBSC# show msc
0 m3ua RI=SSN_PC,PC=0.23.3,SSN=BSSAP RI=SSN_PC,PC=0.23.1,SSN=BSSAP
</pre>
osmo-msc vty will show:
<pre>
OsmoMSC# show bsc
OsmoMSC#
</pre>
So one should *NOT* use an ipv4 address in local-ip, *UNLESS* ipv6 stack is disabled with:
<pre>
sysctl net.ipv6.conf.all.disable_ipv6=1
</pre>
If you have OSMO-STP config with an IPv4 address in local-ip, as soon as you disable the ipv6 stack, you'll see:
<pre>
[other log messages leading up to...]
DMSC NOTICE (msc0) BSSMAP assocation is up
</pre>
To confirm:
with *local-ip ::*
there's no problem with ipv4/ipv6 being enabled or not.
