-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
srsue<->srsgnb via zmq: downlink packets stop flowing likely due to failed PDSCH allocation #1213
Comments
I had the same issue in my environment. |
Hey @dziugas-wg2 - you don't share full logs but I guess your "waiting" results in a UE context release from the RAN/core due to user inactivity. The issue now is that this works well with full UEs, e.g. COTS phones, but not with srsUE because srsUE for 5G SA simply doesn't handle UE idle procedures. But you need to share full logs to confirm. Also try to increase the inactivity timer and see if that shifts the time before it "breaks". |
Apologies for not attaching the full logs previously @andrepuschmann , here are the full srsue and gnb logs gnb-ue-logs.zip. Could you advice which inactivity timer I should be increasing? A 5G core we are using does not enforce an inactivity timer, suggesting that it should be gnb that does that even though a UE is actively sending traffic. I see that srsenb has |
I can confirm that at least the CU/CP inactivity timer (e.g., |
Hey, I am not seeing the scheduler doing any retransmissions. Eventually, all the HARQs are getting stalled. Can you share your full config? |
gnb:
srsue:
|
In my environment, there was a similar issue when using Open5GS and free5GC for CN and connecting gNodeB and NR-UE of srsRAN. (I have slicing enabled.) The configuration details in this case are as follows.
FYI. |
I noticed that you are not using the latest release. Can you see if you still see the same issue for the latest release? If you still see the same issue, I will require your help to run this with the debugger, as I cannot reproduce the issue. I would request the following steps:
Let me know if you need more help. |
Thanks @frankist for your reply. I did not pay attention to the fact that there has been a significant number of commits to the srsRAN_Project repo recently. I recompiled gnb using the head of the main branch (1afd7240f2b5e2061ab4158e8fcdacb15961813a) and I was initially able to see ICMP replies delivered to the UE in 10 minutes without any packet loss that never happened before. However, restarting srsue and gnb made the issue to reappear and downlink packets stopped flowing after around 14 seconds and error messages I will try to run gnb with gdb as you suggested and come back to you as soon as I am able to hit the breakpoint. |
I have exactly the same problem. When using ZeroMQ, the downlink stops working after between 10 seconds to 10 minutes, with
I am using the configuration files from srsRAN gNB with srsUE. |
@frankist Stepping with gdb suggests that line 157 is reached, but
|
Here is why
|
Ok, I see the issue. This will be solved in the next release. In the meantime, maybe this hotfix is sufficient to avoid this problem:
Edit: i am basically setting 0 retransmissions for msg4, which seems to be the problematic harq |
Hi @frankist With that hotfix, ping errors no longer occurred in my environment. Thank you very much! |
I can also confirm that having the diff applied No available HARQs errors is not seen anymore. Thanks for the fix. |
Issue Description
srsue can successfully talk to srsgnb via zeromq and attach to the core network. It can then ping remote hosts and receive replies. However, around 10-20 seconds after initial registration, downlink IP packets does not reach the UE anymore.
Inspecting ICMP packets at the core network and GTPU logs at the gnb suggests that uplink ICMP packets sent from the UE are seen both by the core network and the gnb. The same is also true for the downlink packets, that is, ICMP replies are being received by the gnb, but cannot be forwarded to UE via GTPU.
Once the downlink IP packets stop flowing, for each GTPU DL forwarding attempt there is a follow up
PDSCH allocation skipped. Cause: No available HARQs
message:Setup Details
Steps to reproduce the problem
PDU Session Establishment successful.
andRRC NR reconfiguration successful.
messagesip netns exec ue1 ip route add default dev tun_srsue
sudo ip netns exec ue1 ping remote-host
for 10-20 seconds (this step can be omitted by simply waiting for around 20 seconds)The text was updated successfully, but these errors were encountered: