search

srsran / srsRAN_Project

Open source O-RAN 5G CU/DU solution from Software Radio Systems (SRS) https://docs.srsran.com/projects/project
https://www.srsran.com
GNU Affero General Public License v3.0
478 stars 163 forks source link

srsGNB ERROR: CU-CP failed to connect to AMF #423

Closed oliverxsch closed 7 months ago

oliverxsch commented 8 months ago

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 0b2702cca) ==--

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 0b2702cca 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

hudouseko commented 8 months ago

Hi, try to check on open5gs in amf configuration (/etc/openg5s/amf.yaml) if it contains appropriate TAI configuration corresponding to your gNB config: amf: tai:

oliverxsch commented 8 months ago

Hi, try to check on open5gs in amf configuration (/etc/openg5s/amf.yaml) if it contains appropriate TAI configuration corresponding to your gNB config: amf: tai: - plmn_id: mcc: 001 mnc: 01 tac: 7

Thanks for your answer. I already did this before. But I will atach all of my Open5Gs configs, if it helps. open5gsconfs.zip

pgawlowicz commented 8 months ago

did you restart the Open5GS demons whose configs were changed? Check here: https://open5gs.org/open5gs/docs/guide/01-quickstart/ Probably you need:

sudo systemctl restart open5gs-amfd
oliverxsch commented 8 months ago

did you restart the Open5GS demons whose configs were changed? Check here: https://open5gs.org/open5gs/docs/guide/01-quickstart/ Probably you need:

sudo systemctl restart open5gs-amfd

Hello, i restarted all of them because its easy to do. To start the daemons i simply used the third command: _

For convenience, you can execute all NFs at once by using the following command.

$ ./build/tests/app/5gc ## 5G Core Only with ./build/configs/sample.yaml $ ./build/tests/app/epc -c ./build/configs/srslte.yaml ## EPC Only with ./build/configs/srslte.yaml $ ./build/tests/app/app ## Both 5G Core and EPC with ./build/configs/sample.yaml

_ And to stop them i press STRG+C in that command window.

Your suggestion:

sudo systemctl restart open5gs-amfd

Did not work for me (maybe because its installed from source?)

Using this command results in: Failed to restart open5gs-amfd.service: Unit open5gs-amfd.service is masked.

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: 01/24 13:20:15.014: [amf] INFO: gNB-N2 accepted[127.0.0.1]:46435 in ng-path module (../src/amf/ngap-sctp.c:113) 01/24 13:20:15.014: [amf] INFO: gNB-N2 accepted[127.0.0.1] in master_sm module (../src/amf/amf-sm.c:736) 01/24 13:20:15.017: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:1235) 01/24 13:20:15.017: [amf] INFO: gNB-N2[127.0.0.1] max_num_of_ostreams : 30 (../src/amf/amf-sm.c:775) 01/24 13:20:15.017: [amf] WARNING: NG-Setup failure: (../src/amf/ngap-handler.c:342) 01/24 13:20:15.017: [amf] WARNING: Cannot find Served TAI. Check 'amf.tai' configuration (../src/amf/ngap-handler.c:343) 01/24 13:20:25.052: [amf] INFO: gNB-N2[127.0.0.1] connection refused!!! (../src/amf/amf-sm.c:788) 01/24 13:20:25.052: [amf] INFO: [Removed] Number of gNBs is now 0 (../src/amf/context.c:1262)

pgawlowicz commented 8 months ago

Could you change TAC to 1 in srsgnb config and see if it connects?

cell_cfg:
...
  tac: 1
oliverxsch commented 8 months ago

Could you change TAC to 1 in srsgnb config and see if it connects?

cell_cfg:
...
  tac: 1

Problem and console output stays the same.

pgawlowicz commented 8 months ago

which open5gs version do you use? have you seen those answers: https://github.com/srsran/srsRAN_Project/discussions/388#discussioncomment-8055894 https://github.com/open5gs/open5gs/discussions/2782#discussioncomment-8001181

oliverxsch commented 8 months ago

which open5gs version do you use? have you seen those answers: #388 (comment) open5gs/open5gs#2782 (comment)

I don't have an idea how to find out which version im using. It looks like the usual commands do not work if i installed it from source. But if it helps: I installed it yesterday from source, so it should be the newest version.

Unfortunaly the answers in the linked issue did not work for me.

pgawlowicz commented 8 months ago

ok, then please check with our Open5gs docker image by following this tutorial: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#zeromq-based-setup

please pay attention to this troubleshooting note: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#nd-open5gs-instance-installed-manually

If it works with Open5gs docker image, then there is an issue with your local setup/configs.

oliverxsch commented 8 months ago

ok, then please check with our Open5gs docker image by following this tutorial: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#zeromq-based-setup

please pay attention to this troubleshooting note: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#nd-open5gs-instance-installed-manually

If it works with Open5gs docker image, then there is an issue with your local setup/configs.

Okay, i will try. I will answer again after i tried it.

But maybe this helps (this is still with open5gs from source):

message(2).txt

Its from the open5gs console running in debug mode.

pgawlowicz commented 8 months ago

probably, there is already a docker network that uses the same address space the open5gs wants to create. check here

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: https://github.com/srsran/srsRAN_Project/blob/main/docker/open5gs/open5gs.env#L2

oliverxsch commented 8 months ago

ok, then please check with our Open5gs docker image by following this tutorial: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#zeromq-based-setup

please pay attention to this troubleshooting note: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#nd-open5gs-instance-installed-manually

If it works with Open5gs docker image, then there is an issue with your local setup/configs.

Thanks a lot!!! First i was unable to install the docker container but after doing this: https://github.com/maxking/docker-mailman/issues/85#issuecomment-349429246 I was able to get a step further.

Now im facing a new issue: inets@inets-LAB:~/srsRAN_Project/build$ 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 0b2702cca) ==--

Connecting to AMF on 10.53.1.2:38412 Available radio types: uhd. [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_21.11; UHD_4.5.0.HEAD-0-g471af98f [INFO] [LOGGING] Fastpath logging disabled at runtime. Making USRP object with args 'type=x4xx,addr=192.168.11.2,second_addr=192.168.10.2,master_clock_rate=245.76e6,send_frame_size=8000,recv_frame_size=8000' [INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.168.11.2,type=x4xx,product=x410,serial=324B8F0,name=ni-x4xx-324B8F0,fpga=X4_200,claimed=False,addr=192.168.11.2,second_addr=192.168.10.2,master_clock_rate=245.76e6,send_frame_size=8000,recv_frame_size=8000 [INFO] [MPM.main] Launching USRP/MPM, version: 4.5.0.0-g471af98f [INFO] [MPM.main] Spawning RPC process... [INFO] [MPM.PeriphManager] Device serial number: 324524B [INFO] [MPM.PeriphManager.ClkMgr] Using Clock Configuration: DB0: Master Clock Rate: 245.76 MSps @Converter Rate 2.94912 GHz DB1: Master Clock Rate: 245.76 MSps @Converter Rate 2.94912 GHz [INFO] [MPM.PeriphManager] Initialized 2 daughterboard(s). [INFO] [MPM.PeriphManager] init() called with device args boot_init=True,clock_source=internal,time_source=internal,initializing=True'. [INFO] [MPM.RPCServer] RPC server ready! [INFO] [MPM.RPCServer] Spawning watchdog task... [INFO] [MPM.PeriphManager] init() called with device argsfpga=X4_200,master_clock_rate=(245760000.0,),mgmt_addr=192.168.11.2,name=ni-x4xx-324B8F0,product=x410,recv_frame_size=8000,second_addr=192.168.10.2,send_frame_size=8000,clock_source=internal,time_source=internal,initializing=True'. [INFO] [0/Radio#0] Clocking reconfigured, running ADC Self Cal on DB0... [INFO] [0/Radio#0] Calibrating channel 0... [INFO] [0/Radio#0] Calibrating channel 1... [INFO] [0/Radio#1] Clocking reconfigured, running ADC Self Cal on DB1... [INFO] [0/Radio#1] Calibrating channel 2... [INFO] [0/Radio#1] Calibrating channel 3... [WARNING] [MPM.PeriphManager.ClkMgr] Clock source internal is an invalid selection with time source external. Coercing clock source to external [INFO] [MPM.PeriphManager.ClkMgr] Using Clock Configuration: DB0: Master Clock Rate: 245.76 MSps @Converter Rate 2.94912 GHz DB1: Master Clock Rate: 245.76 MSps @Converter Rate 2.94912 GHz [INFO] [0/Radio#0] Clocking reconfigured, running ADC Self Cal on DB0... [INFO] [0/Radio#0] Calibrating channel 0... [INFO] [0/Radio#0] Calibrating channel 1... [INFO] [0/Radio#1] Clocking reconfigured, running ADC Self Cal on DB1... [INFO] [0/Radio#1] Calibrating channel 2... [INFO] [0/Radio#1] Calibrating channel 3... Error: setting Tx sampling rate. Tx Rate 23.04 MHz is invalid. The nearest valid value is 22.341818181818184. srsGNB ERROR: Unable to create radio session.

Is the X410 not supported?

pgawlowicz commented 8 months ago

you have to use:

ru_sdr:
...
  srate: 30.72
oliverxsch commented 8 months ago

you have to use:

ru_sdr:
...
  srate: 30.72

Thanks a lot for your answer. It looks like im now in a situation simular to one of my old issues. However it looks like your fixes from back then do not solve my problems now. Im able to connect the UE to the gnb. Im also able to ping the gnb from the UE. However i cannot start an iperf test or an speedtest using the ue. Also i cannot ping the UE from the gnb. I did all the commands for the routing configuration from the tutorial. Do you have an idea, why this does not work? image2 image gnbx410.yml (2).txt ue_x310.conf.txt

pgawlowicz commented 8 months ago

could you check if setting time_adv_nsamples = 600 in srsue conf helps?

oliverxsch commented 8 months ago

could you check if setting time_adv_nsamples = 600 in srsue conf helps?

It does not help. More to the contrary, it leads to the UE not connecting at all. If I change it back to auto its like before.

Console Log: inets@inets-LAB:~/srsRAN_4G/build$ sudo srsue /home/inets/Documents/ue_x310.conf Active RF plugins: libsrsran_rf_uhd.so Inactive RF plugins: Reading configuration file /home/inets/Documents/ue_x310.conf...

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 Supported RF device list: UHD file [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.5.0.HEAD-0-g471af98f [INFO] [LOGGING] Fastpath logging disabled at runtime. Opening USRP channels=1, 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,sync=external [INFO] [UHD RF] RF UHD Generic instance constructed [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [X300] Radio 1x clock: 184.32 MHz Setting manual TX/RX offset to 600 samples Waiting PHY to initialize ... done! Attaching UE... Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1134 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1294 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1454 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1614 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1774 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1934 RF status: O=0, U=0, L=6 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=2094 ^CStopping .. --- exiting ---

pgawlowicz commented 8 months ago

could you change the line in srsue config: from device_args = clock=external to device_args = clock_source=external

and try with both time_adv_nsamples=auto and time_adv_nsamples=300 ??

oliverxsch commented 8 months ago

could you change the line in srsue config: from device_args = clock=external to device_args = clock_source=external

and try with both time_adv_nsamples=auto and time_adv_nsamples=300 ??

Both of these suggestion lead to this console output. Nothing happens, there aren't even any Random Access Transmission: inets@inets-LAB:~/srsRAN_4G/build$ sudo srsue /home/inets/Documents/ue_x310.conf Active RF plugins: libsrsran_rf_uhd.so Inactive RF plugins: Reading configuration file /home/inets/Documents/ue_x310.conf...

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 Supported RF device list: UHD file [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.5.0.HEAD-0-g471af98f [INFO] [LOGGING] Fastpath logging disabled at runtime. Opening USRP channels=1, 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 [INFO] [UHD RF] RF UHD Generic instance constructed [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [X300] Radio 1x clock: 184.32 MHz Waiting PHY to initialize ... done! Attaching UE...

oliverxsch commented 8 months ago

Might this be an issue because I use two different types of SDR for UE and GNB? Because my UE is a X410 and my GNB is a X310. I do not have access to another X410, but I could try another X310?

pgawlowicz commented 8 months ago

no, it should not be an issue to run with two different USRPs

pgawlowicz commented 8 months ago

could you go back to the last working configs (when the srsUE connects and gets IP address) and try with 10mhz bandwidth?

oliverxsch commented 8 months ago

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. After "Attaching UE" nothing happens. I adjusted the values to 10 Mhz but i might not have done it correctly which is why i will attach the UE and gNB config.

gnb_20Mhz_x410.yml.txt ue_10Mhz_x310.conf.txt

pgawlowicz commented 8 months ago

You need to run gnb with 10mhz bandwidth as well.

oliverxsch commented 8 months ago

You need to run gnb with 10mhz bandwidth as well.

Ups. I did. I just attached the wrong file ;) I will be able to upload the file tomorrow.

mrouili commented 8 months ago

you have to use:

ru_sdr:
...
  srate: 30.72

Thanks a lot for your answer. It looks like im now in a situation simular to one of my old issues. However it looks like your fixes from back then do not solve my problems now. Im able to connect the UE to the gnb. Im also able to ping the gnb from the UE. However i cannot start an iperf test or an speedtest using the ue. Also i cannot ping the UE from the gnb. I did all the commands for the routing configuration from the tutorial. Do you have an idea, why this does not work? image2 image gnbx410.yml (2).txt ue_x310.conf.txt

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.

oliverxsch commented 8 months ago

you have to use:

ru_sdr:
...
  srate: 30.72

Thanks a lot for your answer. It looks like im now in a situation simular to one of my old issues. However it looks like your fixes from back then do not solve my problems now. Im able to connect the UE to the gnb. Im also able to ping the gnb from the UE. However i cannot start an iperf test or an speedtest using the ue. Also i cannot ping the UE from the gnb. I did all the commands for the routing configuration from the tutorial. Do you have an idea, why this does not work? image2 image gnbx410.yml (2).txt ue_x310.conf.txt

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. Then I will try to use another X310 first to see if this solves the issue and if it does i will try the X410 as the UE. I thought the X410 would lead to better results because with e.G. Open Air Interface it lead to better performance.

oliverxsch commented 8 months ago

You need to run gnb with 10mhz bandwidth as well. gnb_10Mhz_x410.yml.txt

Here is the correct config :)

oliverxsch commented 8 months ago

you have to use:

ru_sdr:
...
  srate: 30.72

Thanks a lot for your answer. It looks like im now in a situation simular to one of my old issues. However it looks like your fixes from back then do not solve my problems now. Im able to connect the UE to the gnb. Im also able to ping the gnb from the UE. However i cannot start an iperf test or an speedtest using the ue. Also i cannot ping the UE from the gnb. I did all the commands for the routing configuration from the tutorial. Do you have an idea, why this does not work? image2 image gnbx410.yml (2).txt ue_x310.conf.txt

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.

Mh. The situation did not change. Now both my gnb and ue are X310s but the problem persists. On 20MHz it connects but only ping from UE to gnb is possible. On 10 Mhz it does not even connect. These were my configs: ue and gnb confs.zip This is a screenshot from the unsuccesful ping from gnb to UE (on 20 MHz) grafik Also I tried to redo the network configuration from the tutorial but this error occured on the UE side: grafik

Thanks in advance

pgawlowicz commented 8 months ago

thanks for the configs, they look good except the gnb config for 10mhz, where you are missing:

  pdcch:
    common:
      ss0_index: 0                  # Set search space zero index to match srsUE capabilities
      coreset0_index: 6            # Set search CORESET Zero index to match srsUE capabilities
    dedicated:
      ss2_type: common              # Search Space type, has to be set to common
      dci_format_0_1_and_1_1: false # Set correct DCI format (fallback)
  prach:
    prach_config_index: 1           # Sets PRACH config to match what is expected by srsUE

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.

oliverxsch commented 8 months ago

thanks for the configs, they look good except the gnb config for 10mhz, where you are missing:

  pdcch:
    common:
      ss0_index: 0                  # Set search space zero index to match srsUE capabilities
      coreset0_index: 6            # Set search CORESET Zero index to match srsUE capabilities
    dedicated:
      ss2_type: common              # Search Space type, has to be set to common
      dci_format_0_1_and_1_1: false # Set correct DCI format (fallback)
  prach:
    prach_config_index: 1           # Sets PRACH config to match what is expected by srsUE

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. Only ping from UE to gnb is possible. If i ping the UE from the gnb, the same like in the screenshot above happens.

Using X410 as the gnb does not change the situation, so I think the X410 is not an issue.

Thanks in advance for testing :)

oliverxsch commented 7 months ago

Today i tried to use a different x310 and different cables just in case anything was faulty. But it still does not work.

pgawlowicz commented 7 months ago

@oliverxsch I still have not managed to replicate your experiment here locally yet, I will do it this week. But could you quickly try to use the following values {345, 800, 845} for the time_adv_nsamples for your srsUE running on x310 with srate=30.72Mhz? And let me know the results.

oliverxsch commented 7 months ago

@oliverxsch I still have not managed to replicate your experiment here locally yet, I will do it this week. But could you quickly try to use the following values {345, 800, 845} for the time_adv_nsamples for your srsUE running on x310 with srate=30.72Mhz? And let me know the results.

Hi, i tried to use your values. These are the console output i got: value 345 and 800:

Attaching UE... Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=974 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1134 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1294 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1454 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1614 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1774 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=1934

value 845:

Attaching UE... Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=3694 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=3854 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=4014 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=4174 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=4334 RF status: O=0, U=0, L=7 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=4494 Random Access Transmission: prach_occasion=0, preamble_index=0, ra-rnti=0x39, tti=4654

On auto it still connects but only ping from ue to gnb is possible but not the other way around. By the way, i just realised that i never sended you the log and pcap files. I will attach them for the "auto" case. gnblog(1).txt pcapfiles.zip uelog(2).txt

pgawlowicz commented 7 months ago

ok, thank you! Then I need to check locally

oliverxsch commented 7 months ago

Any new ideas? I would very much appreciate it.

oliverxsch commented 7 months ago

ok, thank you! Then I need to check locally

you have to use:

ru_sdr:
...
  srate: 30.72

Thanks a lot for your answer. It looks like im now in a situation simular to one of my old issues. However it looks like your fixes from back then do not solve my problems now. Im able to connect the UE to the gnb. Im also able to ping the gnb from the UE. However i cannot start an iperf test or an speedtest using the ue. Also i cannot ping the UE from the gnb. I did all the commands for the routing configuration from the tutorial. Do you have an idea, why this does not work? image2 image gnbx410.yml (2).txt ue_x310.conf.txt

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.

I closed this issue, because the current problem does not fit to the title and the CN problem. https://github.com/srsran/srsRAN_Project/issues/480