In the dense deployment profile I should be able to send traffic on the DL
by running a ping on the core network server. For this I need the
connection manager logs for the UE, where are those located.
I think you should find those in /var/log/
.
Also it is said I can use the TUI for a UE by running /var/tmp/ue_app.py.
but no such file exists.
Hmm.. I’ll watch for your next mobile-endpoints experiment and have a look when one of the buses is ready.
-Dustin
--
You received this message because you are subscribed to the Google Groups "Powder Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to powder-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/powder-users/7514c0e4-1889-489d-bb47-144ad0f24993n%40googlegroups.com.
Hi Adithya,
I have been searching inside /var/log/ but cant seem to find anything
related to the IP address or connection manager, this is on the server for
the campus shuttle UE. I have attached a picture of the /var/log/ directory
of one such UE.
It seems that the deploy script failed on a couple of the buses (bus-6364 being one) for some reason, so the connection manager service was not running… I’ve fixed those up. The logs for the connection manager are now showing up.
I have a doubt, do you think the UEs might not be connecting to the gNB as
I am running my own modified srsRAN which is not a system service unlike
the provide srsRAN which is a system service.
If you are running your own version, I’m pretty sure you aren’t using our patch that enables the use of the RF front ends at the dense sites. Please have a look at the profile repo and make adjustments to include this patch, else the UEs will never see the gNodeB.
Finally, the ue_app.py tool currently only gets installed along with other test tools when an orchestrator node is provided as a parameter in the mobile-endpoints profile… in your next experiment, just provide a random string and I think the ue_app.py tool will be installed. I think I will update the profile to include this script regardless of whether or not an orchestrator node is used when I can.
-Dustin
To view this discussion visit https://groups.google.com/d/msgid/powder-users/4d52cd87-4cd1-4848-91ae-2540e5b187f3n%40googlegroups.com.
OK. Since you are not using the gnb service, can you please share the command you are using to start the gnb? I will have a look tomorrow and see if there is an obvious issue.
-Dustin
To view this discussion visit https://groups.google.com/d/msgid/powder-users/68d19c73-67af-4cad-b38e-fa0be05a7883n%40googlegroups.com.
And the path to your srsRAN build? or are you using the build put in place by the profile?
To view this discussion visit https://groups.google.com/d/msgid/powder-users/54c5372d-ae50-40fe-82d6-f996e6f064f4n%40googlegroups.com.
I see a few issues with your config:
Let’s go through everything during your office hours session tomorrow before you start transmitting again, and see if we can get it working during the session. In anticipation of that, please instantiate another mobile-endpoints experiment prior to the office hours session.
-Dustin
To view this discussion visit https://groups.google.com/d/msgid/powder-users/967c55b2-6014-465d-95bf-1c9d98eb19b6n%40googlegroups.com.