Closed PauBaguer closed 6 months ago
@PauBaguer Thanks for all details, I will investigate this issue.
Hi @PauBaguer , I've been facing the same issue. Any update on that?
Regards, Ginés.
Hello @GinesGarcia, No news from my side, @pgawlowicz have you been able to pinpoint the source of the problem?
Thanks, Pau
Hey @PauBaguer, I am currently working on a similar setup as yours:
I already managed to deploy the same setup using FlexRIC instead of the O-RAN Near-RT-RIC and was able to read metrics from a FlexRIC xApp. Now I want to tdo the same with the O-RAN RIC. I am at a point where the RIC and xApp are successfully deployed and the srsRAN gNodeB successfully connects to the RIC. I can see E2SetupRequest and E2SetupResponse in the pcap. However, I do not see any E2SubscriptionRequest - neither in the logs, nor in the pcaps. Have you changed something in the code of the kpimon-go app to make it compatible with srsRAN?
Hello @P4sca1, Yes, I modified the xApp as well as the submgr component to work around bugs.
Hello @P4sca1, Yes, I modified the xApp as well as the submgr component to work around bugs.
Could you share what you needed to fix?
I would also be interested in this. I found out that in order for the E2SubscriptionMessage to be sent, the gNB needs to be already connected when the kpimon-go xApp is started. However, the xApp crashes when trying to send the message.
Hi @PauBaguer, We have just released a repository that allows running ORAN-SC-RIC as a multi-container Docker application with a single docker command. You can find it here: https://github.com/srsran/oran-sc-ric
In addition, the repository provides two example Python-based xApps that allow requesting and monitoring E2 metrics from the gNB using all reporting styles (1-5) of the e2sm-kpm module (which was updated to version 3).
The Quick Start
section in the readme file demonstrates how to use it.
Note that until the next code release, you have to use the test
branch from the srsRAN_Project repository.
Hi, I close this issue, as with the ORAN SC RIC we show that our E2 agent works correctly with all KPM Report Styles (1-5).
Issue Description
Using the latest version of srsRAN and O-RAN SC i-release, I'm unable to run the KPIMON-go xApp due to a failure in decoding the RIC Subscription Request that arrives to srsRAN.
This problem causes the variable
is_ind_msg_ready_
to always be infalse
and thus Indication messages are never sent.Setup Details
We are using branch
br-flexric
after following the tutorial, as well as the latest version of srsRAN Project.The code in O-RAN SC i-release is slightly modified to work around some internal communications bugs, in our view those changes should not affect the current problem.
logger.info()
lines have been added to srsRAN Project to aid code understanding and debugging. (It should not affect message decoding either.)Expected Behaviour
We expect the gNB to correctly decode all E2AP messages and start reporting KPM metrics via periodic RIC Indication messages.
Actual Behaviour
gnb.log At the start.
gnb.log receiving E2setupResponse.
gnb.log when receiving E2subscriptionRequest (where the failure occurs)
gnb.log: These messages are periodically present.
Console
Steps to reproduce the problem
A "simulator" is provided at https://github.com/PauBaguer/o-ran-sc_i-release_kpimon-go_simulator to quickly simulate the messages sent by the RIC without needing it.
gNB config file:
Additional Information
PCAP capture: srsRAN-fail-to-decode-RICsubscriptionRequest.pcapng.txt