Skip to content

Update doc to correspond to the correct make targets #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 29, 2025
+3 −3
Merged

Update doc to correspond to the correct make targets #52

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion onramp/ref.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,7 +213,7 @@ Quick Start Blueprint.
- Install 5G Core workload; includes bridges for networking.
* - `aether-5gc-uninstall`
- Uninstall 5G Core workload; includes bridges for networking.
* - `aether-resetcore`
* - `aether-5gc-reset`
- Delete and reinstall 5G Core workload; leaves network bridges untouched.
* - `aether-gnbsim-install`
- Install gNBsim containers.
Expand Down
4 changes: 2 additions & 2 deletions onramp/start.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -336,7 +336,7 @@ state, a reset usually corrects the problem. Type:

.. code-block::

make aether-resetcore
make aether-5gc-reset

Once running, you will recognize pods that correspond to many of the
microservices discussed is `Chapter 5
Expand Down Expand Up @@ -427,7 +427,7 @@ of which has been saved in a timestamped file:

If ``summary.log`` reports ``UEs Passed: 0 , UEs Failed: 5`` then it
may be the case that SD-Core did not come up cleanly. Type
``make aether-resetcore``, and after verifying all pods are running
``make aether-5gc-reset``, and after verifying all pods are running
with ``kubectl``, run gNBsim again.

Another possibility is that you have multiple SD-Cores running in
Expand Down