-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
srsGNB ERROR: CU-CP failed to connect to AMF #423
Comments
Hi, try to check on open5gs in amf configuration (/etc/openg5s/amf.yaml) if it contains appropriate TAI configuration corresponding to your gNB config: |
Thanks for your answer. |
did you restart the Open5GS demons whose configs were changed?
|
Hello,
_ Your suggestion:
Did not work for me (maybe because its installed from source?) Using this command results in: Anyways, restarting all daemons/or the host computer did not help. By the way this is what happens in the open5gs console when i try to start the gnb: |
Could you change TAC to 1 in srsgnb config and see if it connects?
|
Problem and console output stays the same. |
which open5gs version do you use? |
I don't have an idea how to find out which version im using. Unfortunaly the answers in the linked issue did not work for me. |
ok, then please check with our Open5gs docker image by following this tutorial: please pay attention to this troubleshooting note: If it works with Open5gs docker image, then there is an issue with your local setup/configs. |
Okay, i will try. But maybe this helps (this is still with open5gs from source): Its from the open5gs console running in debug mode. |
probably, there is already a docker network that uses the same address space the open5gs wants to create. you need to remove the existing docker network or change the the config in docker-compose file. In the latter case, you need to update here: |
Thanks a lot!!! Now im facing a new issue: The PRACH detector will not meet the performance requirements with the configuration {Format 0, ZCZ 0, SCS 1.25kHz, Rx ports 1}. --== srsRAN gNB (commit 0b2702c) ==-- Connecting to AMF on 10.53.1.2:38412 Is the X410 not supported? |
you have to use:
|
Thanks a lot for your answer. |
could you check if setting |
It does not help. Console Log: Built in Release mode using commit eea87b1d8 on branch master. Opening 1 channels in RF device=uhd with args=type=x300,addr=192.168.43.2,second_addr=192.168.30.2,master_clock_rate=184.32e6,send_frame_size=8000,recv_frame_size=8000,clock=external,sync=external |
could you change the line in srsue config: and try with both |
Both of these suggestion lead to this console output. Nothing happens, there aren't even any Random Access Transmission: Built in Release mode using commit eea87b1d8 on branch master. Opening 1 channels in RF device=uhd with args=type=x300,addr=192.168.43.2,second_addr=192.168.30.2,master_clock_rate=184.32e6,send_frame_size=8000,recv_frame_size=8000,clock_source=external,sync=external |
Might this be an issue because I use two different types of SDR for UE and GNB? |
no, it should not be an issue to run with two different USRPs |
could you go back to the last working configs (when the srsUE connects and gets IP address) and try with 10mhz bandwidth? |
I tried, weirdly enough this doesn't work either. |
You need to run gnb with 10mhz bandwidth as well. |
Ups. I did. I just attached the wrong file ;) |
Hi @oliverxsch and @pgawlowicz , I'd like to point out that a while back I have tried using the Ettus USRP x410 and I faced the exact same issues. The only difference is that I was using an actual UE (Pixel 7 pro) instead of srsUE. With the X310 everything works correctly but for some reason this happens when using an x410. @oliverxsch maybe try to use the X310 as the RU and x410 as UE ? this isn't a solution but just to see if the usage of the x410 as the RU is what causes this issue. |
Okay, thanks for your suggestion. |
Here is the correct config :) |
Mh. Thanks in advance |
thanks for the configs, they look good except the gnb config for 10mhz, where you are missing:
Please try to add it and see what happens, if there is any RACH attempt from the UE. I will try to reproduce your experiment in our local lab next week. |
This explains why 10 Mhz did not work at all. Now i have the same situation like with 20 Mhz. Using X410 as the gnb does not change the situation, so I think the X410 is not an issue. Thanks in advance for testing :) |
Today i tried to use a different x310 and different cables just in case anything was faulty. |
@oliverxsch I still have not managed to replicate your experiment here locally yet, I will do it this week. |
Hi, Attaching UE... value 845: Attaching UE... On auto it still connects but only ping from ue to gnb is possible but not the other way around. |
ok, thank you! Then I need to check locally |
Any new ideas? |
I closed this issue, because the current problem does not fit to the title and the CN problem. |
Issue Description
Hi community,
I previously had a functional srsRAN setup, but when I attempted to use it again last week, the gNB failed to start. Upon investigation, I discovered that the open5gs-amf and mme daemons were not running, and I was unable to initiate them.
In an attempt to resolve the issue, I reinstalled open5gs, but unfortunately, this did not fix the problem. Subsequently, I installed open5gs from source. Currently, all daemons are running; however, I'm encountering difficulty starting the gNB.
I have attached the gnb config file. I followed the tutorial at the following link: https://open5gs.org/open5gs/docs/guide/02-building-open5gs-from-sources/. I followed all the steps outlined in the tutorial (excluding the addresses, which remained as 127.0.0.X).
Changes were made to tac, plm, etc.
Do you have any ideas on how to resolve this issue?
Thanks in advance.
Regards
This is the gnb console log:
sudo gnb -c /home/inets/Documents/gnbx410.yml
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 quad executor mode.
--== srsRAN gNB (commit 0b2702c) ==--
Connecting to AMF on 127.0.0.5:38412
srsGNB ERROR: CU-CP failed to connect to AMF
Open5G:
01/23 14:21:37.839: [amf] INFO: gNB-N2 accepted[127.0.0.1]:45665 in ng-path module (../src/amf/ngap-sctp.c:113)
01/23 14:21:37.839: [amf] INFO: gNB-N2 accepted[127.0.0.1] in master_sm module (../src/amf/amf-sm.c:736)
01/23 14:21:37.842: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:1235)
01/23 14:21:37.842: [amf] INFO: gNB-N2[127.0.0.1] max_num_of_ostreams : 30 (../src/amf/amf-sm.c:775)
01/23 14:21:37.842: [amf] WARNING: NG-Setup failure: (../src/amf/ngap-handler.c:342)
01/23 14:21:37.842: [amf] WARNING: Cannot find Served TAI. Check 'amf.tai' configuration (../src/amf/ngap-handler.c:343)
01/23 14:21:47.898: [amf] INFO: gNB-N2[127.0.0.1] connection refused!!! (../src/amf/amf-sm.c:788)
01/23 14:21:47.898: [amf] INFO: [Removed] Number of gNBs is now 0 (../src/amf/context.c:1262)
This is the whole gnb.log
2024-01-23T13:21:37.837644 [GNB ] [I] Built in Release mode using commit 0b2702c on branch main
2024-01-23T13:21:37.838850 [ALL ] [I] Task worker "phy_prach#0" started...
2024-01-23T13:21:37.839038 [ALL ] [I] Task worker "ru_stats_worker" started...
2024-01-23T13:21:37.839064 [ALL ] [I] Task worker "radio" started...
2024-01-23T13:21:37.839101 [ALL ] [I] Task worker "lower_phy_rx#0" started...
2024-01-23T13:21:37.839120 [ALL ] [I] Task worker "lower_phy_dl#0" started...
2024-01-23T13:21:37.839151 [ALL ] [I] Task worker "lower_phy_ul#0" started...
2024-01-23T13:21:37.839162 [ALL ] [I] Task worker "lower_phy_tx#0" started...
2024-01-23T13:21:37.839326 [GNB ] [I] Connecting to AMF (127.0.0.5)..
2024-01-23T13:21:37.839412 [GNB ] [I] AMF connection established
2024-01-23T13:21:37.839806 [GNB ] [I] Starting CU-CP...
2024-01-23T13:21:37.839857 [NGAP ] [I] Sending NgSetupRequest
2024-01-23T13:21:37.842512 [NGAP ] [I] Reinitiating NG setup in 10000s (retry=1/5). Received NGSetupFailure with Time to Wait IE
2024-01-23T13:21:47.849918 [GNB ] [I] CU-CP started successfully
Setup Details
First PC:
Specs: i9 13900, 64GB Ram
OS: Ubuntu 22.04.03 LTS
Newest srsRAN Project and newest Open5Gs.
Connected via a 10G-Link to a USRP X410
"gNB"
gnbx410.yml.txt
The text was updated successfully, but these errors were encountered: