srs RAN docker not working

[jfrey-ntia]

I am trying to get a basic RAN going using a Ettus Research B210. From reading the Docker Readme, it seems like running docker compose up should bring up the core and the gnb. However, when I run sudo docker compose up from the docker directory, the core seems to start up fine, but the gnb gives the following error:

srsran_gnb      | amf was not readable (missing?)
srsran_gnb      | Run with --help for more information.
srsran_gnb      | 
srsran_gnb      | --== srsRAN gNB (commit 8120ffbce) ==--
srsran_gnb      | 
srsran_gnb exited with code 103

Looking at the config files, it appears that the core IP is 10.53.1.2 and this is ping-able from outside the container. I then tried to run the gnb without the container. I changed the IP in the config file and ran the following:

sudo ./gnb -c ../../../configs/gnb_rf_b200_tdd_n78_20mhz.yml

The result was:

--== srsRAN gNB (commit 8120ffbce) ==--

Lower PHY in quad executor mode.
Available radio types: uhd.
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.8.0.0-64-g0dede88c
[INFO] [LOGGING] Fastpath logging disabled at runtime.
Making USRP object with args 'type=b200,num_recv_frames=64,num_send_frames=64'
[INFO] [B200] Detected Device: B210
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Detecting internal GPSDO.... 
[INFO] [GPS] Found an internal GPSDO: GPSTCXO, Firmware Rev 0.929b
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test... 
[INFO] [B200] Register loopback test passed
[INFO] [B200] Performing register loopback test... 
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz... 
[INFO] [B200] Actually got clock rate 16.000000 MHz.
[INFO] [MULTI_USRP] Setting master clock rate selection to 'manual'.
[INFO] [B200] Asking for clock rate 23.040000 MHz... 
[INFO] [B200] Actually got clock rate 23.040000 MHz.
Cell pci=1, bw=20 MHz, 1T1R, dl_arfcn=632628 (n78), dl_freq=3489.42 MHz, dl_ssb_arfcn=632256, ul_freq=3489.42 MHz

N2: Failed to connect to AMF on 10.53.1.2:38412. error="Network is unreachable" timeout=0ms
srsRAN ERROR: CU-CP failed to connect to AMF

I am unsure how to get the gnb to talk to the core, what could I be doing wrong?

[jfrey-ntia]

Ok, I have looked into this a little more, and I think I understand what amf was not readable (missing?) actually means. it's complaining about the command line arguments to the gnb executable. Running the gnb while trying to use the amf sub-command also gives an error. It seems to work if I remove amf --addr ${OPEN5GS_IP:-10.53.1.2} --bind_addr ${GNB_IP:-10.53.1.3} from the gnb command section in the docker compose file and instead set the addresses in the config.

[pgawlowicz]

Please replace the following line in /docker-compose.yml:

command: gnb -c /gnb_config.yml amf --addr ${OPEN5GS_IP:-10.53.1.2} --bind_addr ${GNB_IP:-10.53.1.3}

with:

command: gnb -c /gnb_config.yml cu_cp amf --addr ${OPEN5GS_IP:-10.53.1.2} --bind_addr ${GNB_IP:-10.53.1.3}

[jfrey-ntia]

Thanks! that works. Looking at the enb config, it seems like the arguments follow the sections in the file. Do you know why it's not this way in docker/docker-compose.yml?

[pgawlowicz]

it will be updated.