Problem integrating E2 interface with external nearRT-RIC

[EspiMCF]

Hello,

I am facing issues while I am integrating the srsRAN solution with a nearRT-RIC running on a docker compose.

My current setup is the srsRAN ( commit e73b461 ) on a baremetal server, with Intel E810 and a Broadcom Quad 25Gb Ethernet. The solution is able to connect to the AMF correctly, a full Core Simulator and also to a O-RU FHI simulator. The nearRT-RIC I am trying to integrate is a comercial solution. But when I am adding the E2 interface setup configuration section to the same yaml file I was using previously, it seems it can not reach the nearRT-RIC somehow. But from the nearRT-RIC I can ping the srsRAN server E2 interface and from the server I can ping the nearRT-RIC E2 address. The core is connected to the Intel card, and the RU and nearRT-RIC to the Broadcom card. As far as I know, my nearRT-RIC is running on docker and it is exposing the port 30000:

dric-service-e2node                        NodePort    <none>        5000:30000/SCTP 

And this IP:

dric_e2_intf Link encap:Ethernet 
          inet addr:10.10.20.162

When I am executing the config file without E2 section, I am able to see that is attached to the AMF and the gNB keep working and reporting logs. And I can even attach UEs and make some testing.
But when I add the E2 configuration described here:

e2:
  enable_du_e2: true
  e2sm_kpm_enabled: true
  e2sm_rc_enabled: true
  addr: 10.10.20.162
  bind_addr: 10.10.20.171          
  port: 30000

It reports the following message:

--== srsRAN gNB (commit e73b46182) ==--
2024-11-19T10:05:18.146254 [GNB     ] [I] Built in Release mode using commit e73b46182 on branch main
Connecting to NearRT-RIC on 10.10.20.162:30000
Failed to connect SCTP socket to 10.10.20.162:30000. error="Connection refused" timeout=0ms
2024-11-19T10:05:19.447524 [SCTP-GW ] [E] Failed to connect SCTP socket to 10.10.20.162:30000. error="Connection refused" timeout=0ms
srsRAN ERROR: Failed to create SCTP gateway.

It seems it is not able to configure the interface somehow. Also, what I am expecting in the nearRT-RIC is some message from the gNB in order to reject in a first try but with the values in order to admit it in the database, something like this:

 ERROR         E2T_E2AP     E2T_DATA_01 fd 8 E2node Global Id Not Provisioned: {
   gNB {
      global_gNB_ID {
         plmn_id = 0xXXXXXX
         gnb_id {
            gnb-ID = { 32, 0xXX 0xXX 0xXX 0xXX }
         }
      }
   }
}

ERROR         E2T_E2AP     E2T_DATA_01 Provisioned E2node missing in e2_htab table
INFO         E2T_E2AP     E2T_DATA_01 E2node fd 8 sent invalid e2setup

But even this message does not appear in the nearRT-RIC. Also something I am missing is the bind_interface variable for this interface, as it is not the same as the AMF or RU FHI.

Here I attach my configuration file I am currently using and as I said, I am running on commit e73b461.
gnb-2x2-50-fdd-nearRT.txt

Thanks and regards.

[pgawlowicz]

could you share logs and e2ap pcap file?