2021-11-05 Demo video release Dawn
A 24min video on how to deploy the near-RT RIC, connect an E2 node (gNB simulator) to it and how to deploy an xApp using the DMS CLI: and . Repeating the steps in the video you can reproduce similar results in your own setup.
A shorter (8min) version of the video above that just show how things generally work:
Comments
there's a short demo on deploying the F release today (2022-05-24). You might want to attend.
Both demos (F and Dawn) use a non-public simulator. There's a public simulator in the repo sim/e2-interface. Subhash & co recently updated the simulator to use E2APv2.0 and provided instructions here:
[2] https://gerrit.o-ran-sc.org/r/c/sim/e2-interface/+/8344/1/e2sim/README.md#100
Also ric-dep has recently been updated and deploying a F-release RIC should be as easy as:
install ubuntu 20.04
cd ric-dep
./install_k8s_and_helm.sh
./install_common_templates_to_helm.sh
./install -f ../RECIPE_EXAMPLE/example_recipe_latest_unstable_with_refs_to_staging.yaml
Note that the yaml in stage 6 to be used for the F release will eventually become "example_recipe_oran_f_release.yaml", but for this to happen we first need to release the F release during June. Until then the "example_recipe...refs_to_staging.yaml" has references to the staging repo (https://nexus3.o-ran-sc.org/#browse/browse:docker.staging). The final one will only have references to the release repo (https://nexus3.o-ran-sc.org/#browse/browse:docker.release).
I haven't tried, but my best guess is that the above 6 steps also work for the D release and E release, Obviously using the recipe...yaml files for these releases.
@Thoralf Czichy Thank you very much..Finally, I connected a gnb to ricplt by deploying E2 Simulator as you mentioned in your previous response.
When I tried "curl -s -X GET http://e2mgr_serviceIP:3800/v1/nodeb/states |jq ." it returned gnb in the "CONNECTED" state.
But unfortunately, after about 30 seconds, it was changed to a "DISCONNECTED" state.
Also, when I restart the pod of E2sim, again it returns to the "CONNECTED" state, but after 30 seconds it goes to "DISCONNECTED" state.
I don't know why this happens and how to prevent it from going to "DISCONNECTED" state.
These images are parts of e2mgr logs:
you can see from the first image that gnb is connected successfully:
and from the below image you can see gnb is disconnected automatically:
Thank you very much.
What's happening right before the disconnect in the logs of E2Term? You might also look at the pcap of the messages exchanged between E2Term and the simulator.
It could be related to the simulator started using multi-homing (many IP addresses). You could double-check that by looking at the PCAP of the SCTP Init (if it includes multiple IP addresses, this is what might cause the issue).
@Thoralf Czichy I apologize for taking so long to respond. You can see captured packets in the below image (taken from wireshark environment and pod IP is found from "kubectl get pods -A -o wide" command and service IP is found from "kubectl get svc -A | grep sctp") :
In the above image:
- New E2Sim pod IP = IP of E2Sim pod after restarting the E2Sim pod
- Previous E2Sim pod IP = IP of E2Sim pod before restarting the E2Sim pod
For E2term Logs, nothing is changed. It contains just rmr messages and I couldn't find any change after restarting the E2Sim pod. I have attached the logs of E2Term to this message.
The installation is on ubuntu server 18.04 LTS;
The Dawn Release is installed;
The used E2Sim repo is: https://github.com/o-ran-sc/sim-e2-interface.git
Thank you very much.
Hello,
I'm trying to implement these videos step by step, but I couldn't pull and run image for gNB simulator.
Is there any way to access this image?
Any help would be appreciated.