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

laforge gerrit-no-reply at
Wed Apr 28 10:16:36 UTC 2021

laforge has uploaded this change for review. ( )

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

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

Change-Id: I4d409b55861f05ba229dc5cb97f99370356e3dbd
Requires: osmo-gsm-manuals.git Id344c29eda2a9b3e36376302b425e9db1f6c0f28
A doc/manuals/chapters/qos-example.adoc
M doc/manuals/osmopcu-usermanual.adoc
2 files changed, 49 insertions(+), 0 deletions(-)

  git pull ssh:// refs/changes/29/23929/1

diff --git a/doc/manuals/chapters/qos-example.adoc b/doc/manuals/chapters/qos-example.adoc
new file mode 100644
index 0000000..dcbba2a
--- /dev/null
+++ b/doc/manuals/chapters/qos-example.adoc
@@ -0,0 +1,47 @@
+==== Full example of QoS for osmo-pcu uplink QoS
+In the below example we will show the full set of configuration required
+for both DSCP and PCP differentiation of uplink Gb traffic by osmo-pcu.
+What we want to achieve in this example is the following configuration:
+.DSCP and PCP assignments for osmo-bts uplink traffic in this example
+|Traffic      |DSCP|PCP
+|Gb (NS)      |  10|  1
+. configure the osmocom program to set the DSCP value
+ * osmo-pcu.cfg: `dscp 10` in `udp bind` vty node
+. use a packet filter rule to set the priority based on DSCP
+. configure an egrees QoS map to map from priority to PCP
+.Example Step 2: iptables rules to map from DSCP values to priority values
+$ sudo iptables -t mangle -I OUTPUT -m dscp --dscp 10 -j CLASSIFY --set-class 1
+NOTE:: The above-mentioned `iptables` commands only insert the rules
+into the Linux kernel.  They are volatile and will be gone on next boot.
+It is up to you to ensure they are re-installed at every boot, e.g. by
+some kind of init script, systemd unit file, or packet filter rule
+management software like firewalld, ufw, ...
+.Example Step 3: egress QoS map to map from DSCP values to priority values
+$ sudo ip link set dev eth0.9<1> type vlan egress-qos-map 0:0 1:1 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 mappings for 5, 6, and 7 from the osmo-bts example here (see
+    <<userman-osmobts>>).
+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/osmopcu-usermanual.adoc b/doc/manuals/osmopcu-usermanual.adoc
index e202e33..0fae72a 100644
--- a/doc/manuals/osmopcu-usermanual.adoc
+++ b/doc/manuals/osmopcu-usermanual.adoc
@@ -21,6 +21,8 @@

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

Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I4d409b55861f05ba229dc5cb97f99370356e3dbd
Gerrit-Change-Number: 23929
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge at>
Gerrit-MessageType: newchange
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list