Skip to content

Commit eeec1e6

Browse files
committed
tweaked hosts.ini para
Signed-off-by: Larry Peterson <[email protected]>
1 parent c8a3dd6 commit eeec1e6

File tree

2 files changed

+12
-10
lines changed

2 files changed

+12
-10
lines changed

dict.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ GPP
2222
GTP
2323
GbE
2424
GiB
25+
GigE
2526
GitOps
2627
Github
2728
Grafana

onramp/blueprints.rst

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -502,11 +502,11 @@ The blueprint includes the following:
502502
* Inventory file ``hosts.ini`` uses label ``[oai_gnb_nodes]`` to
503503
denote the server(s) that host the gNB and label ``[oai_ue_nodes]``
504504
to denote the server(s) that host the UE. (The latter is necessary
505-
only when running in simulation mode.) One common configuration is
505+
only when running in simulation mode.) The expected configuration is
506506
to run both the gNB and UE on the same server as Kubernetes (where
507-
the 5G Core runs). Another common common configuration is to
508-
co-locate the gNB and UE on one server, with the 5G Core running on
509-
a separate server.
507+
the 5G Core runs). Another possible configuration is to co-locate
508+
the gNB and UE on one server, with the 5G Core running on a separate
509+
server.
510510

511511
* New make targets, ``oai-gnb-install`` and ``oai-gnb-uninstall``, to
512512
be executed along with the standard SD-Core installation (see below).
@@ -596,12 +596,13 @@ To deploy the OAI blueprint with a physical gNB and UE, first
596596
configure the USRP hardware as described in the `USRP Hardware Manual
597597
<https://files.ettus.com/manual/page_usrp_x3x0.html>`__. Of
598598
particular note, you need to select whether the device is to connect
599-
to the Aether Core using its 1G or 10G interface, and make sure the
600-
OAI configuration file (corresponding to ``oai.conf_file``) sets the
601-
``sd_addrs`` variable to match the interface you select. You also need
602-
to make sure the PLMN-related values in the files specified by
603-
``core.values_file`` and ``oai.conf_file`` (along with the SIM cards
604-
you burn) are consistent. Once ready, run the following Make targets:
599+
to the Aether Core using its 1-GigE or 10-GigE interface, and make
600+
sure the OAI configuration file (corresponding to ``oai.conf_file``)
601+
sets the ``sd_addrs`` variable to match the interface you select. You
602+
also need to make sure the PLMN-related values in the files specified
603+
by ``core.values_file`` and ``oai.conf_file`` (along with the SIM
604+
cards you burn) are consistent. Once ready, run the following Make
605+
targets:
605606

606607
.. code-block::
607608

0 commit comments

Comments
 (0)