Skip to content

Commit 4e5c92c

Browse files
authored
Merge pull request #43 from opennetworkinglab/maintenance
wordsmithing
2 parents 9560ed2 + f335ecf commit 4e5c92c

File tree

1 file changed

+17
-13
lines changed

1 file changed

+17
-13
lines changed

onramp/blueprints.rst

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -852,16 +852,18 @@ To deploy the srsRAN blueprint in simulation mode, run the following:
852852
Multihop gNBs
853853
~~~~~~~~~~~~~~~~~~~~~~
854854

855-
By default OnRamp uses isolated networks for the N3(i.e., 192.168.252.x) and
856-
N6(i.e., 192.168.250.x) interfaces. This prevents gNB, which is on different
857-
subnet and located multiple hops away, connecting to the UPF on N3 interface.
855+
By default OnRamp uses isolated networks for the N3 (e.g.,
856+
192.168.252.x) and N6 (e.g., 192.168.250.x) interfaces. This prevents
857+
gNBs on different subnets or located multiple hops away from
858+
connecting to the UPF on the N3 interface.
858859

859-
In order to support such deployment OnRamp provides an option to configure
860-
N3 IP from the same subnet as DATA_IFACE. It can be enabled by setting
861-
``core.upf.multihop_gnb: true``
860+
In order to support such deployments, OnRamp provides an option to
861+
configure N3 from the same subnet as ``core.data_iface``. It can be
862+
enabled by setting setting ``core.upf.multihop_gnb`` to ``true``.
862863

863-
For example, let's say the DATA_IFACE subnet is 10.21.61.0/24 and gNB subnet
864-
is 10.202.1.0/24. Configure the parameters as follows,
864+
For example, suppose ``core.data_iface`` corresponds to subnet
865+
10.21.61.0/24 and the gNB is on subnet 10.202.1.0/24. Configure the
866+
parameters as follows:
865867

866868
.. code-block::
867869
@@ -873,14 +875,16 @@ is 10.202.1.0/24. Configure the parameters as follows,
873875
multihop_gnb: true
874876
default_upf:
875877
ip:
876-
access: "10.21.61.12" # when multihop_gnb set to true, make sure to assign IP from same subnet of data_iface
878+
access: "10.21.61.12" # same subnet as data_iface when multihop_gnb is true
877879
core: "192.168.250.3"
878880
ue_ip_pool: "172.250.0.0/16"
879881
880-
In case we need to connect multiple gNBs (gNB2 subnet: 10.203.1.0/24)
881-
from different subnet then add routes as follows
882-
in ``deps/5gc/roles/core/templates/sdcore-5g-values.yaml`` ``(if core.upf.mode: af_packet)``, or
883-
in ``deps/5gc/roles/core/templates/sdcore-5g-sriov-values.yaml`` ``(if core.upf.mode: dpdk)``:
882+
To connect multiple gNBs on different subnets, you must modify
883+
``deps/5gc/roles/core/templates/sdcore-5g-values.yaml`` (if
884+
``core.upf.mode: af_packet``) or
885+
``deps/5gc/roles/core/templates/sdcore-5g-sriov-values.yaml`` (if
886+
``core.upf.mode: dpdk``) to add the necessary routes. For example, if
887+
a second gNB is on 10.203.1.0/24, then add the route as follows:
884888

885889
.. code-block::
886890

0 commit comments

Comments
 (0)