aleemgsl
commented
7 months ago Hi Team,
We have deployed omec UPF (bess) pod as a part of 4G core deployment. We are using ipvlan (on access) and host-device (on Gi) plugins. We see that traffic from enb goes to the UPF access interface enters Bess pipeline and goes out to the internet from the core interface. Downlink traffic from the Internet comes to the Gi interface and enters the bess pipeline CoreFast, and goes to Enb via the access interface.
We do not see any issue for a few days ( like 15-20 days approx), and then UPF stops processing packets. Packets are reaching access and core interfaces of UPF but are not entering the Bess pipeline.
There is no container restart/crash.
The issue gets resolved after the UPF pod is restarted.
Has anyone faced this issue before?
Hi Team,
We have deployed omec UPF (bess) pod as a part of 4G core deployment. We are using ipvlan (on access) and host-device (on Gi) plugins. We see that traffic from enb goes to the UPF access interface enters Bess pipeline and goes out to the internet from the core interface. Downlink traffic from the Internet comes to the Gi interface and enters the bess pipeline CoreFast, and goes to Enb via the access interface.
We do not see any issue for a few days ( like 15-20 days approx), and then UPF stops processing packets. Packets are reaching access and core interfaces of UPF but are not entering the Bess pipeline.
There is no container restart/crash.
The issue gets resolved after the UPF pod is restarted.
Has anyone faced this issue before?