Possible CT bug

Infrastructure & Networking DOCA Getting Started & Resources
1

When using DOCA Flow Connection Tracking with amount of sessions bigger than 150 000, doca_flow_ct_rm_entry fails around ~123 200 removals. This causes the connection tracking engine to stop working - packets are not received neither on RSS nor on egress, despite these two being last steps in the pipelines. Looks like the packets don’t enter the pipes at all

However, creation of more than 150 000 session works. Fwd and actions work correctly for all of the session. The issue is only with the removal.

DOCA ver. is 2.9.1, NVIDIA Bluefield 2 2x100Gb/s

2

Please make sure you did call the doca_flow_entries_process to complete entries operation (add, update, delete, and aged).

Thanks!

3

Hi,

I did not have these function call before, but even after adding this it does not help :( Neither invoking doca_flow_ct_entries_process nor doca_flow_entries_process solves the issue

All the best,
Sławek