Unknown RAN Function ID #368
Replies: 7 comments 8 replies
-
Hi, thanks for pointing this out. After the last code release, we need to release also the new version of the app note. |
Beta Was this translation helpful? Give feedback.
-
We also had this issue with the latest updates. Also, when we tried running the testbed without flexric with the latest open5gs and srsran_project gnb and srsran_4g ue, connection could not be established. Is this a known issue? |
Beta Was this translation helpful? Give feedback.
-
The problem is still not solved, however I found out, that when using the latest flexric version , at least the RIC does not crash when starting the srsRAN gNB. Follow the installation guide for flexric (I also needed to update swig to v4.1) And then build the project using these flags in the CMAKE command CC=gcc-10 CXX=g++-10 cmake .. -DE2AP_VERSION=E2AP_V3 -DKPM_VERSION=KPM_V3_00
make install After starting the open5GS core from the srsRAN docker and the nearRT-RIC I get this output (not crashing) in the RIC:
This means, now the Functions with SM ID = 2 and 3 are known to the RIC and the srsRAN gNB is able to connect via E2 Interface. Here the output of the gNB: ./gnb -c gnb_zmq.yaml
The PRACH detector will not meet the performance requirements with the configuration {Format 0, ZCZ 0, SCS 1.25kHz, Rx ports 1}.
Lower PHY in executor blocking mode.
--== srsRAN gNB (commit 55c984b55) ==--
Connecting to AMF on 10.53.1.2:38412
Available radio types: zmq.
Connecting to NearRT-RIC on 127.0.0.1:36421
Cell pci=1, bw=10 MHz, dl_arfcn=368500 (n3), dl_freq=1842.5 MHz, dl_ssb_arfcn=367930, ul_freq=1747.5 MHz
==== gNodeB started ===
Type <t> to view trace However, when i start the UE now, i do not get a connection to the gnb via zmq - but this might be related to another issue - i dont know. Maybe this helps some of you guys - looking forward to hear from you, if anyone has the same issue or a solution for getting the UE connected. Update 08.01.2024 - ZMQ workingAfter copying the adjustments on the config files for gNB and UE from thread #350, I am now able to use the setup with zmq. |
Beta Was this translation helpful? Give feedback.
-
I am facing the same issue, and using -DE2AP_VERSION=<e2ap_version> -DKPM_VERSION=<kpm_version> with cmake does not work |
Beta Was this translation helpful? Give feedback.
-
@LukasWehrstein Did you have all tests passed when running ctest? I had a few tests failed, but near-RT RIC was able to connect to gnb. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Please check our updated tutorial, where the above issue was solved by using a newer version of Flexric. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings,
I am new to srsRAN and I am trying to get one of the example experiments from the docs up and running on my Dell Precision 7670 running Ubuntu 22.04. I followed all of the instructions found here: https://docs.srsran.com/projects/project/en/latest/tutorials/source/flexric/source/index.html, and I can start up the Open5gc core and FlexRIC without a problem, with the following output initially on the FlexRIC terminal
lucas@lucas-dell-research:~$ ./flexric/build/examples/ric/nearRT-RIC
Setting the config -c file to /usr/local/etc/flexric/flexric.conf
Setting path -p for the shared libraries to /usr/local/lib/flexric/
[NEAR-RIC]: nearRT-RIC IP Address = 127.0.0.1, PORT = 36421
[NEAR-RIC]: Initializing
[NEAR-RIC]: Loading SM ID = 142 with def = MAC_STATS_V0
[NEAR-RIC]: Loading SM ID = 148 with def = GTP_STATS_V0
[NEAR-RIC]: Loading SM ID = 145 with def = SLICE_STATS_V0
[NEAR-RIC]: Loading SM ID = 144 with def = PDCP_STATS_V0
[NEAR-RIC]: Loading SM ID = 143 with def = RLC_STATS_V0
[NEAR-RIC]: Loading SM ID = 147 with def = ORAN-E2SM-KPM
[NEAR-RIC]: Loading SM ID = 146 with def = TC_STATS_V0
[iApp]: Initializing ...
[iApp]: nearRT-RIC IP Address = 127.0.0.1, PORT = 36422
fd created with 6
but, when I start up the gNB, I get the following output in the FlexRIC terminal:
Received message with id = 411, port = 40429
[E2AP] Received SETUP-REQUEST from PLMN 1. 1 Node ID 411 RAN type ngran_gNB
Unknown RAN function ID, thus rejecting 2
nearRT-RIC: /home/lucas/flexric/src/ric/msg_handler_ric.c:100: generate_setup_response: Assertion `0!=0 && "Unknown RAN function ID from the agent received"' failed.
Aborted (core dumped)
lucas@lucas-dell-research:~$
For reference, this is what the ouput in the gNB terminal looks like:
lucas@lucas-dell-research:~/srsRAN_Project$ sudo ./build/apps/gnb/gnb -c gnb_zmq.yaml
The PRACH detector will not meet the performance requirements with the configuration {Format 0, ZCZ 0, SCS 1.25kHz, Rx ports 1}.
Lower PHY in executor blocking mode.
--== srsRAN gNB (commit 55c984b) ==--
Connecting to AMF on 10.53.1.2:38412
Available radio types: zmq.
Connecting to NearRT-RIC on 127.0.0.1:36421
Cell pci=1, bw=10 MHz, dl_arfcn=368500 (n3), dl_freq=1842.5 MHz, dl_ssb_arfcn=367930, ul_freq=1747.5 MHz
==== gNodeB started ===
Type to view trace
Can anyone give me a hint about why I might be having this issue? I had this same experiment running just fine on a VM, but it's giving me problems now that I have a dedicated Linux machine.
Please let me know what further details might be helpful.
Beta Was this translation helpful? Give feedback.
All reactions