October 2022 - gerrit-log - lists.osmocom.org

Change in osmo-gsm-manuals[master]: mgwpool.adoc: Use {program-name} instead of BSC

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29827 ) Change subject: mgwpool.adoc: Use {program-name} instead of BSC ...................................................................... mgwpool.adoc: Use {program-name} instead of BSC Change-Id: Iab6560d833e405a36bab142759719377ad302667 --- M common/chapters/mgwpool.adoc 1 file changed, 2 insertions(+), 2 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-gsm-manuals refs/changes/27/29827/1 diff --git a/common/chapters/mgwpool.adoc b/common/chapters/mgwpool.adoc index 01bf5ea..c8f2009 100644 --- a/common/chapters/mgwpool.adoc +++ b/common/chapters/mgwpool.adoc @@ -11,8 +11,8 @@ the pool will automatically assign the call to the MGW with the lowest load. MGW pooling is recommended for larger RAN or CN installations. For small networks -and lab installations the classic method with one MGW per BSC offers sufficient -performance. +and lab installations the classic method with one MGW per {program-name} offers +sufficient performance. === MGW pool VTY configuration -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29827 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: Iab6560d833e405a36bab142759719377ad302667 Gerrit-Change-Number: 29827 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-MessageType: newchange

2 years, 8 months

1
0
0 0

Change in osmo-hnbgw[master]: Introduce support for libosmo-mgcp-client MGW pooling

by osmith

Attention is currently required from: laforge, pespin, fixeria, dexter. osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/29806 ) Change subject: Introduce support for libosmo-mgcp-client MGW pooling ...................................................................... Patch Set 3: Code-Review+2 (1 comment) Patchset: PS3: combining previous votes after minor fixup -- To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/29806 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hnbgw Gerrit-Branch: master Gerrit-Change-Id: I371dc773b58788ee21037dc25d77f556c89c6b61 Gerrit-Change-Number: 29806 Gerrit-PatchSet: 3 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-Comment-Date: Thu, 20 Oct 2022 15:06:34 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 8 months

1
0
0 0

Change in osmo-hnbgw[master]: doc: Include mgwpool.adoc from osmo-gsm-manuals

by osmith

Attention is currently required from: pespin, daniel, dexter. osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/29822 ) Change subject: doc: Include mgwpool.adoc from osmo-gsm-manuals ...................................................................... Patch Set 2: Code-Review+1 (3 comments) File doc/manuals/chapters/running.adoc: https://gerrit.osmocom.org/c/osmo-hnbgw/+/29822/comment/1722856f_354213ef PS1, Line 146: OsmoMSC > OsmoHNBGW? Done https://gerrit.osmocom.org/c/osmo-hnbgw/+/29822/comment/42847406_c1d52bff PS1, Line 148: OsmoMSC > same Done https://gerrit.osmocom.org/c/osmo-hnbgw/+/29822/comment/01927850_13b643ec PS1, Line 158: OsmoMSC > same Done -- To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/29822 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hnbgw Gerrit-Branch: master Gerrit-Change-Id: I3dc8a4b50f13ad50390ba82e64fe4ebe0b97d4e5 Gerrit-Change-Number: 29822 Gerrit-PatchSet: 2 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Attention: daniel <dwillmann(a)sysmocom.de> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-Comment-Date: Thu, 20 Oct 2022 15:05:09 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: daniel <dwillmann(a)sysmocom.de> Gerrit-MessageType: comment

2 years, 8 months

1
0
0 0

Change in osmo-gsm-manuals[master]: Copy mgwpool.adoc from osmo-bsc.git

by pespin

pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29819 ) Change subject: Copy mgwpool.adoc from osmo-bsc.git ...................................................................... Copy mgwpool.adoc from osmo-bsc.git Copied from osmo-bsc.git/doc/manuals/chapters/mgwpool.adoc, version from Change-Id Id0d292506e8b2a888c8d7a682a38db80e9d0933a Related: SYS#5987 Change-Id: Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b --- A common/chapters/mgwpool.adoc 1 file changed, 239 insertions(+), 0 deletions(-) Approvals: Jenkins Builder: Verified daniel: Looks good to me, but someone else must approve osmith: Looks good to me, but someone else must approve pespin: Looks good to me, approved diff --git a/common/chapters/mgwpool.adoc b/common/chapters/mgwpool.adoc new file mode 100644 index 0000000..c429159 --- /dev/null +++ b/common/chapters/mgwpool.adoc @@ -0,0 +1,239 @@ +[[mgw_pooling]] +== MGW Pooling + +{program-name} is able to use a pool of media gateway (MGW) instances. +The aim of MGW pooling is to evenly distribute the RTP voice stream load across +multiple MGW instances. This can help to scale out over multiple VMs or physical +machines. Until osmo-mgw includes multithreading support, it may also be used to +scale-out to multiple cores on a single host. + +The load distribution is managed in such a way that when a new call is placed, +the pool will automatically assign the call to the MGW with the lowest load. + +MGW pooling is recommended for larger RAN or CN installations. For small networks +and lab installations the classic method with one MGW per BSC offers sufficient +performance. + +=== MGW pool VTY configuration + +In {program-name} the MGW is controlled via an MGCP-Client. The VTY commands to +configure the MGCP-Client are part of the several 'mgw' nodes, one per +MGCP-Client to set up. + +To setup an MGW pool, the user must first install multiple OsmoMGW instances, so +that they won’t interfere with each other. This can be done using different +local host IP addresses or different ports. When OsmoMGW is installed from +packages, the systemd configuration may also require adjustment. + +By default, MGCP-Client will use whatever source IP address is resolved by the +kernel routing subsystem, and will also ask the kernel to pick a free UDP port. + +Example configuration with two MGCP-Client instances in a pool: +---- + mgw 0 + description media-gw-0 <2> + remote-ip 127.0.0.1 + remote-port 2432 + local-ip 127.0.0.1 + local-port 2431 + endpoint-domain mgw0 <1> + mgw 1 + description media-gw-1 <2> + remote-ip 127.0.0.1 + remote-port 2430 + local-ip 127.0.0.1 + local-port 2429 + endpoint-domain mgw1 <1> +---- + +<1> When working with multiple MGW / MGCP-Client instances, the domain name for +each MGW should be different. Otherwise it won't be possible to distinguish the +endpoint names in the log. It should also be noted that the domain name must +match the configuration of the related OsmoMGW instance. + +<2> It is also possible to assign a descriptive name to each MGW instance. The +MGCP client specific log lines will then use this name as logging context. If +no description is set, the domain name will be used. + +=== MGW pool management + +The MNGW pool is fully runtime-manageable. The only limitation +is that an MGCP-Client can not be restarted or removed as long as it is serving +calls (see also: <<mgw_pooling_blocking>>). + +==== MGW pool status + +The VTY implements a 'show mgw-pool' command that lists the currently configured +MGW pool members, their status and call utilization. The following snippet shows +an output example run on OsmoBSC, but it should be also available on other +applications supporting the MGW pooling VTY featues: + +---- +OsmoBSC> show mgw-pool +% MGW-Pool: +% MGW 0:media-gw-0 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 1 +% MGW 1:media-gw-1 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 0 +---- + +==== Adding an MGW / MGCP-Client to the MGW pool + +To add a new MGCP-Client to the pool, the 'mgw' node is used. Like with the +'bts' or the 'msc' node a reference number is used that usually starts at 0. +However it is still possible to assign any number from 0-255. The enumeration +also may contain gaps. The following snippet shows an output example run on +OsmoBSC, but it should be also available on other applications supporting the +MGW pooling VTY featues: + +---- +OsmoBSC> enable +OsmoBSC# configure terminal +OsmoBSC(config)# network +OsmoBSC(config-net)# mgw 2 +OsmoBSC(config-mgw)# ? + local-ip local bind to connect to MGW from + local-port local port to connect to MGW from + remote-ip remote IP address to reach the MGW at + remote-port remote port to reach the MGW at + endpoint-domain Set the domain name to send in MGCP messages, e.g. the part 'foo' in 'rtpbridge/*@foo'. + reset-endpoint Add an endpoint name that should be reset (DLCX) on connect to the reset-endpoint list,e.g. 'rtpbridge/*' +---- + +The newly added MGW will immediately appear in the mgw-pool list but it won't +be used until its configuration finished by reconnecting it. + +---- +% MGW-Pool: +% MGW 0:media-gw-0 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 2 +% MGW 1:media-gw-1 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 3 +% MGW 2:mgw <1> +% mgcp-client: disconnected +% service: unblocked +% ongoing calls: 0 +---- + +<1> In this example a description is not set yet, so the domain name ("mgw") +is displayed. + +==== Reconnecting an MGW / MGCP-Client + +It may become necessary to reconnect an MGCP-Client. This is the case when the +VTY configuration was changed at runtime. In order to make the changes effective +the MGW configuration must be reloaded by reconnecting the MGW connection. Also +newly created MGW instances require a reconnect once their configuration is +done. + +To reconnect an MGCP-Client use the 'reconnect' VTY command: +---- +OsmoBSC# mgw 2 reconnect +---- + +The mgcp-client status should immediately change to 'connected'. The MGW is now +ready to be used for new calls. + +---- +OsmoBSC# show mgw-pool +% MGW-Pool: +% MGW 0:media-gw-0 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 2 +% MGW 1:media-gw-1 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 3 +% MGW 2:mgw +% mgcp-client: connected +% service: unblocked +% ongoing calls: 0 +---- + +It should be noted that MGCP a protocol is used via UDP, the connect only +happens locally to forward the UDP datagrams properly. Also (unless a reset +endpoint is configured like in the example config above) there will be no +immediate interaction with the MGW. However, the log should at least confirm +the the connect worked and the MGCP client has been created successfully. + +---- +Mon Aug 2 17:15:00 2021 DLMGCP mgcp_client.c:788 MGCP client: using endpoint domain '@mgw' +Mon Aug 2 17:15:00 2021 DLMGCP mgcp_client.c:908 MGCP GW connection: r=127.0.0.1:2427<->l=127.0.0.1:2727 +---- + +It is strongly advised to check the activity on the related MGW and to follow +the log in order to see that the communication between {program-name} and the MGW is +working correctly. + +[[mgw_pooling_blocking]] +==== Blocking an MGW / MGCP-Client + +If it becomes apparent that an MGCP-Client must be restarted or removed from +the config (maintenance) the operator can put that MGCP-Client into a blocked +mode. A blocked MGCP-Client will still serve the ongoing calls but it will not +be picked for the assignment of new calls. + +To block an MGCP-Client use the 'block' VTY command: +---- +OsmoBSC# mgw 2 block +OsmoBSC# show mgw-pool +% MGW-Pool: +% MGW 0:media-gw-0 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 11 +% MGW 1:media-gw-1 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 12 +% MGW 2:mgw +% mgcp-client: connected +% service: blocked +% ongoing calls: 10 +---- + +When the number of ongoing calls has tapered off, the MGW / MGCP-Client can be +restarted or removed if necessary. + +---- +OsmoBSC# show mgw-pool +% MGW-Pool: +% MGW 0:media-gw-0 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 15 +% MGW 1:media-gw-1 +% mgcp-client: connected +% service: unblocked +% ongoing calls: 14 +% MGW 2:mgw +% mgcp-client: connected +% service: blocked +% ongoing calls: 0 +---- + +If the blockade should be reverted, the 'unblock' VTY command can be used in +the same way to remove the blockade. (Reconnecting will not remove the +blockade.) + +==== Removing an MGW / MGCP-Client + +An MGCP-Client is removed from the pool using the 'no mgw' command from the +configure terminal. The MGCP-Client instance will automatically be terminated +and the related resources are freed. The only requirement is that there are no +ongoing calls on the selected instance. + +---- +OsmoBSC# configure terminal +OsmoBSC(config)# network +OsmoBSC(config-net)# no mgw 2 +---- -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29819 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b Gerrit-Change-Number: 29819 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-MessageType: merged

2 years, 8 months

1
0
0 0

Change in osmo-gsm-manuals[master]: mgwpool.adoc: Fix typo

by pespin

pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29824 ) Change subject: mgwpool.adoc: Fix typo ...................................................................... mgwpool.adoc: Fix typo Change-Id: I10370b508caf06b08505933b306d79825674a8fa --- M common/chapters/mgwpool.adoc 1 file changed, 1 insertion(+), 1 deletion(-) Approvals: Jenkins Builder: Verified osmith: Looks good to me, approved pespin: Looks good to me, but someone else must approve diff --git a/common/chapters/mgwpool.adoc b/common/chapters/mgwpool.adoc index c429159..01bf5ea 100644 --- a/common/chapters/mgwpool.adoc +++ b/common/chapters/mgwpool.adoc @@ -57,7 +57,7 @@ === MGW pool management -The MNGW pool is fully runtime-manageable. The only limitation +The MGW pool is fully runtime-manageable. The only limitation is that an MGCP-Client can not be restarted or removed as long as it is serving calls (see also: <<mgw_pooling_blocking>>). -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29824 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: I10370b508caf06b08505933b306d79825674a8fa Gerrit-Change-Number: 29824 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-MessageType: merged

2 years, 8 months

1
0
0 0

Change in osmo-gsm-manuals[master]: mgwpool.adoc: Fix typo

by pespin

pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29824 ) Change subject: mgwpool.adoc: Fix typo ...................................................................... Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29824 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: I10370b508caf06b08505933b306d79825674a8fa Gerrit-Change-Number: 29824 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 20 Oct 2022 15:04:40 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 8 months

1
0
0 0

Change in osmo-gsm-manuals[master]: Copy mgwpool.adoc from osmo-bsc.git

by pespin

Attention is currently required from: osmith, dexter. pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29819 ) Change subject: Copy mgwpool.adoc from osmo-bsc.git ...................................................................... Patch Set 1: Code-Review+2 (1 comment) File common/chapters/mgwpool.adoc: https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29819/comment/9a8d030f_0411… PS1, Line 14: BSC > {program-name}? I'll fix it as a followup commit. -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29819 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b Gerrit-Change-Number: 29819 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-Comment-Date: Thu, 20 Oct 2022 15:04:34 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: osmith <osmith(a)sysmocom.de> Gerrit-MessageType: comment

2 years, 8 months

1
0
0 0

Change in osmo-bsc[master]: doc: Generalize mgwpool.adoc and move BSC-specific sections to runnni...

by pespin

pespin has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/29818 ) Change subject: doc: Generalize mgwpool.adoc and move BSC-specific sections to runnning.adoc ...................................................................... doc: Generalize mgwpool.adoc and move BSC-specific sections to runnning.adoc This is a preparation commit before moving mgwpool.adoc to a share place (osmo-gsm-manuals.adoc) so that other apps like osmo-msc and osmo-hnbgw can also include this section. Related: SYS#5987 Change-Id: Id0d292506e8b2a888c8d7a682a38db80e9d0933a --- M doc/manuals/chapters/mgwpool.adoc M doc/manuals/chapters/running.adoc 2 files changed, 79 insertions(+), 82 deletions(-) Approvals: Jenkins Builder: Verified daniel: Looks good to me, but someone else must approve osmith: Looks good to me, approved diff --git a/doc/manuals/chapters/mgwpool.adoc b/doc/manuals/chapters/mgwpool.adoc index 8904bad..c429159 100644 --- a/doc/manuals/chapters/mgwpool.adoc +++ b/doc/manuals/chapters/mgwpool.adoc @@ -1,7 +1,7 @@ [[mgw_pooling]] == MGW Pooling -OsmoBSC is able to use a pool of media gateway (MGW) instances since mid 2021. +{program-name} is able to use a pool of media gateway (MGW) instances. The aim of MGW pooling is to evenly distribute the RTP voice stream load across multiple MGW instances. This can help to scale out over multiple VMs or physical machines. Until osmo-mgw includes multithreading support, it may also be used to @@ -10,39 +10,23 @@ The load distribution is managed in such a way that when a new call is placed, the pool will automatically assign the call to the MGW with the lowest load. -MGW pooling is recommended for larger RAN installations. For small networks and -lab installations the classic method with one MGW per BSC offers sufficient +MGW pooling is recommended for larger RAN or CN installations. For small networks +and lab installations the classic method with one MGW per BSC offers sufficient performance. -=== VTY configuration +=== MGW pool VTY configuration -In OsmoBSC the MGW is controlled via an MGCP-Client. The VTY commands to -configure the MGCP-Client are part of the 'msc' node due to historical reasons. -Unfortunately this concept does not allow to configure multiple MGCP-Client -instances as required by MGW pooling. In order to support MGW pooling a new -'mgw' node has been added under the 'network' node. - -=== Existing configuration files - -Existing OsmoBSC configuration files will continue to work, but as soon as an -MGW pool is configured the 'mgw' settings under the 'msc' node will be ignored. - -Example configuration with only one MGCP-Client under the 'msc' node: ----- -msc 0 - mgw remote-ip 127.0.0.1 - mgw remote-port 2428 ----- - -=== MGW pool configuration +In {program-name} the MGW is controlled via an MGCP-Client. The VTY commands to +configure the MGCP-Client are part of the several 'mgw' nodes, one per +MGCP-Client to set up. To setup an MGW pool, the user must first install multiple OsmoMGW instances, so that they won’t interfere with each other. This can be done using different local host IP addresses or different ports. When OsmoMGW is installed from packages, the systemd configuration may also require adjustment. -The VTY settings under the 'mgw' node works the same way as the VTY settings for -the MGW under the 'msc' node. +By default, MGCP-Client will use whatever source IP address is resolved by the +kernel routing subsystem, and will also ask the kernel to pick a free UDP port. Example configuration with two MGCP-Client instances in a pool: ---- @@ -73,15 +57,16 @@ === MGW pool management -While it was not possible to change the MGCP-Client configuration under the -“msc” node at runtime, the pool is fully runtime-manageable. The only limitation +The MNGW pool is fully runtime-manageable. The only limitation is that an MGCP-Client can not be restarted or removed as long as it is serving calls (see also: <<mgw_pooling_blocking>>). ==== MGW pool status The VTY implements a 'show mgw-pool' command that lists the currently configured -MGW pool members, their status and call utilization. +MGW pool members, their status and call utilization. The following snippet shows +an output example run on OsmoBSC, but it should be also available on other +applications supporting the MGW pooling VTY featues: ---- OsmoBSC> show mgw-pool @@ -101,14 +86,16 @@ To add a new MGCP-Client to the pool, the 'mgw' node is used. Like with the 'bts' or the 'msc' node a reference number is used that usually starts at 0. However it is still possible to assign any number from 0-255. The enumeration -also may contain gaps. +also may contain gaps. The following snippet shows an output example run on +OsmoBSC, but it should be also available on other applications supporting the +MGW pooling VTY featues: ---- OsmoBSC> enable OsmoBSC# configure terminal OsmoBSC(config)# network OsmoBSC(config-net)# mgw 2 -OsmoBSC(config-mgw)# mgw +OsmoBSC(config-mgw)# ? local-ip local bind to connect to MGW from local-port local port to connect to MGW from remote-ip remote IP address to reach the MGW at @@ -184,7 +171,7 @@ ---- It is strongly advised to check the activity on the related MGW and to follow -the log in order to see that the communication between OsmoBSC and the MGW is +the log in order to see that the communication between {program-name} and the MGW is working correctly. [[mgw_pooling_blocking]] @@ -250,52 +237,3 @@ OsmoBSC(config)# network OsmoBSC(config-net)# no mgw 2 ---- - -==== Pinning a BTS to a specific MGW - -It is sometimes desirable to assign a specific MGW to a given BTS, so that all -calls where the BTS is involved use the assigned MGW with a higher precedence if -possible. - -This is specially important if the BTS is configured to serve calls using Osmux -instead of RTP. Osmux features trunking optimizations, which allow transmission -of audio payload from different concurrent calls inside the same underlaying UDP -packet, hence reducing the total required throughput and saving costs on the -required link. - -In order for Osmux trunking optimization to work, the source and destination IP -address of uderlaying UDP packet must be of course the same for all the calls -involved. That essentially boils down to having all the concurrent calls of the -BTS be connected to the same MGW so that they can be trunked over the same UDP -connection. - -The pinning to a specific MGW can be configured per BTS, and hence it is -configured under the `bts` VTY node: - ----- -OsmoBSC> enable -OsmoBSC# configure terminal -OsmoBSC(config)# network -OsmoBSC(config-net)# bts 1 -OsmoBSC(config-bts)# mgw pool-target 1 <1> -OsmoBSC(config-bts)# exit -OsmoBSC(config-net)# bts 2 -OsmoBSC(config-mgw)# mgw pool-target 7 strict <2> -OsmoBSC(config-net)# bts 3 -OsmoBSC(config-mgw)# no mgw pool-target <3> ----- - -<1> Pin BTS1 to prefer MGW1 (node `mgw 1`). If MGW1 is not configured, -administrateivly blocked or not connected at the time a new call is to be -established, then another MGW from the pool is selected following the usual -procedures. This allows applying pinning in the usual scenario while still -keeping call service ongoing against another MGW if the preferred MGW is not -available at a given time. - -<2> Pin BTS2 to prefer MGW3 (node `mgw 7`). If MGW7 is not configured, -administrateivly blocked or not connected at the time a new call is to be -established, then the MGW assignment will fail and ultimately the call will be -terminated during establishment. - -<3> Apply no pinning at all (default). The MGW with the lowest load is the one -being selected for each new call. diff --git a/doc/manuals/chapters/running.adoc b/doc/manuals/chapters/running.adoc index 930682d..e338dee 100644 --- a/doc/manuals/chapters/running.adoc +++ b/doc/manuals/chapters/running.adoc @@ -144,9 +144,68 @@ DLCX to the media gateway. This helps to clear lingering calls from the media gateway when the OsmoBSC is restarted. -NOTE: OsmoBSC is also able to handle a pool of media gateways for load -distribution. See also <<mgw_pooling>>. +OsmoBSC is also able to handle a pool of media gateways for load +distribution since mid 2021. See also <<mgw_pooling>>. +[NOTE] +==== +Previous versions of OsmoBSC didn't have the 'mgw' VTY node and +hence didn't support the MGW pooling feature. Therefore, historically the MGW +related commands where placed under the `msc` VTY node. The MGW related commands +under the `msc` VTY are still parsed and used but its use is deprecated and +hence discouraged in favour of the new `mgw` node. Writing the config to a file +from within OsmoBSC will automatically convert the config to use the new `mgw` +node. +==== + +===== Pinning a BTS to a specific MGW + +It is sometimes desirable to assign a specific MGW to a given BTS, so that all +calls where the BTS is involved use the assigned MGW with a higher precedence if +possible. + +This is specially important if the BTS is configured to serve calls using Osmux +instead of RTP. Osmux features trunking optimizations, which allow transmission +of audio payload from different concurrent calls inside the same underlaying UDP +packet, hence reducing the total required throughput and saving costs on the +required link. + +In order for Osmux trunking optimization to work, the source and destination IP +address of uderlaying UDP packet must be of course the same for all the calls +involved. That essentially boils down to having all the concurrent calls of the +BTS be connected to the same MGW so that they can be trunked over the same UDP +connection. + +The pinning to a specific MGW can be configured per BTS, and hence it is +configured under the `bts` VTY node: + +---- +OsmoBSC> enable +OsmoBSC# configure terminal +OsmoBSC(config)# network +OsmoBSC(config-net)# bts 1 +OsmoBSC(config-bts)# mgw pool-target 1 <1> +OsmoBSC(config-bts)# exit +OsmoBSC(config-net)# bts 2 +OsmoBSC(config-mgw)# mgw pool-target 7 strict <2> +OsmoBSC(config-net)# bts 3 +OsmoBSC(config-mgw)# no mgw pool-target <3> +---- + +<1> Pin BTS1 to prefer MGW1 (node `mgw 1`). If MGW1 is not configured, +administrateivly blocked or not connected at the time a new call is to be +established, then another MGW from the pool is selected following the usual +procedures. This allows applying pinning in the usual scenario while still +keeping call service ongoing against another MGW if the preferred MGW is not +available at a given time. + +<2> Pin BTS2 to prefer MGW3 (node `mgw 7`). If MGW7 is not configured, +administrateivly blocked or not connected at the time a new call is to be +established, then the MGW assignment will fail and ultimately the call will be +terminated during establishment. + +<3> Apply no pinning at all (default). The MGW with the lowest load is the one +being selected for each new call. ==== Configure Lb to connect to an SMLC -- To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/29818 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Change-Id: Id0d292506e8b2a888c8d7a682a38db80e9d0933a Gerrit-Change-Number: 29818 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-MessageType: merged

2 years, 8 months

1
0
0 0

Change in osmo-msc[master]: doc: Include mgwpool.adoc from osmo-gsm-manuals

by osmith

Attention is currently required from: pespin, dexter. osmith has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/29821 ) Change subject: doc: Include mgwpool.adoc from osmo-gsm-manuals ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/29821 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-msc Gerrit-Branch: master Gerrit-Change-Id: I9d8116a74a63591599c4cbafa60f9a313e6ab19c Gerrit-Change-Number: 29821 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-Comment-Date: Thu, 20 Oct 2022 15:03:45 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment

2 years, 8 months

1
0
0 0

Change in osmo-hnbgw[master]: Introduce support for libosmo-mgcp-client MGW pooling

by pespin

Attention is currently required from: osmith, laforge, fixeria, dexter. Hello osmith, Jenkins Builder, fixeria, daniel, dexter, I'd like you to reexamine a change. Please visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/29806 to look at the new patch set (#3). Change subject: Introduce support for libosmo-mgcp-client MGW pooling ...................................................................... Introduce support for libosmo-mgcp-client MGW pooling Large RAN installations may benefit from distributing the RTP voice stream load over multiple media gateways. libosmo-mgcp-client supports MGW pooling since version 1.8.0 (more than one year ago). OsmoBSC has already been making use of it since then (see osmo-bsc.git 8d22e6870637ed6d392a8a77aeaebc51b23a8a50); lets use this feature in osmo-hngw too. This commit is also part of a series of patches cleaning up libosmo-mgcp-client and slowly getting rid of the old non-mgw-pooled VTY configuration, in order to keep only 1 way to configure libosmo-mgcp-client through VTY. Related: SYS#5091 Related: SYS#5987 Change-Id: I371dc773b58788ee21037dc25d77f556c89c6b61 --- M doc/examples/osmo-hnbgw/osmo-hnbgw-pfcp.cfg M doc/examples/osmo-hnbgw/osmo-hnbgw.cfg M doc/manuals/chapters/running.adoc M include/osmocom/hnbgw/hnbgw.h M include/osmocom/hnbgw/vty.h M src/osmo-hnbgw/hnbgw.c M src/osmo-hnbgw/hnbgw_vty.c M src/osmo-hnbgw/mgw_fsm.c M tests/ranap_rab_ass/Makefile.am 9 files changed, 82 insertions(+), 37 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-hnbgw refs/changes/06/29806/3 -- To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/29806 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hnbgw Gerrit-Branch: master Gerrit-Change-Id: I371dc773b58788ee21037dc25d77f556c89c6b61 Gerrit-Change-Number: 29806 Gerrit-PatchSet: 3 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: daniel <dwillmann(a)sysmocom.de> Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de> Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Attention: dexter <pmaier(a)sysmocom.de> Gerrit-MessageType: newpatchset

2 years, 8 months

1
0
0 0

2025

2024

2023

2022

gerrit-log October 2022