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
514 stars 173 forks source link

"Network is unreachable" when connecting to ORAN-SC near-RT RIC #248

Closed hoangtuansu closed 1 year ago

hoangtuansu commented 1 year ago

Issue Description

srsRAN gNB (commit 5e6f50a20) failed to connect SCTP socket of ORAN-SC nearRT-RIC while commit c54bcfe works. I followed the tutorial from https://docs.srsran.com/projects/project/en/latest/tutorials/source/flexric/source/index.html and only replace FlexRIC by ORAN-SC nearRT-RIC.

image

Setup Details

Server host srsRAN gNB and Open5GS: Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz, 96 cores, 192 threads, 256 GB RAM, 500 Gi SSD.

Expected Behavior

The connection should be successfully created as it did with commit c54bcfe

image

Actual Behaviour

Only NGAP messages are exchanged. 2 other files (gnb_e2ap, gnb_mac) are empty.

Steps to reproduce the problem

srsRAN commit 5e6f50a20 ORAN-SC nearRT-RIC H version, deployed on K8s and exposed its pod, i.e. e2term, via a NodePort service.

srs.zip gnb.log gnb_zmq.txt

hoangtuansu commented 1 year ago

Close. Fix by adding bind_addr to config file.

fklement commented 9 months ago

@hoangtuansu Which release of the O-RAN SC did you use? Was it the h-release?

faratell commented 3 months ago

Hello. I was installed near RT RIC from bellow link and all pods are ok running: https://gerrit.o-ran-sc.org/r/gitweb?p=ric-plt/ric-dep.git;a=blob;f=new-installer/README.md;h=a4cb085c12a61bfd7421c8b04aee147232688c42;hb=HEAD

kubectl get pods -n ricplt NAME READY STATUS RESTARTS AGE deployment-ricplt-a1mediator-7fdbb756c5-2qrx7 1/1 Running 1 (15h ago) 15h deployment-ricplt-appmgr-6f445568d9-8xtpd 1/1 Running 0 15h deployment-ricplt-e2mgr-647999fcbc-zl755 1/1 Running 3 (15h ago) 15h deployment-ricplt-e2term-alpha-5cdf68cb54-kcjlx 1/1 Running 0 15h deployment-ricplt-rtmgr-86c96d6b6-mjwrv 1/1 Running 0 15h deployment-ricplt-submgr-64c9b8cf89-kwd9h 1/1 Running 0 15h ricplt-influxdb-0 1/1 Running 0 15h statefulset-ricplt-dbaas-server-0 1/1 Running 0 15h

Also i set my mcc and mnc in near RT RIC yaml file. ric ip an aux ip are also set as ip of my near RT RIC machine.

extsvcplt: ricip: "192.168.75.154" auxip: "192.168.75.154" %% e2mgr: e2mgr: image: registry: "nexus3.o-ran-sc.org:10002/o-ran-sc" name: ric-plt-e2mgr tag: 6.0.1 privilegedmode: false globalRicId: ricId: "AACCE" mcc: "999" mnc: "70" rnibWriter: stateChangeMessageChannel: RAN_CONNECTION_STATUS_CHANGE ranManipulationMessageChannel: RAN_MANIPULATION %% I also installed srsRAN-project in another machine and set e2 parameters in gnb.yaml config as bellow : e2: enable_du_e2: true # Enable DU E2 agent (one for each DU insta> e2sm_kpm_enabled: true # Enable KPM service module addr: 192.168.75.154 # RIC IP address bind_addr: 192.168.75.151 # A local IP that the E2 agent binds to fo> port: 36422 # RIC port

But have this error: ./gnb -c gnb_zmq_e2.yaml

--== srsRAN gNB (commit 40b17b429) ==--

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. N2: Connection to AMF on 192.168.75.150:38412 completed Cell pci=1, bw=10 MHz, 1T1R, dl_arfcn=368500 (n3), dl_freq=1842.5 MHz, dl_ssb_arfcn=368410, ul_freq=1747.5 MHz

Connecting to NearRT-RIC on 192.168.75.154:36422 Failed to connect SCTP socket to 192.168.75.154:36422. error="Connection refused" timeout=0ms srsRAN ERROR: Failed to create SCTP gateway.

Can you help me how can solve it?

pgawlowicz commented 3 months ago

can you ping RIC PC from the srsGNB pc?

faratell commented 3 months ago

can you ping RIC PC from the srsGNB pc?

yes srsGNB can ping RIC

faratell commented 3 months ago

@hoangtuansu can you help me? what should I set for bind_addr , e2 addr , ricip and auxip: and e2 port? if i installed srsRAN on 192.168.75.183 , nrt ric on 192.168.75.197 vm with docker interface 172.17.0.1 , and kubectl get svc -n ricplt show : service-ricplt-e2term-sctp-alpha NodePort 10.101.146.165 36422:32222/SCTP 19d

faratell commented 2 months ago

Can any one help me?