Change in osmo-mgw[master]: manual: Include QoS chapter and add osmo-mgw specific example

laforge gerrit-no-reply at
Thu Apr 29 19:49:35 UTC 2021

laforge has submitted this change. ( )

Change subject: manual: Include QoS chapter and add osmo-mgw specific example

manual: Include QoS chapter and add osmo-mgw specific example

Change-Id: I46f632f52a86a50242689a0132a7a7cb2a8feb12
Depends: osmo-gsm-manuals.git Id344c29eda2a9b3e36376302b425e9db1f6c0f28
A doc/manuals/chapters/qos-example.adoc
M doc/manuals/osmomgw-usermanual.adoc
2 files changed, 44 insertions(+), 0 deletions(-)

  laforge: Looks good to me, approved
  Jenkins Builder: Verified

diff --git a/doc/manuals/chapters/qos-example.adoc b/doc/manuals/chapters/qos-example.adoc
new file mode 100644
index 0000000..deb3d86
--- /dev/null
+++ b/doc/manuals/chapters/qos-example.adoc
@@ -0,0 +1,42 @@
+==== Full example of QoS for osmo-mgw
+In the below example we will show the full set of configuration required
+for both DSCP and PCP differentiation of RTP traffic by osmo-mgw.
+What we want to achieve in this example is the following configuration:
+.DSCP and PCP assignments for osmo-mgw Abis downlink traffic in this example
+|Traffic      |DSCP|PCP
+|RTP    |  46|  6
+. configure the osmo-mgw program to set the DSCP value
+. configure an egrees QoS map to map from priority to PCP
+.Example Step 1: add related VTY configuration to `osmo-mgw.cfg`
+ rtp ip-dscp 46
+ rtp socket-priority 6
+.Example Step 2: egress QoS map to map from socket priority to PCP values
+$ sudo ip link set dev eth0.9<1> type vlan egress-qos-map 0:0 5:5 6:6 7:7 <2>
+<1> make sure to specify your specific VLAN interface name here instead of `eth0.9`.
+<2> create a egress QoS map that maps the priority value 1:1 to the PCP. We also include the
+    mapping 5:5 and 7:7 from the osmo-bsc example (see <<userman-osmobsc>>) here.
+NOTE:: The settings of the `ip` command are volatile and only active until
+the next reboot (or the network device or VLAN is removed).  Please refer to
+the documentation of your specific Linux distribution in order to find out how
+to make such settings persistent by means of an `ifup` hook whenever the interface
+comes up.  For CentOS/RHEL 8 this can e.g. be achieved by means of an `/sbin/ifup-local
+script` (when using `network-scripts` and not NetworkManager).  For Debian or Ubuntu,
+this typically involves adding `up` lines to `/etc/network/interfaces` or a `/etc/network/if-up.d`
diff --git a/doc/manuals/osmomgw-usermanual.adoc b/doc/manuals/osmomgw-usermanual.adoc
index c4660f5..7ebc2db 100644
--- a/doc/manuals/osmomgw-usermanual.adoc
+++ b/doc/manuals/osmomgw-usermanual.adoc
@@ -24,6 +24,8 @@

To view, visit
To unsubscribe, or for help writing mail filters, visit

Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Change-Id: I46f632f52a86a50242689a0132a7a7cb2a8feb12
Gerrit-Change-Number: 23967
Gerrit-PatchSet: 3
Gerrit-Owner: laforge <laforge at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier at>
Gerrit-Reviewer: fixeria <vyanitskiy at>
Gerrit-Reviewer: laforge <laforge at>
Gerrit-Reviewer: pespin <pespin at>
Gerrit-MessageType: merged
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list