<p>daniel has uploaded this change for <strong>review</strong>.</p><p><a href="https://gerrit.osmocom.org/c/osmo-sgsn/+/22495">View Change</a></p><pre style="font-family: monospace,monospace; white-space: pre-wrap;">manuals/gbproxy: MSC -> SGSN for pooling chapter<br><br>Mostly just change the chapter so it makes sense for gbproxy. Some todos<br>are still left<br><br>Change-Id: I905835c2be7be43fe376fbc9d743107948c7e6d4<br>Related: SYS#5115, SYS#5005<br>---<br>M doc/manuals/chapters/gbproxy-sgsnpool.adoc<br>1 file changed, 85 insertions(+), 104 deletions(-)<br><br></pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;">git pull ssh://gerrit.osmocom.org:29418/osmo-sgsn refs/changes/95/22495/1</pre><pre style="font-family: monospace,monospace; white-space: pre-wrap;"><span>diff --git a/doc/manuals/chapters/gbproxy-sgsnpool.adoc b/doc/manuals/chapters/gbproxy-sgsnpool.adoc</span><br><span>index 923a088..c600bcf 100644</span><br><span>--- a/doc/manuals/chapters/gbproxy-sgsnpool.adoc</span><br><span>+++ b/doc/manuals/chapters/gbproxy-sgsnpool.adoc</span><br><span>@@ -1,96 +1,87 @@</span><br><span style="color: hsl(0, 100%, 40%);">-== MSC Pooling</span><br><span style="color: hsl(120, 100%, 40%);">+== SGSN Pooling</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-MSC pooling is described in 3GPP TS 23.236 <<3gpp-ts-23-236>>, and is supported</span><br><span style="color: hsl(0, 100%, 40%);">-by OsmoBSC since mid 2020.</span><br><span style="color: hsl(120, 100%, 40%);">+SGSN pooling is described in 3GPP TS 23.236 <<3gpp-ts-23-236>>, and is supported</span><br><span style="color: hsl(120, 100%, 40%);">+by OsmoGbProxy since early 2021.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The aim of MSC pooling is to distribute load from a BSC across multiple MSCs,</span><br><span style="color: hsl(120, 100%, 40%);">+The aim of SGSN pooling is to distribute load from a BSS across multiple SGSNs,</span><br><span> which are equivalent and redundant infrastructure for the same core network.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The main mechanism for MSC pooling is the TMSI identity, which an MSC hands out</span><br><span style="color: hsl(0, 100%, 40%);">-to its attached subscribers. Typically 10 bits of the TMSI are designated as a</span><br><span style="color: hsl(0, 100%, 40%);">-Network Resource Identifier (NRI) that identifies the originating MSC, and</span><br><span style="color: hsl(0, 100%, 40%);">-allows OsmoBSC to direct a subscriber back to the same MSC instance that</span><br><span style="color: hsl(0, 100%, 40%);">-previously negotiated the IMSI Attach procedure. Typically, the full NRI value</span><br><span style="color: hsl(0, 100%, 40%);">-range available is divided into N even ranges, where each MSC is assigned one</span><br><span style="color: hsl(120, 100%, 40%);">+The main mechanism for SGSN pooling is the TLLI/P-TMSI, which an SGSN hands out</span><br><span style="color: hsl(120, 100%, 40%);">+to its attached subscribers. Typically 10 bits of the P-TMSI are designated as a</span><br><span style="color: hsl(120, 100%, 40%);">+Network Resource Identifier (NRI) that identifies the originating SGSN, and</span><br><span style="color: hsl(120, 100%, 40%);">+allows OsmoGbProxy to direct a subscriber back to the same SGSN instance that</span><br><span style="color: hsl(120, 100%, 40%);">+previously negotiated the Attach procedure. Typically, the full NRI value</span><br><span style="color: hsl(120, 100%, 40%);">+range available is divided into N even ranges, where each SGSN is assigned one</span><br><span> NRI range.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Subscribers attaching without a TMSI identity, or those with unknown NRI value,</span><br><span style="color: hsl(0, 100%, 40%);">-are evenly distributed across MSC instances. OsmoBSC uses a round-robin</span><br><span style="color: hsl(0, 100%, 40%);">-approach to distribute load across all connected MSCs.</span><br><span style="color: hsl(120, 100%, 40%);">+Subscribers attaching without a TLLI, or those with unknown NRI value,</span><br><span style="color: hsl(120, 100%, 40%);">+are evenly distributed across SGSN instances. OsmoGbProxy uses a hash-based</span><br><span style="color: hsl(120, 100%, 40%);">+approach to distribute load across all connected SGSNs.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-A Paging Response from a subscriber is always returned back to whichever MSC</span><br><span style="color: hsl(120, 100%, 40%);">+A Paging Response from a subscriber is always returned back to whichever SGSN</span><br><span> initiated the Paging, regardless of the Mobile Identity used.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Finally, a NULL-NRI is a special NRI value that indicates that the MSC wishes</span><br><span style="color: hsl(0, 100%, 40%);">-to offload this subscriber to a different MSC. A NULL-NRI is an arbitrary NRI</span><br><span style="color: hsl(0, 100%, 40%);">-value that is chosen distinctly for each PLMN served by a BSC, so that a</span><br><span style="color: hsl(120, 100%, 40%);">+Finally, a NULL-NRI is a special NRI value that indicates that the SGSN wishes</span><br><span style="color: hsl(120, 100%, 40%);">+to offload this subscriber to a different SGSN. A NULL-NRI is an arbitrary NRI</span><br><span style="color: hsl(120, 100%, 40%);">+value that is chosen distinctly for each PLMN served by a BSS, so that a</span><br><span> subscriber can be reassigned within that PLMN. Upon (periodic) Location</span><br><span style="color: hsl(0, 100%, 40%);">-Updating, an offloading MSC hands out a NULL-NRI value in the assigned TMSI,</span><br><span style="color: hsl(120, 100%, 40%);">+Updating, an offloading SGSN hands out a NULL-NRI value in the assigned TLLI,</span><br><span> along with a non-broadcast LAI. The subscriber will notice the LAI mismatch,</span><br><span style="color: hsl(0, 100%, 40%);">-and immediately re-attempt the attach using the TMSI containing the NULL-NRI.</span><br><span style="color: hsl(0, 100%, 40%);">-The BSC recognises the NULL-NRI and redirects the subscriber to one of the</span><br><span style="color: hsl(0, 100%, 40%);">-other MSCs. A prerequisite for this to work well is that the particular MSC is</span><br><span style="color: hsl(0, 100%, 40%);">-previously marked as not accepting new subscribers, in the BSC's configuration.</span><br><span style="color: hsl(120, 100%, 40%);">+and immediately re-attempt the attach using the TLLI containing the NULL-NRI.</span><br><span style="color: hsl(120, 100%, 40%);">+OsmoGbProxy recognises the NULL-NRI and redirects the subscriber to one of the</span><br><span style="color: hsl(120, 100%, 40%);">+other SGSNs. A prerequisite for this to work well is that the particular SGSN is</span><br><span style="color: hsl(120, 100%, 40%);">+previously marked as not accepting new subscribers, in OsmoGbProxy's configuration.</span><br><span> </span><br><span> The mechanisms described above make up the NAS node selection function</span><br><span style="color: hsl(0, 100%, 40%);">-implemented in the BSC.</span><br><span style="color: hsl(120, 100%, 40%);">+implemented in OsmoGbProxy.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-3GPP TS 23.236 also defines that an offloading MSC hands subscriber information</span><br><span style="color: hsl(0, 100%, 40%);">-to the newly assigned MSC, which takes place outside the scope of the BSC.</span><br><span style="color: hsl(120, 100%, 40%);">+3GPP TS 23.236 also defines that an offloading SGSN hands subscriber information</span><br><span style="color: hsl(120, 100%, 40%);">+to the newly assigned SGSN, which takes place outside the scope of OsmoGbProxy.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-=== Configuring MSC Pooling</span><br><span style="color: hsl(120, 100%, 40%);">+=== Configuring SGSN Pooling</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-The NRI ranges assigned to each MSC must match in the BSC and the MSC</span><br><span style="color: hsl(0, 100%, 40%);">-configuration. If MSC and BSC had inconsistent NRI value ranges configured,</span><br><span style="color: hsl(0, 100%, 40%);">-attached subscribers would be redirected MSC instances that did not perform the</span><br><span style="color: hsl(120, 100%, 40%);">+The NRI ranges assigned to each SGSN must match in the OsmoGbProxy and the SGSN</span><br><span style="color: hsl(120, 100%, 40%);">+configuration. If inconsistent NRI value ranges are configured,</span><br><span style="color: hsl(120, 100%, 40%);">+attached subscribers would be redirected to SGSN instances that did not perform the</span><br><span> attach, possibly rendering the core network unusable.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== Connecting Multiple MSCs</span><br><span style="color: hsl(0, 100%, 40%);">-</span><br><span style="color: hsl(0, 100%, 40%);">-The `cs7 instance` configuration defines the SCCP addresses to reach the MSCs</span><br><span style="color: hsl(0, 100%, 40%);">-at. In addition, each MSC is configured by its own `msc` section in the</span><br><span style="color: hsl(0, 100%, 40%);">-configuration. An example osmo-bsc.cfg serving three MSCs:</span><br><span style="color: hsl(120, 100%, 40%);">+==== Connecting Multiple SGSNs</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-cs7 instance 0</span><br><span style="color: hsl(0, 100%, 40%);">- # SCCP address book entries for the three MSCs</span><br><span style="color: hsl(0, 100%, 40%);">- sccp-address my-msc-0</span><br><span style="color: hsl(0, 100%, 40%);">- point-code 0.23.0</span><br><span style="color: hsl(0, 100%, 40%);">- sccp-address my-msc-1</span><br><span style="color: hsl(0, 100%, 40%);">- point-code 0.23.1</span><br><span style="color: hsl(0, 100%, 40%);">- sccp-address my-msc-2</span><br><span style="color: hsl(0, 100%, 40%);">- point-code 0.23.2</span><br><span style="color: hsl(0, 100%, 40%);">-</span><br><span style="color: hsl(0, 100%, 40%);">-# assign each MSC configuration its remote SCCP address</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(0, 100%, 40%);">- msc-addr my-msc-0</span><br><span style="color: hsl(0, 100%, 40%);">-msc 1</span><br><span style="color: hsl(0, 100%, 40%);">- msc-addr my-msc-1</span><br><span style="color: hsl(0, 100%, 40%);">-msc 2</span><br><span style="color: hsl(0, 100%, 40%);">- msc-addr my-msc-2</span><br><span style="color: hsl(0, 100%, 40%);">-</span><br><span style="color: hsl(120, 100%, 40%);">+# Configure the Network Service</span><br><span style="color: hsl(120, 100%, 40%);">+ns</span><br><span style="color: hsl(120, 100%, 40%);">+ bind udp sgsn</span><br><span style="color: hsl(120, 100%, 40%);">+ listen 10.0.0.1 23000</span><br><span style="color: hsl(120, 100%, 40%);">+ nse 1</span><br><span style="color: hsl(120, 100%, 40%);">+ ip-sns 10.0.1.1 23000</span><br><span style="color: hsl(120, 100%, 40%);">+ ip-sns 10.0.1.1 23001</span><br><span style="color: hsl(120, 100%, 40%);">+ nse 2</span><br><span style="color: hsl(120, 100%, 40%);">+ ip-sns 10.0.1.2 23000</span><br><span style="color: hsl(120, 100%, 40%);">+ nse 3</span><br><span style="color: hsl(120, 100%, 40%);">+ ip-sns 10.0.1.3 23000</span><br><span> # configure NRI value ranges</span><br><span style="color: hsl(0, 100%, 40%);">-network</span><br><span style="color: hsl(120, 100%, 40%);">+gbproxy</span><br><span> nri bitlen 10</span><br><span> nri null add 0</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn 1</span><br><span> nri add 1 341</span><br><span style="color: hsl(0, 100%, 40%);">-msc 1</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn 2</span><br><span> nri add 342 682</span><br><span style="color: hsl(0, 100%, 40%);">-msc 2</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn 3</span><br><span> nri add 683 1023</span><br><span> ----</span><br><span> </span><br><span> ==== NRI Value Bit Length</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-In OsmoBSC, the NRI value's bit length is freely configurable from 1 to 15</span><br><span style="color: hsl(0, 100%, 40%);">-bits. 3GPP TS 23.236 suggests a typical bit length of 10, which is OsmoBSC's</span><br><span style="color: hsl(0, 100%, 40%);">-default. The NRI bit length must be identical across the entire MSC pool.</span><br><span style="color: hsl(120, 100%, 40%);">+In OsmGbProxy, the NRI value's bit length is freely configurable from 0 to 15</span><br><span style="color: hsl(120, 100%, 40%);">+bits. 3GPP TS 23.236 suggests a typical bit length of 10. Setting the length</span><br><span style="color: hsl(120, 100%, 40%);">+to 0 disables SGSN pooling, this is also the default.</span><br><span style="color: hsl(120, 100%, 40%);">+The NRI bit length must be identical across the entire SGSN pool.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Change the NRI value bit length in OsmoBSC's VTY configuration like this:</span><br><span style="color: hsl(120, 100%, 40%);">+Change the NRI value bit length in OsmoGbProxy's VTY configuration like this:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-network</span><br><span style="color: hsl(120, 100%, 40%);">+gbproxy</span><br><span> nri bitlen 10</span><br><span> ----</span><br><span> </span><br><span>@@ -100,9 +91,9 @@</span><br><span> </span><br><span> ==== NULL-NRI</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Since OsmoBSC supports serving only one PLMN, NULL-NRI are configured globally.</span><br><span style="color: hsl(120, 100%, 40%);">+Since OsmoGbProxy supports serving only one PLMN, NULL-NRI are configured globally.</span><br><span> Even though 3GPP TS 23.236 indicates that there is a single NULL-NRI per PLMN,</span><br><span style="color: hsl(0, 100%, 40%);">-OsmoBSC allows configuring multiple NULL-NRI values.</span><br><span style="color: hsl(120, 100%, 40%);">+OsmoGbProxy allows configuring multiple NULL-NRI values.</span><br><span> </span><br><span> ----</span><br><span> network</span><br><span>@@ -110,9 +101,9 @@</span><br><span> nri null add 423</span><br><span> ----</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== Assigning NRI Ranges to MSCs</span><br><span style="color: hsl(120, 100%, 40%);">+==== Assigning NRI Ranges to SGSNs</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-Each MSC configured in OsmoBSC must be assigned a distinct NRI value range.</span><br><span style="color: hsl(120, 100%, 40%);">+Each SGSN configured in OsmoGbProxy must be assigned a distinct NRI value range.</span><br><span> Overlapping NRI value ranges will cause failure to serve subscribers.</span><br><span> </span><br><span> NRI values are typically configured in ranges, here dividing a 10bit range</span><br><span>@@ -120,18 +111,18 @@</span><br><span> as NULL-NRI:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> nri add 1 341</span><br><span style="color: hsl(0, 100%, 40%);">-msc 1</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 2</span><br><span> nri add 342 684</span><br><span style="color: hsl(0, 100%, 40%);">-msc 2</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 3</span><br><span> nri add 685 1023</span><br><span> ----</span><br><span> </span><br><span> NRI can also be assigned in single values:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> nri add 23</span><br><span> ----</span><br><span> </span><br><span>@@ -139,75 +130,65 @@</span><br><span> configurations, here a contrived example:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> nri add 0 342</span><br><span> nri del 23</span><br><span> nri del 42 235</span><br><span> nri add 1000 1023</span><br><span> ----</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-To view the current NRI config in a running OsmoBSC instance, use the</span><br><span style="color: hsl(0, 100%, 40%);">-`show nri` command, here showing the result of the contrived example:</span><br><span style="color: hsl(120, 100%, 40%);">+On the VIEW and ENABLE VTY nodes, `show nri all` shows all SGSNs:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-OsmoBSC(config-msc)# show nri</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(0, 100%, 40%);">- nri add 0 22</span><br><span style="color: hsl(0, 100%, 40%);">- nri add 24 41</span><br><span style="color: hsl(0, 100%, 40%);">- nri add 236 342</span><br><span style="color: hsl(0, 100%, 40%);">- nri add 1000 1023</span><br><span>-----</span><br><span style="color: hsl(0, 100%, 40%);">-</span><br><span style="color: hsl(0, 100%, 40%);">-On the VIEW and ENABLE VTY nodes, `show nri` shows all MSCs:</span><br><span style="color: hsl(0, 100%, 40%);">-</span><br><span>-----</span><br><span style="color: hsl(0, 100%, 40%);">-OsmoBSC> show nri</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+OsmoGbProxy> show nri all</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> nri add 1 341</span><br><span style="color: hsl(0, 100%, 40%);">-msc 1</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 2</span><br><span> nri add 342 684</span><br><span style="color: hsl(0, 100%, 40%);">-msc 2</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 3</span><br><span> nri add 685 1023</span><br><span> ----</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-When configuring overlapping NRI value ranges across MSCs, the telnet VTY warns</span><br><span style="color: hsl(0, 100%, 40%);">-about it, and starting OsmoBSC with such a configuration will fail:</span><br><span style="color: hsl(120, 100%, 40%);">+When configuring overlapping NRI value ranges across SGSNs, the telnet VTY warns</span><br><span style="color: hsl(120, 100%, 40%);">+about it, and starting OsmoGbProxy with such a configuration will fail:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> nri add 1 511</span><br><span style="color: hsl(0, 100%, 40%);">-msc 1</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 2</span><br><span> nri add 512 1023</span><br><span style="color: hsl(0, 100%, 40%);">-msc 2</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 3</span><br><span> nri add 500 555</span><br><span> ----</span><br><span> </span><br><span> This results in:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-$ osmo-bsc</span><br><span style="color: hsl(0, 100%, 40%);">-DMSC ERROR msc 2: NRI range [500..555] overlaps between msc 2 and msc 0. For overlaps, msc 0 has higher priority than msc 2</span><br><span style="color: hsl(0, 100%, 40%);">-DMSC ERROR msc 2: NRI range [500..555] overlaps between msc 2 and msc 1. For overlaps, msc 1 has higher priority than msc 2</span><br><span style="color: hsl(120, 100%, 40%);">+$ osmo-gbproxy</span><br><span style="color: hsl(120, 100%, 40%);">+% Warning: NSE(00003/SGSN): NRI range [500..555] overlaps between NSE 00003 and NSE 00001. For overlaps, NSE 00001 has higher priority than NSE 00003</span><br><span style="color: hsl(120, 100%, 40%);">+% Warning: NSE(00003/SGSN): NRI range [500..555] overlaps between NSE 00003 and NSE 00002. For overlaps, NSE 00002 has higher priority than NSE 00003</span><br><span> ----</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-==== MSC Offloading</span><br><span style="color: hsl(120, 100%, 40%);">+==== SGSN Offloading</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-To effectively offload a particular MSC, it must be marked as no longer taking</span><br><span style="color: hsl(0, 100%, 40%);">-new subscribers in OsmoBSC. This can be achieved in the telnet VTY by:</span><br><span style="color: hsl(120, 100%, 40%);">+To effectively offload a particular SGSN, it must be marked as no longer taking</span><br><span style="color: hsl(120, 100%, 40%);">+new subscribers in OsmoGbProxy. This can be achieved in the telnet VTY by:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> no allow-attach</span><br><span> ----</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-This MSC will, as long as it is connected, continue to serve subscribers</span><br><span style="color: hsl(0, 100%, 40%);">-already attached to it: those that yield an NRI matching this MSC, and those</span><br><span style="color: hsl(0, 100%, 40%);">-that are being paged by this MSC. But OsmoBSC will no longer direct new</span><br><span style="color: hsl(0, 100%, 40%);">-subscribers to this MSC.</span><br><span style="color: hsl(120, 100%, 40%);">+This SGSN will, as long as it is connected, continue to serve subscribers</span><br><span style="color: hsl(120, 100%, 40%);">+already attached to it: those that yield an NRI matching this SGSN, and those</span><br><span style="color: hsl(120, 100%, 40%);">+that are being paged by this SGSN. But OsmoGbProxy will no longer direct new</span><br><span style="color: hsl(120, 100%, 40%);">+subscribers to this SGSN.</span><br><span> </span><br><span style="color: hsl(0, 100%, 40%);">-To re-enable an MSC for attaching new subscribers:</span><br><span style="color: hsl(120, 100%, 40%);">+TODO: Is paging response relevant for SGSN?</span><br><span style="color: hsl(120, 100%, 40%);">+</span><br><span style="color: hsl(120, 100%, 40%);">+To re-enable an SGSN for attaching new subscribers:</span><br><span> </span><br><span> ----</span><br><span style="color: hsl(0, 100%, 40%);">-msc 0</span><br><span style="color: hsl(120, 100%, 40%);">+sgsn nsei 1</span><br><span> allow-attach</span><br><span> ----</span><br><span></span><br></pre><p>To view, visit <a href="https://gerrit.osmocom.org/c/osmo-sgsn/+/22495">change 22495</a>. To unsubscribe, or for help writing mail filters, visit <a href="https://gerrit.osmocom.org/settings">settings</a>.</p><div itemscope itemtype="http://schema.org/EmailMessage"><div itemscope itemprop="action" itemtype="http://schema.org/ViewAction"><link itemprop="url" href="https://gerrit.osmocom.org/c/osmo-sgsn/+/22495"/><meta itemprop="name" content="View Change"/></div></div>
<div style="display:none"> Gerrit-Project: osmo-sgsn </div>
<div style="display:none"> Gerrit-Branch: master </div>
<div style="display:none"> Gerrit-Change-Id: I905835c2be7be43fe376fbc9d743107948c7e6d4 </div>
<div style="display:none"> Gerrit-Change-Number: 22495 </div>
<div style="display:none"> Gerrit-PatchSet: 1 </div>
<div style="display:none"> Gerrit-Owner: daniel <dwillmann@sysmocom.de> </div>
<div style="display:none"> Gerrit-MessageType: newchange </div>