Can't eliminate RX_LATE packets [RAN650, n77, BW:100 MHz, no DPDK] #782
Replies: 3 comments 1 reply
-
The messages like " Dropped received Open Fronthaul message as no uplink PRACH context was found for slot '177.9' and eAxC '4'", I think it is because the RU is configured 4x2 and your DU is configured 2x2. Not sure about the other issues. |
Beta Was this translation helpful? Give feedback.
1 reply
-
@ppisanski-sg any update on this issue? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @pgawlowicz, since I have no longer access to the project, I'm closing the ticket. Br. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey guys,
I saw similar topics here, however couldn't find a fix. I run setup with RAN650, n77, no DPDK, bandwidth 100MHz, center freq: 3879.99 MHz, E810-XXVDA4T, Xeon(R) D-2187NT cpu, 128 GB RAM. Open5gs and srsRAN are running on the same server.
Setup is in sync, rms for ptp4l does not exceed 4, phc offset fluctuates between -40 and 30.
UE -redmi note 5G - attaches successfully, DL at iperf reaches ~200 Mbps between UE and gNB, UL ~50 Mbps.
However I can't get rid of RX_EARLY and RX_LATE packets.
Also number of dropped packets is quite high:
Network interface:
Kernel: 5.15.0-1066-realtime
lsb_release -a
My gnb configuration is following:
RU configuration:
root@benetelru:~# cat /etc/benetel-rootfs-version
root@benetelru:~# cat /etc/ru_config.cfg
Moreover I see a lot of received messages, like:
Received Open Fronthaul message size is '2' bytes and is smaller than the section header size
and dropped messages, like:
Dropped received Open Fronthaul message as no uplink PRACH context was found for slot '177.9' and eAxC '4'
at gnb.log
Will be grateful for any hint.
Beta Was this translation helpful? Give feedback.
All reactions