aboutsummaryrefslogtreecommitdiffstats
path: root/doc/manuals
diff options
context:
space:
mode:
authorDaniel Willmann <dwillmann@sysmocom.de>2021-01-27 19:32:33 +0100
committerDaniel Willmann <dwillmann@sysmocom.de>2021-01-28 20:57:16 +0100
commitf955d078eda0dc333c2b6d9f5ef2506c148b0366 (patch)
treea50ddb8d92fe1cfe26078e2940db90adc76f25ac /doc/manuals
parent93ccc3cf5da525d885433e569bb89ae05a02a448 (diff)
manuals/gbproxy: Move pooling to separate chapter
Diffstat (limited to 'doc/manuals')
-rw-r--r--doc/manuals/chapters/gbproxy-configuration.adoc24
-rw-r--r--doc/manuals/chapters/gbproxy-sgsnpool.adoc25
2 files changed, 25 insertions, 24 deletions
diff --git a/doc/manuals/chapters/gbproxy-configuration.adoc b/doc/manuals/chapters/gbproxy-configuration.adoc
index 726ec41ad..87da471ff 100644
--- a/doc/manuals/chapters/gbproxy-configuration.adoc
+++ b/doc/manuals/chapters/gbproxy-configuration.adoc
@@ -39,27 +39,3 @@ sgsn 101 <1>
<1> Each SGSN is identified by its NSEI (same as in the NS configuration)
<2> An SGSN can optionally have a name. If none is set a default name will be used.
-=== SGSN pool support
-
-In a SGSN pool, osmo-gbproxy is facing the problem of dividing the downlink
-capacity of a cell towards the SGSN. The BSS advertises the per-BVC capacity
-by means of the BSSGP FLOW-CONTROL-BVC messages, but as there are multiple
-SGSN in a pool, they all have to share / divide that total capacity.
-
-By default, osmo-gbproxy advertises the full capacity to _each_ of the SGSN
-pool members, which results in significant over-provisioning and can lead to
-overload situations.
-
-The administrator can configure the _percentage_ of the overall BSS-advertised
-capacity that shall be reported to each pool member SGSN using the
-`pool bvc-flow-control-ratio <1-100>` configuration command.
-
-A setting of 100 means that each pool member is informed of 100% of the
-BSS side capacity.
-
-A setting of 25 means that each pool member is informed of 25% of the
-BSS side capacity. This would make most sense in a set-up with four
-SGSN of equal share.
-
-More complex capacity division schemes are so far not supported by
-osmo-gbproxy.
diff --git a/doc/manuals/chapters/gbproxy-sgsnpool.adoc b/doc/manuals/chapters/gbproxy-sgsnpool.adoc
index c600bcfae..61806af8c 100644
--- a/doc/manuals/chapters/gbproxy-sgsnpool.adoc
+++ b/doc/manuals/chapters/gbproxy-sgsnpool.adoc
@@ -192,3 +192,28 @@ To re-enable an SGSN for attaching new subscribers:
sgsn nsei 1
allow-attach
----
+
+==== Traffic allocation
+
+In a SGSN pool, osmo-gbproxy is facing the problem of dividing the downlink
+capacity of a cell towards the SGSN. The BSS advertises the per-BVC capacity
+by means of the BSSGP FLOW-CONTROL-BVC messages, but as there are multiple
+SGSN in a pool, they all have to share / divide that total capacity.
+
+By default, osmo-gbproxy advertises the full capacity to _each_ of the SGSN
+pool members, which results in significant over-provisioning and can lead to
+overload situations.
+
+The administrator can configure the _percentage_ of the overall BSS-advertised
+capacity that shall be reported to each pool member SGSN using the
+`pool bvc-flow-control-ratio <1-100>` configuration command.
+
+A setting of 100 means that each pool member is informed of 100% of the
+BSS side capacity.
+
+A setting of 25 means that each pool member is informed of 25% of the
+BSS side capacity. This would make most sense in a set-up with four
+SGSN of equal share.
+
+More complex capacity division schemes are so far not supported by
+osmo-gbproxy.