@@ -849,18 +849,18 @@ To deploy the srsRAN blueprint in simulation mode, run the following:
849
849
$ make srsran-gnb-install
850
850
$ make srsran-uesim-start
851
851
852
- Multihop gNB's
852
+ Multihop gNBs
853
853
~~~~~~~~~~~~~~~~~~~~~~
854
854
855
- By default OnRamp uses isolated networks for the N3(ex: 192.168.252.x) and
856
- N6(ex: 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(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.
858
858
859
859
In order to support such deployment OnRamp provides an option to configure
860
860
N3 IP from the same subnet as DATA_IFACE. It can be enabled by setting
861
861
``core.upf.multihop_gnb: true ``
862
862
863
- For ex, lets say the DATA_IFACE subnet is 10.21.61.0/24 and gNB subnet
863
+ For example, let's say the DATA_IFACE subnet is 10.21.61.0/24 and gNB subnet
864
864
is 10.202.1.0/24. Configure the parameters as follows,
865
865
866
866
.. code-block ::
@@ -877,9 +877,9 @@ is 10.202.1.0/24. Configure the parameters as follows,
877
877
core: "192.168.250.3"
878
878
ue_ip_pool: "172.250.0.0/16"
879
879
880
- In case if we need to connect multiple gNB's (gNB2 subnet: 10.203.1.0/24)
880
+ In case we need to connect multiple gNBs (gNB2 subnet: 10.203.1.0/24)
881
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) ``:
882
+ in ``deps/5gc/roles/core/templates/sdcore-5g-values.yaml `` ``(if core.upf.mode: af_packet) ``, or
883
883
in ``deps/5gc/roles/core/templates/sdcore-5g-sriov-values.yaml `` ``(if core.upf.mode: dpdk) ``:
884
884
885
885
.. code-block ::
0 commit comments