blob: 057d1cadd90fb6d515140604c4d5f6b3c0faed98 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
== Configuring OsmoGbProxy
TBD. Unfortunately this chapter of the manual still needs to be written.
Osmocom has very limited funding and support resources; Feel free to help
us completing this documentation by contributing with code, documentation
or by supporting the developers financially.
=== 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.
|
