Skip to content

Commit 4388f04

Browse files
committed
Update doc to correspond to the correct make targets
Signed-off-by: Marcus Hufvudsson <[email protected]>
1 parent 95dee24 commit 4388f04

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

onramp/ref.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ Quick Start Blueprint.
213213
- Install 5G Core workload; includes bridges for networking.
214214
* - `aether-5gc-uninstall`
215215
- Uninstall 5G Core workload; includes bridges for networking.
216-
* - `aether-resetcore`
216+
* - `aether-5gc-reset`
217217
- Delete and reinstall 5G Core workload; leaves network bridges untouched.
218218
* - `aether-gnbsim-install`
219219
- Install gNBsim containers.

onramp/start.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ state, a reset usually corrects the problem. Type:
336336

337337
.. code-block::
338338
339-
make aether-resetcore
339+
make aether-5gc-reset
340340
341341
Once running, you will recognize pods that correspond to many of the
342342
microservices discussed is `Chapter 5
@@ -427,7 +427,7 @@ of which has been saved in a timestamped file:
427427

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

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

0 commit comments

Comments
 (0)