added troubleshooting hints
Change-Id: I3c2674cfa215a935eebda919331deee7963e2019
diff --git a/onramp/gnb.rst b/onramp/gnb.rst
index 4819727..07e4ca2 100644
--- a/onramp/gnb.rst
+++ b/onramp/gnb.rst
@@ -62,6 +62,13 @@
* OPc: ``69d5c2eb2e2e624750541d3bbc692ba5``
* Key: ``000102030405060708090a0b0c0d0e0f``
+Note that the actual config files distributed with OnRamp have IMSIs
+constructed using PLMN id ``00101``. Both sets of examples are taken
+from working deployments, so either should work as a model you can
+emulate in your deployment, although it is certainly easiest to start
+with the existing code. So they are easy to distinguish, note that the
+IMSIs used in emulations are constructed using PLMN id ``20893``.
+
Insert the SIM cards into whatever devices you plan to connect to
Aether. Be aware that not all phones support the CBRS frequency bands
that Aether uses. Aether is known to work with recent iPhones (11 and
diff --git a/onramp/start.rst b/onramp/start.rst
index 11de367..04bdb2f 100644
--- a/onramp/start.rst
+++ b/onramp/start.rst
@@ -184,6 +184,14 @@
these three values as a running example throughout the guide, as a
placeholder for your local details.
+.. admonition:: Troubleshooting Hint
+
+ Due to a limitation in gNBsim (the RAN emulator introduced later in
+ this section), it is necessary for your server to be configured with
+ IPv6 enabled (as the ``inet6`` line in the example output indicates
+ is the case for interface ``ens18``). If IPv6 is not enabled, the
+ emulated RAN will not successfully connect to the AMF.
+
Note that ``vars/main.yml`` and ``hosts.ini`` are the only two files
you need to modify for now, but there are additional config files that
you may want to modify as we move beyond the Quick Start deployment.
@@ -326,7 +334,7 @@
If you are interested in seeing the details about how SD-Core is
configured, look at
``deps/5gc/roles/core/templates/radio-5g-values.yaml``. This is an
-example of a *values override* file that Helm passes to along to
+example of a *values override* file that Helm passes along to
Kubernetes when launching the service. Most of the default settings
will remain unchanged, with the main exception being the
``subscribers`` block of the ``omec-sub-provision`` section. This
@@ -385,6 +393,15 @@
2023-08-09T19:57:05Z [INFO][GNBSIM][GNodeB][ControlPlaneTransport] Connected to AMF, AMF IP: 10.76.28.113 AMF Port: 38412
...
+.. admonition:: Troubleshooting Hint
+
+ If ``summary.log`` is empty, it means the emulation did not run due
+ to a configuration error. To debug the problem, open a bash shell on
+ the gNBsim container (as shown in the preceding example), and look
+ at ``gnbsim.log``. Output that includes ``failed to connect amf``
+ and ``err: address family not supported by protocol`` indicates that
+ your server does not have IPv6 enabled.
+
If you are interested in the config file that controls the test,
including the option of enabling other profiles, take a look at
``deps/gnbsim/config/gnbsim-default.yaml``. We return to the issue of