Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

srsRAN with LiteON RU - Missed incoming User-Plane messages #1035

Open
bharani1990 opened this issue Feb 4, 2025 · 0 comments
Open

srsRAN with LiteON RU - Missed incoming User-Plane messages #1035

bharani1990 opened this issue Feb 4, 2025 · 0 comments

Comments

@bharani1990
Copy link

We are trying to setup a test bed with the following components,
. LITEON FlexFi (firmware version- 02.00.10)
. srsRAN Project
. FibroLAN Falcon switch
. Intel NIC - E810XXVDA2
. OS Version - Ubuntu 22.04
. Core - Open5gs
In our setup, server running CU/DU and RU are connected via the FibroLAN switch. The devices are synchronized via PTP. Note that we are using the same interface for both PTP Sync and C/U Plane traffic.

Please find the screenshots of PTP processes in the CU/DU server below,
Image
Image

Upon running the gNB software, we could see the following message in the log file (please find it attached),
2025-02-04T12:48:17.730545 [OFH ] [W] Sector#0: missed incoming User-Plane PRACH messages for slot '500.19' and sector#0

We have crosschecked the configurations (gNB config attached) in the RU. It would be really helpful if you could help us in resolving this issue. Also it would be great if you could comment on our infrastructure setup, especially the fact that we are using the same interface for PTP sync and C/U Plane traffic.

gnb_log.zip

gnb_ru_liteon_tdd_n78_100mhz.yml.txt

additionally, attaching the screenshot which describes the oru_status before and after the gnb start. (Note: duConnected: NotReady --> in both cases)

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant