Connecting Near RT RIC to gNB in Indoor OTA Lab

[Adithya Anand]

Hi All 

I am running into an issue with connecting the Near RT RIC to my gNB in the POWDER Indoor OTA profile. The current issue involves the gNB being unable to create a SCTP gateway when trying to connect with the Near RT RIC. This is due to the incorrect RIC IP address and maybe port number (although the same port number for the AMF works). The error message is as follows. 

I can also post the config files I have for the gNB and RIC. 

[David M Johnson]

On 10/9/24 21:14, Adithya Anand wrote:
> Hi All
>
> I am running into an issue with connecting the Near RT RIC to my gNB in
> the POWDER Indoor OTA profile. The current issue involves the gNB being
> unable to create a SCTP gateway when trying to connect with the Near RT
> RIC. This is due to the incorrect RIC IP address and maybe port number
> (although the same port number for the AMF works). The error message is
> as follows.

> Screenshot 2024-10-09 231105.png
>
> I can also post the config files I have for the gNB and RIC.

Hi Adithya,

The screenshot shows your srsRAN gNB trying to use `127.0.0.1` as the
RIC ip address. Is your RIC really listening on `127.0.0.1` of your gNB
node? If not, you'll want to change the srsRAN config bits to the
proper IP addr and port, as demonstrated here:
https://docs.srsran.com/projects/project/en/latest/tutorials/source/near-rt-ric/source/index.html#gnb
.

David

[Adithya Anand]

I have tried a few other IP addresses based on the config files of the RIC, but they also dont work. Specifically I have tried  10.0.2.10, 10.0.2.15, 10.0.2.1, 192.168.1.2; they all result in the same issue. I had tried 127.0.0.1 (loopback address) as the RIC and gNB are on the same server. 

I had looked into the same tutorial for modifying the other parts of the gNB config file. 

[David M Johnson]

Can you please say more about the scenario you are trying to create?
Which RIC? Are you using the OSC near-real time RIC from our O-RAN
profile (https://www.powderwireless.net/show/PowderProfiles/O-RAN)?
Where (on which node) is your RIC being deployed?

David

> https://docs.srsran.com/projects/project/en/latest/tutorials/source/near-rt-ric/source/index.html#gnb <https://docs.srsran.com/projects/project/en/latest/tutorials/source/near-rt-ric/source/index.html#gnb>
> .
>
> David
>
> --
> You received this message because you are subscribed to the Google
> Groups "Powder Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to powder-users...@googlegroups.com
> <mailto:powder-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/powder-users/ed314173-f6b3-4e14-8733-2e95588d3ed2n%40googlegroups.com <https://groups.google.com/d/msgid/powder-users/ed314173-f6b3-4e14-8733-2e95588d3ed2n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Adithya Anand]

yes of course

I am using the O-RAN Near RT RIC (dockized version,  https://github.com/srsran/oran-sc-ric) to host xAPP's that will currentlly collect averages of KPM's. 

No I am just using an instance in the indoor OTA Lab

The RIC is on the gNB server, in my profile this is a d430 as no d470's were available when reserving. 

I have made some progress by changing the RIC addr to 10.0.2.10 AND including the bind:addr. Although the bind:addr does not make sense to me as the gNB and RIC are on the same server, unless the RIC being in a docker container affects this. In a tutorial from srsRAN they did the same thing and they did not have to include the bind:addr and their RIC addr was the loopback address. 

Images in order: gNB, RIC, then Core Network.